Summary: | media-libs/libglvnd makes Qt(?) unusable | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mark Nowiasz <mark+gentoobugs> |
Component: | Current packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mark Nowiasz
2020-03-07 09:32:04 UTC
I just ran the same update, and Plasma 5.18.2 runs fine for me. (In reply to Andreas Sturmlechner from comment #1) > I just ran the same update, and Plasma 5.18.2 runs fine for me. Well, I can give you some more information. I'm running this setup: A laptop connected to a larger monitor which is Plasma's primary display (the Laptop's screen is secondary). During a emerge -uDN (libglvnd was just installed) the screensaver got activated and all I got was the "failed to unlock... use loginctl unlocksession.." screen (the one you usually get when you are in the middle of updating qt). This time I wasn't able to switch to a virtual console, however I was able to use my phone to ssh into the laptop and then issue a loginctl unlocksessions and the screen unlocked. However, Plasma was in odd state - no windows, no bar, there was just a hint of one of the windows - a uttermost left part of it was partly visible on the main screen. It was as if there was a *third* screen right to main screen. I wasn't able to do anything apart from moving the mouse, so I rebooted - and sddm-greeter was unable to work. As a wild guess: It seems that the combination (libglvnd, mesa, xorg) is unable to detect the screens properly. The sddm log (issued when I tried to start sddm manually as root) seems also to support this theory: [10:06:00.983] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{eb662282-36ef-425f-99df-77123183cf9f} -background none -noreset -displayfd 17 -seat seat0 vt1 [10:06:01.095] (EE) DAEMON: Failed to read display number from pipe [10:06:01.096] (EE) DAEMON: Display server failed to start. Exiting [10:11:15.708] (II) DAEMON: Initializing... [10:11:15.713] (II) DAEMON: Starting... [10:11:15.714] (II) DAEMON: Logind interface found [10:11:15.715] (II) DAEMON: Adding new display on vt 1 ... [10:11:15.715] (II) DAEMON: Loading theme configuration from "" [10:11:15.715] (II) DAEMON: Display server starting... [10:11:15.715] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{cc2b9aa6-dc06-497c-98b5-d72fc2f71139} -background none -noreset -displayfd 17 -seat seat0 vt1 [10:11:16.119] (EE) DAEMON: Failed to read display number from pipe [10:11:16.119] (EE) DAEMON: Display server failed to start. Exiting I expect you at least need to restart X. Are the problems fixed after doing that? (In reply to Matt Turner from comment #3) > I expect you at least need to restart X. Are the problems fixed after doing > that? <Sarcasmmode>Well, if numerous reboots (and manual restarting sddm) to find out what package caused this malfunction counts as "restart X" I reckon that the problems weren't fixed after doing that, as stated above: > After rebooting, sddm stopped working, too - so I was unable to login </Sarcasmode> I'm not in the habit of issueing bug reports that a simple "Have you tried turn it on and off" would fix. My apologies. I've looked at a huge number of bugs today... To confirm, you have libglvnd, mesa[libglvnd], and xorg-server[libglvnd] installed? (And nvidia-drivers[libglvnd] if you have nvidia-drivers) (In reply to Matt Turner from comment #6) > To confirm, you have libglvnd, mesa[libglvnd], and xorg-server[libglvnd] > installed? (And nvidia-drivers[libglvnd] if you have nvidia-drivers) I had, and it was not working - it created havoc with Plasma: I was unable to unlock the screen, after unlocking it via loginctl unlocksessions the windows/bars have vanished (probably moved to the uttermost right of the screen) After reboot sddm (in fact, sddm-greeter) didn't work, either. The only way to fix it was adding "-libglvnd" to USE in /etc/portage/make.conf and reinstalling xorg and mesa (20.0.0, 20.0.1 caused permanent @presevered-rebuild, even after running through, but that's another story) it worked again. I'm not using nvidia-drivers, I'm using intel/i965. Some more information: On another machine libglvnd works just fine - even with intel/i965, however this machine isn't running Plasma - just xbmc via X. Some more information: I had an emerge -uDN running, about 17 packages. I let the laptop do it's work, screensaver was activated and then the "unable to unlock session"-Screen came on when I tried to unlock it - with the result I described before. I tried to pinpoint the package and came to libglvnd. However, a simple emerge --unmerge libglvnd didn't suffice - after doing that an rebooting sddm-greeter still didn't work. Only after USE="-libglvnd" emerge -1 xorg mesa it worked again. What's so puzzling: mesa/xorg worked just fine *before* libglvnd was installed. After that Plasma broke down - even unmerging libglvnd had no effect. To be honest, I have no idea what exactly went wrong, hence the quite verbose bug report After taking some precautions - taking a snapshot of /'s filesystem so I could easily revert - I've disabled the "-libglvnd" and did a emerge -uDN @world @system, installing libglvnd during the process plus recompiling xorg/mesa. Guess what? This time everything worked without a problem. I still don't understand what exactly caused these problem the first time :-/ (In reply to Mark Nowiasz from comment #8) > After taking some precautions - taking a snapshot of /'s filesystem so I > could easily revert - I've disabled the "-libglvnd" and did a emerge -uDN > @world @system, installing libglvnd during the process plus recompiling > xorg/mesa. > > Guess what? This time everything worked without a problem. I still don't > understand what exactly caused these problem the first time :-/ Ugh, that's the worst :| Thanks for following up! |