FS#47728 - After update to qt5.5.1-8 plasmashell crashes all the time and sddm flickers

Attached to Project: Arch Linux
Opened by Sascha P. (MrPeacock) - Tuesday, 12 January 2016, 18:57 GMT
Last edited by Felix Yan (felixonmars) - Saturday, 16 January 2016, 13:45 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Felix Yan (felixonmars)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 10
Private No

Details

Description:
sddm flickers. after login plasmashell crashes, no taskbar

Additional info:
* package version(s)
* config and/or log files etc.

nouveau driver

Steps to reproduce:

update qt5 to 5.5.1-8

Jan 12 19:44:48 kiste kernel: nouveau 0000:02:00.0: fb: trapped read at 0000000000 on channel 6 [1f60e000 plasmashell[1801]] engine 00 [PGRAPH] client 0a [TEXTURE] subclient 0
Jan 12 19:44:48 kiste kernel: nouveau 0000:02:00.0: gr: 00200000 [] ch 6 [001f60e000 plasmashell[1801]] subc 3 class 8297 mthd 1b0c data 1000f010
Jan 12 19:44:48 kiste kernel: nouveau 0000:02:00.0: gr: TRAP_TEXTURE - TP0: 00000003 [ FAULT]
Jan 12 19:44:48 kiste kernel: nouveau 0000:02:00.0: gr: 00408910: f5ef0000
Jan 12 19:44:48 kiste kernel: nouveau 0000:02:00.0: gr: 0040890c: 40000430
Jan 12 19:44:48 kiste kernel: nouveau 0000:02:00.0: gr: 00408908: ec00fbdf
Jan 12 19:44:48 kiste kernel: nouveau 0000:02:00.0: gr: 00408904: b2281c08
Jan 12 19:44:48 kiste kernel: nouveau 0000:02:00.0: gr: magic set 0:

downgrade to qt5-5.5.1-7 solves the problems
This task depends upon

Closed by  Felix Yan (felixonmars)
Saturday, 16 January 2016, 13:45 GMT
Reason for closing:  Fixed
Additional comments about closing:  5.5.1-9
Comment by Sascha P. (MrPeacock) - Tuesday, 12 January 2016, 19:08 GMT
see https://bbs.archlinux.org/viewtopic.php?pid=1594792#p1594792

May https://bugs.archlinux.org/task/47703 cause this problems?
Comment by Juan Francisco Cantero Hurtado (juanfra) - Wednesday, 13 January 2016, 01:10 GMT
I can confirm the bug. The problem is obviously related to the patch fs47703. If you (maintainer) need a quick workaround, probably enclosing the new code in an "if" which checks that "glxvendor" is not nouveau would be enough.
Comment by Gustavo Alvarez (sl1pkn07) - Wednesday, 13 January 2016, 03:01 GMT
reverse related

if not apply the patch of https://bugs.archlinux.org/task/47703:
https://devtalk.nvidia.com/default/topic/908506/linux/several-essential-kde-applications-sddm-krunner-plasmashell-segfault-on-startup-with-361-16/
Comment by Antonio Rojas (arojas) - Wednesday, 13 January 2016, 09:26 GMT
This patch is also causing heavy flickering on Intel. Should be reverted until properly fixed upstream, having nvidia broken in testing is less bad than having intel and nouveau broken in extra
Comment by Baeyens (berbae) - Wednesday, 13 January 2016, 15:22 GMT
nouveau broken here also using openbox, chromium, xscreensaver, ...
I downgraded qt5 to 5.5.1-7
Comment by Alex (__AlexL__) - Wednesday, 13 January 2016, 16:08 GMT
It is so because fs47703.patch is correct for nvidia only. Looks like qt5 mantainer has nvidia. I recompiled qt5-base with modified patch I attached. Please replace your patch by mine one in next qt5 package release.
   fs47703.patch (2.1 KiB)
Comment by Felix Yan (felixonmars) - Wednesday, 13 January 2016, 16:46 GMT
Is the patch still needed with nvidia beta 361.18?
Comment by Darek (blablo) - Wednesday, 13 January 2016, 17:23 GMT
@Felix https://devtalk.nvidia.com/default/topic/908506/linux/several-essential-kde-applications-sddm-krunner-plasmashell-segfault-on-startup-with-361-16/post/4776281/#4776281
Edit: Today NV released 361.18 beta
Comment by AnAkkk (AnAkkk) - Wednesday, 13 January 2016, 18:01 GMT
@Alex, technically this patch may not be correct either. What if glXGetCurrentDisplay() returns null in any case because it's called too early or something, then m_supportsThreading will always be false (where it was supposed to be true before the patch).
It seems that the method to check which driver is being used should probably be changed.
Comment by Felix Yan (felixonmars) - Thursday, 14 January 2016, 01:51 GMT
With nvidia beta 361.18 driver and qt5 5.5.1-7 (the unpatched packages) I am unable to reproduce any crashes. If you can confirm this too, I'm going to remove the patch and release -9.
Comment by Alex (__AlexL__) - Thursday, 14 January 2016, 05:35 GMT
AnAkkk, I'm agree but my change will be workable on any gpu. Could you tell me why 97%-incorrected patch was added into release package? Was it tested with Intel gpu for example?
Comment by Ongun Kanat (6ng4n) - Thursday, 14 January 2016, 16:21 GMT
The same happens with Intel i915 driver here. I'm using mesa libGL.
Comment by Stanislav (Stanislav_pythonist) - Friday, 15 January 2016, 15:14 GMT
Confirm on i915 (just flickering)
Comment by AnAkkk (AnAkkk) - Friday, 15 January 2016, 23:17 GMT
@Alex, I guess in the first place the patch shouldn't have been merged in Qt git repo, now it's going to be in Qt 5.6 either way if the issue doesn't get fixed.

EDIT: Actually for some reason this patch has only been merged in the 5.5 branch.
Comment by dovla (kakonema) - Saturday, 16 January 2016, 12:54 GMT
@Felix flickering is fixed with downgrading to qt5 5.5.1-7. I.m using nouveau.

Loading...