[opensuse] KDE issues following upgrade to TWeed 20180116 (with fix)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Yesterday afternoon I upgraded my laptop to Tumbleweed 20180116. I don't remember the Tumbleweed serial that I was on before then specifically, but my last upgrade day was Jan 8 of this year. Following the upgrade, after rebooting my laptop and logging into Plasma, I was greeted with a black screen with a mouse cursor. The weird thing is I could still hear my computer sounds in the background, and the mouse cursor would change shape based on what was underneath it. Eg., KGPG prompts for my password on login, and I could enter the password and hit enter and the mouse cursor would change appropriately. I could also (blindly) do alt+f2, type in konsole<enter>, type in screen<enter>, start a ping, and then resume that screen session from one of the virtual terminals. So it was as if KDE was running but hidden. I tried creating a new user account and trying to log into it (same issue,) so I knew that it wasn't a profile problem. So, I rebooted and tried to log in, and as soon as I did that, I did the following from a virtual terminal: journalctl > journalctl.txt dmesg > dmesg.txt Looking at the journalctl file, I saw this: Jan 18 14:14:28 caradhras.millikin.edu org.kde.kglobalaccel[5242]: libEGL warning: DRI2: failed to authenticate Jan 18 14:14:28 caradhras.millikin.edu org.kde.kglobalaccel[5242]: libEGL warning: DRI2: failed to open swrast (search paths /usr/lib64/dri) I did some poking around on Google, and saw references to problems with libmesa, so I decided to force-reinstall it just to be safe. As I was telling YaST to "upgrade" the various Mesa packages, as soon as I did that with the "Mesa" package, it auto-added two additional packages that weren't installed at the time - Mesa-dri and Mesa- gallium. After reinstalling all of the Mesa packages (including those two additional ones) and rebooting, all was back to normal again :) So it seems as if possibly that dependency wasn't set up correctly? Chris -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE7GM/Dul8WSWn72odQ1nEo4DFCIUFAlpiCIoACgkQQ1nEo4DF CIWyqwf+MVd47OwPQ5ROWJW6cw+8LgGHjgu1mTu37zq0onuC0p1F7T8WZ2ve73hw XgTwHzVD6A8xxeizy74FjfeVbEwll9r6XgcPJtRNi2lMF/wVcOf3f76eUL7W5zdW Ph73SUh829DZBPAMjaSum/YS8uljrmb59KDNzBsfZBrHF+HKDabX5vHwgnxxiqBr 1YF+qalduf+kL9mOb7exB3ICzb4WAW/N0SwI1z/Er1n6oqlP7DrFuieo7lU7yDzF kjrSPKjtJabRfrn5EO/Elo/4HaAyYiwC036yXkayLx5QCXbJrwaLHfS6/dP2jT8n cFwx0HQDOnSQ7LpQ6yNr9zpIyNZTBg== =Di3M -----END PGP SIGNATURE-----
On 19/01/2018 17:02, Christopher Myers wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Yesterday afternoon I upgraded my laptop to Tumbleweed 20180116. I don't remember the Tumbleweed serial that I was on before then specifically, but my last upgrade day was Jan 8 of this year.
Following the upgrade, after rebooting my laptop and logging into Plasma, I was greeted with a black screen with a mouse cursor.
The weird thing is I could still hear my computer sounds in the background, and the mouse cursor would change shape based on what was underneath it. Eg., KGPG prompts for my password on login, and I could enter the password and hit enter and the mouse cursor would change appropriately. I could also (blindly) do alt+f2, type in konsole<enter>, type in screen<enter>, start a ping, and then resume that screen session from one of the virtual terminals. So it was as if KDE was running but hidden.
I tried creating a new user account and trying to log into it (same issue,) so I knew that it wasn't a profile problem. So, I rebooted and tried to log in, and as soon as I did that, I did the following from a virtual terminal:
journalctl > journalctl.txt dmesg > dmesg.txt
Looking at the journalctl file, I saw this:
Jan 18 14:14:28 caradhras.millikin.edu org.kde.kglobalaccel[5242]: libEGL warning: DRI2: failed to authenticate Jan 18 14:14:28 caradhras.millikin.edu org.kde.kglobalaccel[5242]: libEGL warning: DRI2: failed to open swrast (search paths /usr/lib64/dri)
I did some poking around on Google, and saw references to problems with libmesa, so I decided to force-reinstall it just to be safe.
As I was telling YaST to "upgrade" the various Mesa packages, as soon as I did that with the "Mesa" package, it auto-added two additional packages that weren't installed at the time - Mesa-dri and Mesa- gallium. After reinstalling all of the Mesa packages (including those two additional ones) and rebooting, all was back to normal again:) So it seems as if possibly that dependency wasn't set up correctly?
If you look on the factory list, which is where this should have been reported, you will see that quite a few users where bitten by the Mesa-dri not installed bug. Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Christopher Myers -
Dave Plater