Bug 368754

Summary:	KDE Plasma version 5.7.4 kactivitymanager
Product:	[Plasma] kactivitymanagerd	Reporter:	Jón Frímann <jonfr3200>
Component:	general	Assignee:	Ivan Čukić <ivan.cukic>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	plasma-bugs
Priority:	NOR
Version:	5.7.0
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:

Description Jón Frímann 2016-09-13 18:48:47 UTC

When on Facebook and new message is received this can trigger a crash in kactivitymanager due to the banner of Firefox going up and down as it blinks. This completely freezes  the kde framework and only way to restart it is to go shell and restart xdm. This happens every time a new message is received on Facebook. This might be related to nvidia, that also crashes at the same time but I do not think the drivers are at fault here. 

Reproducible: Always

Steps to Reproduce:
1. Log-in to Facebook in Firefox 45.3.0 (ESR).
2. Get new message while logged into Facebook, several windows needs to be open so the list appears along with other normal desktop application. I just have Thunderbird and shell open. Along with clementine as an icon in the task bar next to the clock.
3. The banner is going to blink with the new message making it hard to click on as it moves up and down and then crash happens.

Actual Results:  
KDE plasma 5 crashes hard and cannot be worked on.

Expected Results:  
I should be able to click on the open window list with out crash happening.

From dmesg, I don't have other debug information due to the nature of the crash.
------
[  765.864078] kactivitymanage[3551]: segfault at 7fa2a4ff1c50 ip 00007fa2a4111071 sp 00007fffe4763958 error 4 in libQt5Sql.so.5.6.1[7fa2a40fc000+42000]
[  765.948650] traps: ck-remove-direc[4119] trap int3 ip:7f2d5be2b537 sp:7ffd150e2290 error:0
[  766.162120] nvidia-modeset: Freed GPU:0 (GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI:0000:01:00.0
[  766.613672] nvidia-modeset: Allocated GPU:0 (GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI:0000:01:00.0
[  778.642296] traps: ck-remove-direc[4209] trap int3 ip:7fc4e28eb537 sp:7ffca3201a00 error:0
[  779.661008] QXcbEventReader[4304]: segfault at 7fd9a90d3ef9 ip 00007fd9a90d3ef9 sp 00007fd9a650aea0 error 14 in locale-archive[7fd9a918c000+26c000]
[16865.944833] traps: ck-remove-direc[9220] trap int3 ip:7f1991deb537 sp:7fff6c34d820 error:0
[16865.952519] kactivitymanage[4317]: segfault at 7f1f0c021c50 ip 00007f1f00351071 sp 00007ffee1a4f8a8 error 4 in libQt5Sql.so.5.6.1[7f1f0033c000+42000]
[16866.371451] nvidia-modeset: Freed GPU:0 (GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI:0000:01:00.0
[16866.806249] nvidia-modeset: Allocated GPU:0 (GPU-c596bde8-99af-0bbf-bfda-49e673acdf90) @ PCI:0000:01:00.0
[16881.976298] traps: ck-remove-direc[9260] trap int3 ip:7f5c14f1b537 sp:7ffd89f6f230 error:0
[21853.867588] kactivitymanage[9384]: segfault at 7f66e8f39c50 ip 00007f66e8059071 sp 00007ffdbf01c398 error 4 in libQt5Sql.so.5.6.1[7f66e8044000+42000]
[21853.892186] traps: ck-remove-direc[11549] trap int3 ip:7f5b22f43537 sp:7fff94837700 error:0
[21861.462516] traps: ck-remove-direc[11636] trap int3 ip:7fb3ed613537 sp:7ffed9d0c1d0 error:0
[31277.972176] kactivitymanage[11755]: segfault at 7f9863361c50 ip 00007f9860059071 sp 00007ffeb7ea1b38 error 4 in libQt5Sql.so.5.6.1[7f9860044000+42000]
[31278.034639] traps: ck-remove-direc[13579] trap int3 ip:7fd172ebb537 sp:7fffe0fc2110 error:0
[31283.524440] traps: ck-remove-direc[13666] trap int3 ip:7f2e37703537 sp:7ffc84741a50 error:0

Comment 1 Jón Frímann 2016-09-15 00:25:31 UTC

I wanted to add to this information. I was using an old xorg-server (version 1.7.4). This seems to have triggered the issue I found. I hope that upgrading to xorg-server version 1.8.3 solves this problem. The problem has to due with how graphic (of KDE) is not properly handled by the old xorg-server, along with changes in the nvidia driver that are not properly supported by older versions of xorg-server.

Comment 2 Ivan Čukić 2016-09-20 14:25:14 UTC

There is a bug in QtSQL which makes kamd (sometimes, often) crash on exist. Some issue you have with xorg triggers kamd to exit improperly, and it crashes.

*** This bug has been marked as a duplicate of bug 348194 ***