Bug 476135

Summary:	Crash when waking up from sleep
Product:	[Plasma] plasmashell	Reporter:	Nicolas <nicolas>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	kde, nate
Priority:	NOR	Keywords:	drkonqi
Version:	5.27.8
Target Milestone:	1.0
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi

Description Nicolas 2023-10-27 06:19:28 UTC

Application: plasmashell (5.27.8)

Qt Version: 5.15.11
Frameworks Version: 5.111.0
Operating System: Linux 6.2.0-35-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.8 [CoredumpBackend]

-- Information about the crash:
I have connected a docking station and two external displays. Whenever the system wakes up from sleep, the first thing it does is that plasma crashes.

Notebook: lenovo x1 extreme gen2, NVIDIA GeForce GTX 1650 (535.113.01), Docking station: lenovo thunderbolt 3 dock

The crash can be reproduced every time.

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


The reporter indicates this bug may be a duplicate of or related to bug 474868.

Reported using DrKonqi

Comment 1 Nicolas 2023-10-27 06:19:29 UTC

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

DrKonqi auto-attaching complete backtrace.

Comment 2 Nate Graham 2023-10-27 15:26:28 UTC


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

Comment 3 Nate Graham 2024-01-11 16:01:57 UTC


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