Discussion thread for Leap 42.2 Beta1

Writing this from Leap 42.2 Beta1.
I have upgraded a standard KDE 42.1 and installed a standard XFCE in Virtualbox and upgraded a 42.2 Alpha3 Gnome on bare metal using the iso DVD image.
The only apparent problem so far is a “package Thunderbird is broken” warning in the XFCE install.
The installer and the base system seem already “production grade”; for the package selection we have a few weeks left before “package freeze”…

Seems there are some grumblings on the Factory ML regarding btrfs and quotas being enabled… how big is your btrfs partition?


btrfs qgroup show /

Running Tumbleweed and SLED 12 SP2 RC2 (Similar to 42.2) and not seen any issues, but my / partitions are only 40GB.

Hi there!

Was it something wrong whit the tread I started about 42.2 beta 1?

A new tread… Hmm. Intresting. The club of offshelf-admirers maybe?


Is that what that factory thread was all about. I’m not using “btrfs” so I didn’t bother to read it. I haven’t run into quota problem with “ext4” yet (not sure if they are turned on).

Two bare metal installs here (different computers).

On one of them, I have intermittent “lvmetad” issues (bug 989871).

The good news is that Plasma 5 is running on nouveau for one of those installs. I have to give up on Plasma 5 with the alpha3 release on that computer. This time the first login crashed and burned. But on the second login it was fine, and it had automatically set the compositing backend to use XRender. (With Leap 42.1, I have to manually set XRender to use nouveau).

The bad news is that on both computers, when I logout from KDE it looks as if the plasma desktop is crashing and restarting before it finishes logging me out. That also happened with Alpha3, but it doesn’t happen with Tumbleweed.

Apart from what I mentioned above, it has gone pretty smoothly. The install went well.

My fresh install on a clean disc seems pretty good. The installation went smoothly. I get a possible Plasma crash and restart when shutting down - which then manages to shutdown without any help.

No problem with Thunderbird. Limited testing so far but nothing obviously wrong. Am using 42.1 Packman successfully.

No BTRFS on my SSDs, sorry. Might try the “default install” next week on my test machine.

Nothing wrong, it just stated “My op about…”, not “Discussion…” where we usually discuss issues before possibly filing bugreports…

I have installed this on my ASUS X550C Inter I7 laptop, mostly seems OK, not had the Plasma crash on shutdown (yet). However there is one strange thing which I noticed on this laptop when I had TW on it and that is I am unable to change the konsole appearance to black on white. Also although the initial install shows the plymouth screen OK having re-done grub2 to change the timeout I now have the problem with ??? (yes three question marks) instead, this also happened on the TW install, neither of which were dual-booted. I’m stll unable to get the icons I want , plus another couple of other niggles but that is probably me having a senior moment. I am disappointed it only has digiKam V4 as well as default.


Spoke too soon, just logged out and had the plasma crash. Also been ubale to allow hibernate as an option, so far not found any way of doing this, resume is set OK in grub2 but not hibernate option in menu, swap is big enough and mounted. Anyone any suggestions please?


I logged into Gnome Classic. That is to say, I selected “Gnome Classic” on the login window. That took me to KDE Plasma 5. It probably went to the default desktop.

So I checked with Yast Software Management, and Gnome Classic is indeed installed. So something must be broken.

An update on this.

Login to Gnome Classic works from GDM. It does not work from “sddm” or from “lightdm”

I really hate GDM with a passion. But then I don’t much care for Gnome, either. So I guess I’ll go back to “lightdm” and not try to use Gnome Classic.

Writing this from a clean Gnome install on bare metal; install OK, even with bumblebee & Nvidia 367.27.
Everything seems functional at first sight, but…

The good:

  1. working OOTB with the customary config for this machine, even with Nvidia (Nouveau doesn’t support my Maxwell chip);
  2. suspend-to-ram and suspend-to-disk work OOTB (with enough SWAP); options configurable in Gnome Tweak tool;
  3. fn+F1 to fn+F12 (LCD brightness, volume, touchpad enable, KBD light…) work as expected;
  4. **@nrickert **confirming logging to Gnome Classic or SLE Classic from GDM, although some of the above doesn’t work there; Gnome almost depends on GDM, so no surprise.

