The Leap 15 Beta test build 127.1 was published 2018 Calendar Week 7: <https://download.opensuse.org/distribution/leap/15.0/iso/>.
The roadmap is here: <https://en.opensuse.org/openSUSE:Roadmap>.Draft schedule:
February 2018: Beta phase
April/May: RC phase
May: Release
Feel free to use this thread for any initial comments.
And today Build 128.1 was released:
https://lists.opensuse.org/opensuse-factory/2018-02/msg00458.html
Again a new thread? :\
My question too. I suggest we stick to one thread per “phase” … , builds can appear daily …
I updated to 127.1 yesterday evening. And this morning I went to 128.1.
Here’s the problem I am having. I am not getting an IPv4 address. This was working fine before the update to 127.1. And I’ll note that I have the same problem with recent Tumbleweed.
This is using “wicked”. I do get an IPv4 address if I use NetworkManager. And Leap 42.3 on the same computer gets an IPv4 address. It is happening on two computers. However, I also have Leap 15 in a virtual machine under KVM, and that virtual machine has no problem getting an IP address.
I’ll be reporting a bug soon.
*** to wolfi’s question – no, I don’t think we need a new thread for every build.
Definitely not.
My question was actually meant a bit sarcastic… 
This thread has “Build 127.1” in the title now, which may be confusing I think.
But whatever, let’s stick to this now.
… I think most of us will already understand that, but we still sarcastically agree.lol!
#MeToo: >:)
May be if someone with privileges could change the “Build 127.1” in the title to something like “February - March builds”
Looking at the initial thread, these Beta test threads will possibly become quite long and unwieldy if they’re not broken up into shorter time-spans.
Best regards
DCu
I tried to install openSUSE 15.0 (129.1) on a laptop with the following specs:
To start with: openSUSE 42.2 and 42.3 work fine (with graphic-cards-option set to “MSHYBRID”) on that machine.
With openSUSE 15.0 129.1 the installation system does not come up at all when the graphic-cards-option is set to “MSHYBRID”. Adding “nomodeset acpi_os_name=Linux 3” or any combination of those in grub (at the end of the line that starts with linuxefi) makes no difference. With openSUSE 42.3 i only had to add “3” in grub and the installer would start in non-graphical-mode.
Setting the graphic-cards-option to “DISCRETE” and adding “nomodeset” in grub allows to install (and then run) openSUSE 15.0 129.1 (with KDE as desktop) without any problems.
However switching the graphic-cards-option to “MSHYBRID” will cause the system to end up with a “blinking” screen after boot (although bumblebee is installed and enabled).
Before i give more details i have a few basic questions:
Is openSUSE 15.0 129.1 “mature” enough so that it is worth to look deeper into the problem described or would it be better to wait for a more “mature” version?
Is this here the correct forum to discuss my problem in detail?
Thank you very much.
Regards
susejunky
I’ve started playing with Wayland and KDE. To try that, you need to install the “plasma5-session-wayland” package. I am using SDDM for login.
When I last tried KDE/Wayland, I could see that it was not ready for prime time. That was several months ago on Tumbleweed.
Now – perhaps still not ready for prime time, but it is getting pretty close. Most of what I have tried does work. There are a few bugs.
The mouse pointer is larger with Wayland than with X11. I prefer the X11 size.
On login, “ssh-agent” is not automatically started with Wayland (it is started when using X11). This is probably an openSUSE bug rather than a KDE bug. My workaround is to start it in my shell startup file.
A couple of obvious bugs:
On login, “ssh-agent” is not automatically started with Wayland (it is started when using X11). This is probably an openSUSE bug rather than a KDE bug. My workaround is to start it in my shell startup file.
Where was it configured to autostart?
A couple of obvious bugs:
If I open “Info Center”, I can look at graphics. If I click on Wayland, and after looking there I click on OpenGL, then “Info Center” takes a segmentation fault (i.e. crashes).
If I open “Configure Desktop”, and then “Input Devices”, the touchpad settings are grayed out. The setting to disable touchpad if a mouse is plugged in – that doesn’t work. But the “Fn” key combination to disable touchpad does work. If I click on the “Mouse” tab of “Input Devices”, then the settings window disappears (presumably crashes silently).
Both are fixed with Plasma 5.12.1 and Frameworks 5.43.
I think it is in the session startup definition (for X11). I’ll note that ssh-agent is started if I login to KaOS with Wayland, but not with openSUSE and Wayland. That’s why I assume it is an openSUSE issue rather than a KDE issue.
Both are fixed with Plasma 5.12.1 and Frameworks 5.43.
Glad to hear that.
Hi,
When you do your testing on Wayland on KDE on any of your test systems are you using proprietary or open source drivers?
The reason I’m asking is I have a legacy nvidia card - 340.xx drivers.
Of course if you aren’t using nvidia the question for you is pointless.
Anyone who is using nvidia proprietary drivers please feel free to chip in.
Best wishes
AFAIK (i.e. unless that has changed recently), Plasma/Wayland will not work at all with the proprietary nvidia driver.
The reason is that the driver doesn’t support the same interfaces that the open source drivers do, so would need explicit support in kwin (which the maintainer refuses/or at least refused to add).
nvidia’s Wayland support basically requires patches/changes to the compositor which they only offer for Weston (and probably GNOME).
See also:
https://community.kde.org/Plasma/Wayland_Showstoppers#NVIDIA
https://blog.martin-graesslin.com/blog/2017/10/plasmawayland-and-nvidia-2017-edition/
PS: as I just read in the second link, it actually should at least work meanwhile, but without hardware acceleration i.e. probably (very) slow.
I am not. My last computer with Nvidia graphics died about 1 year ago.
I’m all Intel graphics (various versions).
I see that Tumbleweed is now at Plasma 5.12.1, which seems to have fixed some of the Wayland problems. But Leap 15.0 Build 139.1 is still on Plasma 5.12.0.
I just noticed another problem with KDE Wayland. The pager, to switch between virtual desktops is not showing in the panel. And if I go to the settings (“configure desktop”), that shows only one virtual desktop, and it won’t accept changes. However, the keys that I set for switching desktops still work, so Wayland does properly switch between them. It is just a tad confused. That seems to still be an issue with Plasma 5.12.1.
Thanks for the reply,
I take no comfort from what I read in the second link.
However I read the comments as well and the last one is optimistic.
Thanks again,
h
OK.
Thanks for replying,
h
That’s because virtual desktops are not fully supported on Wayland (yet).
See also the first link in my previous reply:
https://community.kde.org/Plasma/Wayland_Showstoppers#Virtual_Desktops
But only regarding XWayland, which will only affect X11 applications and not the desktop…
Anyway, that’s out of scope in a discussion about Leap 15.0 Beta IMHO, maybe the situation will be slightly better when we talk about Leap 15.1 Beta though…
PS: The keyboard shortcuts probably work because they are handled by kwin (the compositor) itself.
But there currently is no way for other applications (like the pager) to get information about virtual desktops or change/switch them.
Or at least that’s how I understand it.
As I keep writing, Wayland is still very much work-in-progress…
Although it should be more or less usable in general meanwhile (depending on your graphics card, I suppose).
Just don’t expect all features (that were in X11) to work. Some may not even be possible in Wayland…
With build 139 running in an Oracle VirtualBox (latest version) VM, (KDE) Plasma Wayland has more than a few issues around screen/display tearing and other misbehaviour with switching between “VM in a window” and “VM full screen”. Plasma “normal” (X11) is looking good.