Bug 348350

Summary:	Plasmashell crashed on clicking on the updater icon
Product:	[Plasma] plasmashell	Reporter:	Lastique <andysem>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	bshah, davidsboogs, notmart, plasma-bugs
Priority:	NOR
Version First Reported In:	5.3.0
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Crash report

Description Lastique 2015-05-28 06:52:56 UTC

Plasmashell crashed when I clicked on the updater icon in the system tray. This doesn't usually happen, so I don't think updater or any other icon is the trigger.

Reproducible: Couldn't Reproduce




Kubuntu 15.04, x86_64, Plasma 5.3 from Kubuntu backports, Nvidia drivers 346.59.

Comment 1 Lastique 2015-05-28 06:53:23 UTC

Created attachment 92881 [details]
Crash report

Comment 2 Marco Martin 2015-05-28 08:17:27 UTC

pasting relevant piece inline
bt doesn't seem to tell too much
Thread 30 (Thread 0x7fd7ea5f0700 (LWP 2444)):
[KCrash Handler]
#6  0x00007fd9bfaa04f0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x00007fd9bfacbf26 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x00007fd9bfa9d986 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#9  0x00007fd9bfa9f360 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#10 0x00007fd9baf94b0e in QThreadPrivate::start (arg=0x5c62190) at thread/qthread_unix.cpp:337
#11 0x00007fd9ba19a6aa in start_thread (arg=0x7fd7ea5f0700) at pthread_create.c:333
#12 0x00007fd9ba91eeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Comment 3 Lastique 2015-05-28 08:27:34 UTC

Yes. Unfortunately, I didn't find a debug package for libQt5Quick.so.5.

Comment 4 Marco Martin 2015-07-20 08:56:30 UTC

different action that brings to the crash, but very similar backtrace

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

Comment 5 Marco Martin 2015-07-20 08:56:46 UTC

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