[opensuse-factory] Recent "zypper dup" against Tumbleweed borks KDE5 Plasma
Hello Factory / Tumbleweed folks! Short version: recent zypper dup to Tumbleweed doesn't let me log in via KDE5/Plasma, forcing me to use LXDE. This is suboptimal ;) History: - Originally installed Tumbleweed off DVD based on the 2015-03-15 release. - Desktop was KDE4 based, lots of packages installed, etc. - On May 16th, When KDE5 / Plasma5 was hauled into Tumbleweed, I could no longer log in, with crashes similar to my current ones with krunner and plasmashell. - Forum posts recommended deleting the ~/.kde4 directory, which **worked!** Now: - More recently (ie: last ten days?), another update to KDE5 was pushed out. - Said update to KDE5 and Tumbleweed results to crashes on KDM login against plasmashell and krunner, with GUI dialog boxes saying the processes erred out. - Deleting ~/.kde4 doesn't work. - A different forum post mentioned adding "autoload=false" to ~/.config/kded5rc 's kscreen section. This too did not work. - That said, the above-mentioned purdy dialog boxes let me access developer info and get stack dumps, which I saved and attached to this email. Are there packages from kde4 that really should be blacklisted and purged from a KDE5 + Plasma install? Anything people can see from the stack traces that could hint at a solution? LXDE is functional, but not pretty, ya know?..... Ken Savage
Am Samstag, 20. Juni 2015, 11:05:44 schrieb Ken Savage:
Are there packages from kde4 that really should be blacklisted and purged from a KDE5 + Plasma install? Anything people can see from the stack traces that could hint at a solution?
Well, this rather looks like a graphics driver problem to me. nvidia is mentioned in the stack traces, so you apparently have that one installed. But is it working/are you using it? Check with "glxinfo | grep render" (package Mesa-demo-x) , or check the Xorg.0.log. I hope you are aware that you need to recompile the kernel module after each kernel update... ;-) Background: nvidia replaces some system libraries with its own, incompatible, versions which breaks Mesa (including its OpenGL software renderer). If you are not using nvidia when it is installed, applications using OpenGL won't work therefore. And Qt5 does make use of OpenGL for certain things. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I had blacklisted the nouveau driver, and definitely had pixels up, so I know the nvidia driver was doing (some of) its trickery. I know to recompile/reinstall the driver whenever the kernel was updated, but I don't always do kernel updates all the time (ie: lock the package until I'm darn good and ready to perform a reboot) ... so I had not deemed it necessary to do anything with the video driver. Your mention of Mesa lead me to reassess that assumption ;) After downloading and installing the latest drivers, presto, I'm back to my happy, compositing, KDE5 environment. Sorry LXDE, nice to know you. Thanks, Wolfgang for your hints there! Cheers, Ken On 06/21/2015 12:34 PM, Wolfgang Bauer wrote:
Am Samstag, 20. Juni 2015, 11:05:44 schrieb Ken Savage:
Are there packages from kde4 that really should be blacklisted and purged from a KDE5 + Plasma install? Anything people can see from the stack traces that could hint at a solution?
Well, this rather looks like a graphics driver problem to me. nvidia is mentioned in the stack traces, so you apparently have that one installed. But is it working/are you using it?
Check with "glxinfo | grep render" (package Mesa-demo-x) , or check the Xorg.0.log.
I hope you are aware that you need to recompile the kernel module after each kernel update... ;-)
Background: nvidia replaces some system libraries with its own, incompatible, versions which breaks Mesa (including its OpenGL software renderer). If you are not using nvidia when it is installed, applications using OpenGL won't work therefore. And Qt5 does make use of OpenGL for certain things.
Kind Regards, Wolfgang
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Sonntag, 21. Juni 2015, 16:31:24 schrieb Ken Savage:
I had blacklisted the nouveau driver, and definitely had pixels up, so I know the nvidia driver was doing (some of) its trickery.
Well, Xorg could also fall back to something else (modesetting, fbdev, or vesa) if nvidia cannot be loaded, which would require Mesa's software renderer for OpenGL then...
I know to recompile/reinstall the driver whenever the kernel was updated, but I don't always do kernel updates all the time (ie: lock the package until I'm darn good and ready to perform a reboot) ... so I had not deemed it necessary to do anything with the video driver.
Your mention of Mesa lead me to reassess that assumption ;)
After downloading and installing the latest drivers, presto, I'm back to my happy, compositing, KDE5 environment. Sorry LXDE, nice to know you.
The nvidia driver in particular replaces some of Mesa's libraries (libGL e.g.), so an update to Mesa also requires a reinstallation of nvidia, because nvidia's versions are replaced by the standard (Mesa's) ones again. That's probably the biggest reason to prefer the nvidia RPM packages (not available for Tumbleweed though). You can automatically "workaround" kernel updates with dkms e.g.
Thanks, Wolfgang for your hints there!
You're welcome. I'm glad your problems are solved. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Ken Savage -
Wolfgang Bauer