Bug 479966 - Wayland: Turn off/on monitor results in kwin crash
Summary: Wayland: Turn off/on monitor results in kwin crash
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: platform-drm (show other bugs)
Version: 5.27.10
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: wayland-only
Depends on:
Blocks:
 
Reported: 2024-01-18 00:33 UTC by Jake Hutchinson
Modified: 2024-03-16 03:46 UTC (History)
1 user (show)

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


Attachments
KWin Output Config (2.64 KB, application/json)
2024-01-18 00:33 UTC, Jake Hutchinson
Details
Journalctl log (5.31 KB, text/x-log)
2024-01-18 00:34 UTC, Jake Hutchinson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jake Hutchinson 2024-01-18 00:33:45 UTC
Created attachment 164992 [details]
KWin Output Config

SUMMARY
Turning off/on primary monitor results in a black screen where kwin_wayland needs to be restarted manually. So far I've only been able to reproduce this error on my Displayport monitor and not via HDMI.


STEPS TO REPRODUCE
1. Turn off/on monitor

OBSERVED RESULT
Black screen

EXPECTED RESULT
Plasma shell

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Arch
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.114.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION
Possible duplicate of https://bugs.kde.org/show_bug.cgi?id=438839
Not sure as to why but I had this issue for awhile but It went away when I left my system on for long enough, on a restart this issue has resurfaced, whether this is related/helpful I'm not sure.
Comment 1 Jake Hutchinson 2024-01-18 00:34:11 UTC
Created attachment 164993 [details]
Journalctl log
Comment 2 Nate Graham 2024-02-15 21:06:13 UTC
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the `coredumpctl` command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!
Comment 3 Bug Janitor Service 2024-03-01 03:46:45 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:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

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 4 Bug Janitor Service 2024-03-16 03:46:59 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!