Bug 417341

Summary:	Plasmashell crashes in random intervalls
Product:	[Plasma] plasmashell	Reporter:	ln
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	nate, plasma-bugs
Priority:	NOR	Keywords:	drkonqi
Version:	5.17.5
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description ln 2020-02-09 14:45:04 UTC

Application: plasmashell (5.17.5)

Qt Version: 5.14.1
Frameworks Version: 5.66.0
Operating System: Linux 5.5.2-arch1-1 x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:

Plasmashell crashes in unspecific intervals when just using the desktop. I's unrelated to KDE applications themselves and also happens when e.g. using Firefox or other desktop applications.

This seems to be related to Wayland dropping the connection and plasmashell crashing and restarting afterwards.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#8  0x00007f1007decb6e in  () at /usr/lib/libQt5Core.so.5
#9  0x00007f100321be3d in  () at /usr/lib/libQt5WaylandClient.so.5
#10 0x00007f100321c0a9 in QtWaylandClient::QWaylandDisplay::dispatchQueueWhile(wl_event_queue*, std::function<bool ()>, int) () at /usr/lib/libQt5WaylandClient.so.5
#11 0x00007f100322636a in QtWaylandClient::QWaylandWindow::waitForFrameSync(int) () at /usr/lib/libQt5WaylandClient.so.5
#12 0x00007f100082075c in  () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so


Possible duplicates by query: bug 417329, bug 417285, bug 417279, bug 417232, bug 417229.

Reported using DrKonqi

Comment 1 ln 2020-02-09 14:45:05 UTC

Created attachment 125784 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 Nate Graham 2021-03-08 22:45:33 UTC


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

Comment 3 Nate Graham 2021-10-04 14:25:04 UTC


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