Plasma 5 broken after this morning's updates

English Install/Boot/Login
1

I installed the latest slew of Tumbleweed updates this morning and upon reboot Plasma won’t start up.
I get the OpenGL2 cannot start error, please check your video driver.
I am using a radeon card and the kernel module is installed.

I looked over this thread https://forums.opensuse.org/showthread.php/517197-Plasma-5-broken-after-this-morning-s-updates but I don’t have an nVidia card so it doesn’t seem to be my issue.
I tried pulling all the nvidia packages I could find off but still no joy.
I am logged in using IceWM but would really like to get Plasma working again.

I don’t see anything odd in /var/log/Xorg.0.log

2

I tried booting to the previous kernel (4.10.5.1) since the radeon drivers are at the kernel level and that didn’t make any difference.
Current kernel level is 4.10.8.1.

I have also tried unconditional updates on all of the installed QT5 and Mesa packages along with anything radeon related but still no luck starting Plasma.

3

OpenGL support is provided by Mesa (unless you use a proprietary driver), so your problem lies there likely.
Mesa has been updated to a newer version, and it uses libglvnd now (which is a "wrapper that allows to use several OpenGL implementations and should “solve” the “incompatibilities” between nvidia and Mesa, see also http://lists.opensuse.org/opensuse-factory/2017-03/msg00848.html).

Please install Mesa-demo-x and post the output of “glxinfo” (run as user). Maybe that provides a clue?

4

PS: How exactyl do you update your system?

Maybe try to run “zypper dup --no-allow-vendor-change”. A plain “zypper up” may cause problems in case of big changes like this.

5

Hi,

perhaps your problem is the new Mesa version. Two week ago, I had a Mesa problem because of “libglvnd” and Plasma was not able to start.
Have a look on following discussion: https://forums.opensuse.org/showthread.php/523998-Problems-with-Mesa

Best,

Michael

6

It looks like Mesa is the culprit,
glxinfo give me the following

glxinfo
name of display: :0
Xlib: extension “NV-GLX” missing on display “:0”.
Xlib: extension “NV-GLX” missing on display “:0”.
Xlib: extension “NV-GLX” missing on display “:0”.
Xlib: extension “NV-GLX” missing on display “:0”.
Xlib: extension “NV-GLX” missing on display “:0”.
Xlib: extension “NV-GLX” missing on display “:0”.
Xlib: extension “NV-GLX” missing on display “:0”.
Xlib: extension “NV-GLX” missing on display “:0”.
Xlib: extension “NV-GLX” missing on display “:0”.
Xlib: extension “NV-GLX” missing on display “:0”.
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 24 (X_GLXCreateNewContext)
Value in failed request: 0x0
Serial number of failed request: 35
Current serial number in output stream: 36

I ran zypper up to update the system in this case

7

I attempted to remove libglvnd0 but there were a ton of incompatibilities that popped up when I did so and as such I have left it (for now)

8

Almost certainly an issue with my system and Mesa, I tried removing the radeon card and putting an nvidia in and same behaviour persists.
Not sure where to go from here to try and address this and can’t seem to see how to roll back Mesa to the earlier version

9

Hi dougis,

you can install an other/older MESA version directly from the opensuse repositories. Have a look on: https://software.opensuse.org/package/Mesa (here you can choose the official Mesa version from X11:XOrg or older versions from e.g. openSUSE:Factory:Stable).

Best,

Michael

10

Indeed.

Unfortunately I don’t know anything about the new libglvnd, and I don’t use Tumbleweed either.

It turned out that a package dependency was missing, so check that Mesa-libGL1 is installed. Should only affect fresh installations though, as you should have had it installed before anyway.
But also check whether it is the latest version. A similar problem (with the same glxinfo error) in the Arch forums was indeed caused by this:
https://bbs.archlinux.org/viewtopic.php?id=165772

Or maybe “LIBGL_DEBUG=1 glxinfo” would give more clues…

I ran zypper up to update the system in this case

As I wrote, try running “zypper dup --no-allow-vendor-change”. Maybe “up” didn’t properly update all packages.