Bug 479589

Summary:	Plasma crashes and restarts when screen is locked on X11
Product:	[Plasma] plasmashell	Reporter:	Ahmad Khalifa <ahmad>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	akselmo, kde, nate
Priority:	NOR	Keywords:	drkonqi
Version:	5.27.5
Target Milestone:	1.0
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Ahmad Khalifa 2024-01-10 01:24:57 UTC

Application: plasmashell (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.4.3 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [CoredumpBackend]

-- Information about the crash:
On a multiscreen setup, when unlocking there is occasionally a crash handler dialog complaining about a plasma crash.
Desktop looks normal and is restored to a normal state, just the DrKonqi dialog complaining about the crash
It's not directly after a lock or a manual lock/unlock. But usually when leaving the machine for a while to to lock itself then coming back a few hours later.

This behaviour has been around for more than a  year since the machine was on Debian 11 and persisted through the upgrade to 12.
There are several standard widgets running and frequent changes to primary screen and going from 1->2->3 screens multiple times a day.

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#5  QWeakPointer<QObject>::internalData() const (this=0x58) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:696
#6  QPointer<QScreen>::data() const (this=0x58) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer.h:77
#7  QPointer<QScreen>::operator QScreen*() const (this=0x58) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qpointer.h:83
#8  DesktopView::screenToFollow() const (this=0x0) at ./shell/desktopview.cpp:124
#9  0x000056410df0d4c0 in ShellCorona::screenInvariants() const (this=0x56410ec8a3c0) at ./shell/shellcorona.cpp:828


Reported using DrKonqi

Comment 1 Ahmad Khalifa 2024-01-10 01:24:58 UTC

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

DrKonqi auto-attaching complete backtrace.

Comment 2 Ahmad Khalifa 2024-01-10 01:48:03 UTC

Just to explain how occasional it is and very difficult to reproduce, here is 'coredumpctl list'

Sat 2023-12-02    88183 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Sat 2023-12-02   140085 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Sun 2023-12-03   216853 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Fri 2023-12-08     2144 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Sun 2023-12-10   154488 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Sun 2023-12-10   179588 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Fri 2023-12-15     2258 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Sat 2023-12-16    33209 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Sat 2023-12-16    82034 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Sun 2023-12-17    82647 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Thu 2023-12-21   100673 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Sun 2023-12-24   218747 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Sat 2023-12-30  1606772 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Tue 2024-01-02  1769663 1000 1000 SIGSEGV missing  /usr/bin/plasmashell
Mon 2024-01-08  3003451 1000 1000 SIGSEGV present  /usr/bin/plasmashell
Tue 2024-01-09     2244 1000 1000 SIGSEGV present  /usr/bin/plasmashell

I also went back to a previous crash to check the backtrace and it's the same stack trace as the attached one.

Comment 3 Akseli Lahtinen 2024-01-10 14:16:15 UTC


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

Comment 4 Nate Graham 2024-01-11 16:02:06 UTC


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