Bug 571632 – Plasma with x11-drivers/nvidia-drivers-361.16 - ?

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description killerpsi23 2016-01-12 08:07:25 UTC]

'sddm' got black screen
start KDE with 'startx', and then some components of KDE report crash

everything works well if downgrading to nvidia-drivers-358.16-r1 

Reproducible: Always

[Comment 1 Jeroen Roovers (RETIRED) 2016-01-12 08:32:20 UTC]

Please file a separate bug report for x11-misc/sddm.

[Comment 2 Andreas Sturmlechner 2016-01-12 09:04:06 UTC]

Known upstream problem, Nvidia currently breaks Qt.

[Comment 3 Urmet Saar 2016-01-12 13:44:29 UTC]

Just got hit by this few hours ago. This can also be fixed from Qt side. Apply https://codereview.qt-project.org/#/c/145531/ to qtgui package and everything will work.

[Comment 4 Michael Palimaka (kensington) 2016-01-12 14:51:57 UTC]

Plasma 5 I presume?

[Comment 5 Tanktalus 2016-01-12 16:41:29 UTC]

Can this level be masked due to the problems it causes?  True, it doesn't cause problems for everyone, but still for a lot of people?

[Comment 6 Michael Palimaka (kensington) 2016-01-12 16:43:54 UTC]

This thread was reported on IRC: https://devtalk.nvidia.com/default/topic/908506/linux/several-essential-kde-applications-sddm-krunner-plasmashell-segfault-on-startup-with-361-16/1

[Comment 7 Chris Smith 2016-01-12 20:21:42 UTC]

This is what I get with nvidia-drivers-361.16:

kernel: sddm-greeter[757]: segfault at e4 ip 00007f80d60db040 sp 00007ffca8d280c8 error 4 in libX11.so.6.3.0[7f80d60aa000+139000]

[Comment 8 Chris Smith 2016-01-12 20:29:08 UTC]

(In reply to Chris Smith from comment #7)
> This is what I get with nvidia-drivers-361.16:
> 
> kernel: sddm-greeter[757]: segfault at e4 ip 00007f80d60db040 sp
> 00007ffca8d280c8 error 4 in libX11.so.6.3.0[7f80d60aa000+139000]

Adding that rebuilding x11-libs/libX11, x11-misc/sddm, and kde-plasma/sddm-kcm, had no positive affect. Needed to downgrade to nvidia-drivers-358.16-r1.

[Comment 9 killerpsi23 2016-01-13 08:50:11 UTC]

(In reply to Michael Palimaka (kensington) from comment #4)
> Plasma 5 I presume?

yes, Plasma 5.

[Comment 10 Michael Palimaka (kensington) 2016-01-13 18:12:06 UTC]

nvidia-drivers-361.18 appears to be out which apparently contains a workaround.

[Comment 11 Michael Palimaka (kensington) 2016-01-13 18:35:03 UTC]

@qt, there's also a patch we could consider backporting? https://quickgit.kde.org/?p=qt%2Fqtbase.git&a=commitdiff&h=c8af3160d2514fb973a0d00d5bac324d4f7159f7&o=plain

[Comment 12 Davide Pesavento (RETIRED) 2016-01-14 00:34:15 UTC]

Sure, feel free to backport as needed. The original upstream commit/change is at https://codereview.qt-project.org/145531

[Comment 13 Jeroen Roovers (RETIRED) 2016-01-14 10:21:02 UTC]

(In reply to Michael Palimaka (kensington) from comment #10)
> nvidia-drivers-361.18 appears to be out which apparently contains a
> workaround.

I'll work on that, then.

[Comment 14 Jeroen Roovers (RETIRED) 2016-01-15 06:19:34 UTC]

So 361.18 is in the tree since yesterday.

[Comment 15 Jeroen Roovers (RETIRED) 2016-02-28 20:39:02 UTC]

How was this fixed and when and by whom? I don't see a proper description of the actual problem yet, and once we have that we can progress to telling KDE users what they should presumably do to work around or fix that problem.

[Comment 16 killerpsi23 2016-03-29 08:19:20 UTC]

It's nvidia-361.16 that breaks KDE and nvidia-361.16 has been out of portage tree.

[Comment 17 Jeroen Roovers (RETIRED) 2016-04-12 09:35:15 UTC]

*** Bug 579696 has been marked as a duplicate of this bug. ***

[Comment 18 Billy DeVincentis 2016-04-21 00:32:03 UTC]

364.15 does not exhibit any problems

[Comment 19 Michael Palimaka (kensington) 2016-08-18 20:00:22 UTC]

If I understand correctly, both nvidia-drivers and Qt were exposing a bug in the other, but a fix in one package was enough to avoid the issue.

The bug in nvidia-drivers was fixed in 361.18 (with the offending 361.16 since removed), and the Qt bug fixed in 5.6.0 (5.6.1 is now stable). I think we can definitely call this one fixed.