The bad:

  1. “grilo-plugins” still at 0.2.x, while at least 0.3.x is needed on Gnome 3.20; multimedia functionality greatly impaired (although individual files play…);
  2. **@broadstairs **LibreOffice still at 5.1.3 (has broken OpenCL support, for instance), possibly other major apps hopefully to be updated before release; what are we really testing right now?

The odd:

  1. “primus-32” is included in the DVD, but the main “primus” is not; both need “bumblebee” which is not on the DVD either, so anyway an “optimus” laptop cannot be thoroughly installed even with the “nouveau” driver; is there a reason for that or the package selection is somewhat casual at this stage?
  2. “Thunderbird broken” on the DVD, but DVD sha256 match? Apparently no problem with the (same version) from the online repo?

I’m wondering if my testing time is worth it at this stage:

  1. the base system seems pretty solid, but this would be still an Alpha in my world;
  2. major DEs seem not yet up to par; don’t see any real progress in Gnome relative to Alpha3; the more popular KDE seems lagging behind even more from early reports here…
  3. major applications seem nowhere near their expected release version …

So, this Beta is a good workbench for developers, to work out the remaining build problems they face, but maybe not yet something to be extensively tested by “users” like me.
Better wait Beta3 for extensive testing? Or am I missing something obvious (to nrickert :wink: ) as usual?

For KDE, it is a wait for Beta3. That’s when we will see Plasma 5.8, as understand it.

I can’t install the nvidia proprietary drivers in the 42.2 Beta1. Is this to be expected? If so, at what point should I expect these drivers to be easily installable?

sudo zypper install x11-video-nvidiaG04
Problem: nothing provides ksym(default:up_read) = 996808b2 needed by nvidia-gfxG04-kmp-default-367.35_k4.1.12_1-25.1.x86_64

In the meantime, I’m considering intalling the drivers the hard way but the wiki doesn’t seem to have instructions for uninstalling the nvidia driver and going back to nouveau (for when I decide to try installing via zypper again). Does anyone know how to do that? What do I need to do in addition to removing nouveau from the modprobe blacklist?

That’s up to Nvidia AFAIK.
nvidia-gfxG04-kmp-default-367.35_k4.1.12_1-25.1.x86_64 is not compatible with the 4.4.x kernel in 42.2, but the “hard way” should work like the Bumblebee Project version that had no problem here.

In the meantime, I’m considering intalling the drivers the hard way but the wiki doesn’t seem to have instructions for uninstalling the nvidia driver and going back to nouveau (for when I decide to try installing via zypper again). Does anyone know how to do that? What do I need to do in addition to removing nouveau from the modprobe blacklist?

I never had to do that, but see ch. “4G. OTHER FEATURES OF THE INSTALLER” in the README file in /usr/src/nvidia-367.27-20.1 (or adjust for your version of the NVIDIA***.run file) for uninstall options.

Try “systemctl hibernate” to see if it works. Gnome can be configured to hibernate by pressing the power button, don’t know about KDE shortcuts.

Installed 42.2 Beta1 on a HP ProBook 455 G1 with the AMD A4-5150M APU dual core (ARUBA GPU) aside from the Install first slide still saying 42.1, install went fine, no issues. Gnome shell configured with my favorite shell extensions (lock keys, openWeather and Activities configurator). So far all good…

My only issue is being stuck with the radeon driver now on this system, no access to boost states for the APU :frowning:

My version of that directory doesn’t seem to contain a README file. However, looking at the NVIDIA-Linux-x86_64-367.44.run file with a text editor I found out that it comes with a “–uninstall” command line option. Anyways, thanks for the help. Now I can run my games again!

I’ve sorted the hibernate issue. Here you have to turn off the secure boot flag in the BIOS for it to hibernate, having done that it shows up and works. This became an issue when I used Fedora a while ago, apparently there is no way to verify that you are loading the correct OS/kernel when starting from hibernate in secure boot mode. So if you want hibernate currently you have to turn off the BIOS option.