Bug 467756 - Plasma crashes when turning on main monitor
Summary: Plasma crashes when turning on main monitor
Status: RESOLVED DUPLICATE of bug 468430
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (show other bugs)
Version: 5.27.3
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
Depends on:
Reported: 2023-03-24 17:05 UTC by billk
Modified: 2023-04-14 15:55 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

ZIP file with 3 crash reports. Two of those state Konsole as the host application because I tried running "kstart5 plasmashell" after a crash. (3.11 KB, application/x-zip-compressed)
2023-03-24 17:05 UTC, billk
Plasma crash report with Qt debug symbols (4.33 KB, text/plain)
2023-03-25 11:14 UTC, billk
plasmashell backtrace when turning primary monitor off (2.44 KB, text/vnd.kde.kcrash-report)
2023-04-12 23:06 UTC, Mikah Chapman
plasmashell backtrace when turning monitors back on from powersave (2.19 KB, text/vnd.kde.kcrash-report)
2023-04-13 13:58 UTC, Mikah Chapman

Note You need to log in before you can comment on or make changes to this bug.
Description billk 2023-03-24 17:05:57 UTC
Created attachment 157552 [details]
ZIP file with 3 crash reports. Two of those state Konsole as the host application because I tried running "kstart5 plasmashell" after a crash.

Hello. I have a dual monitor setup on my Arch Linux system. I have noticed Plasma crashing when turning my main monitor on after it has been turned off.

Main monitor is a Samsung 27'' Curved Display, secondary is an older Samsung 23'' TV, now only used as a monitor. Both are connected through HDMI to my Sapphire Nitro+ RX580.

Reproduction steps are as follows:
1) Turn off both monitors
2) Turn secondary monitor on - nothing happens, system continues to function normally
3) Turn main monitor on - Plasma crashes

After the crash, Plasma restarts (taskbar & desktop icons vanish and reappear after a couple seconds), but the display configuration is messed up (main monitor becomes secondary and vice versa), and I have to restart my PC to get it back to normal. The KDE Crash Handler window appears only when Plasma is started with the '--no-respawn' argument.

I have to note the frequency of the issue though: on my previous Ryzen APU's integrated graphics (Ryzen 3 3200G) the issue occurred once in a while. After upgrading to the RX 580 and changing my CPU to a Ryzen 5 2600 (no integrated graphics) it occurrs every single time I turn off and then turn on my main monitor. Changing from the HDMI to the DVI or DisplayPort port(s) on my graphics card does not do anything - the issue still remains.

Crash reports are attached. (Note: The "displayport" crash report was taken when I tried connecting my main monitor to the DisplayPort port to see if anything would change.)

Also, this issue only occurs when using X11 as my window system - on Wayland there are no crashes. But, I really don't want to change to Wayland, since screen recording and similar features (such as screen sharing) do not work.

System software information:

Operating system: Arch Linux (253.1-3-arch)
Kernel: 6.1.20-1-lts x64
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Comment 1 David Edmundson 2023-03-25 08:14:27 UTC
The two of konsole crashing are of konsole crashing.

#7  0x00007fe39ef594ce in ?? () from /usr/lib/libQt5XcbQpa.so.5
#8  0x00007fe3a54ddd45 in QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) () from /usr/lib/libQt5Gui.so.5

#4  0x0000555ed87f41dd in  ()
#5  0x00007ff0204bea71 in  () at /usr/lib/libQt5Core.so.5
#6  0x00007ff0204c0fcf in QTimer::timeout(QTimer::QPrivateSignal) () at /usr/lib/libQt5Core.so.5
#7  0x00007ff0204b1b56 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5

none in KDE level code. Please get debug symbols for Qt, also ensure it's up to date
Comment 2 billk 2023-03-25 11:14:33 UTC
Created attachment 157563 [details]
Plasma crash report with Qt debug symbols

I have attached the new crash report with Qt debug symbols (feel free to ask me again if there is anything missing). Also, the host app is Konsole with 'kstart5 plasmashell --no-respawn' being ran (again) because the KDE Crash Handler window closes before I get a chance to copy or save the crash log, so it's my only other option.
Comment 3 billk 2023-03-25 11:16:24 UTC
I forgot to state that although the crash logs are a bit older, the same issue persists as of the time of writing and my system is fully up to date.
Comment 4 Bug Janitor Service 2023-04-09 03:45:36 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Mikah Chapman 2023-04-12 23:06:48 UTC
Created attachment 158050 [details]
plasmashell backtrace when turning primary monitor off

I came across this bug because plasmashell is crashing on my system whenever the monitors go to sleep. I haven't reproduced that with a backtrace yet, but I was able to reproduce a situation similar to billk: when I turn my primary monitor off, plasmashell crashes with a segmentation fault. I've been able to reproduce this with both monitors. Turning off any secondary monitors doesn't cause the crash. I am also running under X instead of Wayland.

Kernel: archlinux 6.2.10-arch1-1
plasma-desktop version: 5.27.4
CPU: Ryzen 9 5900X
GPU: Nvidia RTX 2080
Comment 6 Mikah Chapman 2023-04-13 13:58:43 UTC
Created attachment 158073 [details]
plasmashell backtrace when turning monitors back on from powersave

Adding backtrace for crash when screens are waking up. Appears to be the same issue, the screen seems to be disconnecting when it wakes, which achieves the same effect as turning it off: I think it's null pointer to/within a DesktopView object? Not super familiar with reading backtraces.
Comment 7 Nate Graham 2023-04-14 15:55:26 UTC

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