Bug 500610 - Plasma crashes when monitor plugged in
Summary: Plasma crashes when monitor plugged in
Status: RESOLVED DUPLICATE of bug 499383
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 6.3.1
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-02-23 08:46 UTC by mitchell
Modified: 2025-02-23 21:12 UTC (History)
1 user (show)

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


Attachments
New crash information added by DrKonqi (225.32 KB, text/plain)
2025-02-23 08:46 UTC, mitchell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mitchell 2025-02-23 08:46:09 UTC
Application: plasmashell (6.3.1)

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.2
Frameworks Version: 6.11.0
Operating System: Linux 6.13.3-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.3.1 [CoredumpBackend]

-- Information about the crash:
Since plasma 6.3, plugging in a displayport monitor (my primary monitor) causes plasma to crash. This is a similar issue to what happened in 6 (and possibly 6.1?) and was fixed in 6.2.

In addition, plasma jacks the brightness of the monitor to 100%. At least, I assume plasma does it, as plasma does offer brightness controls. I can use plasma to turn the brightness back down.


This often happens during waking my PC from sleep, as my monitor has a firmware bug causing it to appear unplugged to the PC when the monitor is powered off. (It's physically plugged in all the time.) I can avoid the firmware bug by turning off Freesync VRR on the monitor settings.

Sometimes when waking from sleep, my main monitor doesn't get a signal, continuing to act as if the cable was unplugged despite being plugged in and the PC awake. This never happened before the plasma 6.3 upgrade, but I also got a new kernel version during that upgrade, so this could be a kernel bug?

The reporter is unsure if this crash is reproducible.

-- Backtrace (Reduced):
#5  QWindow::screen (this=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qwindow.cpp:2200
#6  0x00007ad446bcf1ac in QPlatformWindow::screen (this=this@entry=0x557514903420) at /usr/src/debug/qt6-base/qtbase/src/gui/kernel/qplatformwindow.cpp:70
#7  0x00007ad4474ab86a in QtWaylandClient::QWaylandWindow::calculateScreenFromSurfaceEvents (this=0x557514903410) at /usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:554
#8  0x00007ad4474b849a in QtWaylandClient::QWaylandWindow::handleScreensChanged (this=0x557514903410) at /usr/src/debug/qt6-wayland/qtwayland/src/client/qwaylandwindow.cpp:1446
#9  0x00007ad4463b1a49 in QtPrivate::QSlotObjectBase::call (this=<optimized out>, r=<optimized out>, a=<optimized out>, this=<optimized out>, r=<optimized out>, a=<optimized out>) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:486


Reported using DrKonqi
Comment 1 mitchell 2025-02-23 08:46:13 UTC
Created attachment 178761 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 cwo 2025-02-23 21:12:50 UTC
Thank you for the bug report! This issue is already being tracked; marking as a duplicate.

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