https://bugs.kde.org/show_bug.cgi?id=503363
Bug ID: 503363
Summary: Graphics reset causes screen blackout and sometimes
lead to freezing
Classification: Plasma
Product: kwin
Version: 6.3.4
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: effects-window-management
Assignee: kwin-bugs-n...@kde.org
Reporter: kde.vacant...@passmail.net
Target Milestone: ---
SUMMARY
After a graphics reset, either a laptop screen or an external monitor attached
to it turn black, until the system is forcefully rebooted.
STEPS TO REPRODUCE
1. Use plasma with a relatively high graphics load (e.g. fast switching between
multiple windows, mostly some graphics related task in Firefox or forks) on two
screens (laptop and one external screen).
2. One of both screen blackouts and a notification pops up, "Desktop effects
were restarted due to a graphics reset"
3. Screen that blacked out doesn't "wake up" any more and remains blacked out.
Soon after, the screen looses the signal and turn in standby mode.
4. The laptop can be used normally until the next graphics reset, causing the
second screen to irrevocably turn black. Alternatively, disabling the screen in
the "Display configuration" causes the system to immediately freeze. Audio is
still being played back, but the system is completely unresponsive or heavily
delayed (in the realm of minutes).
5. Only a forced reboot solves the issue.
EXPECTED RESULT
After a graphical reset, the screen should return to its previous state and
operate normally.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux 6.14.3-arch1-1 (64-bit)
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
ADDITIONAL INFORMATION
This only happens when an external monitor is connected to my laptop. Using my
laptop screen only doesn't lead to the permanently blacked out screen.
One or two months ago, this "graphics reset" did never occur one, not even
under high graphical and CPU load. It seems a more recent update introduced
this "feature" I don't really understand in the first place, as I could not
find any information related to this.
My laptop has pretty recent hardware (2024 Q2) and features an OLED screen. I
could see that being part of the issue.
BACKTRACE
Generated with gdb with following command from the KWin/Debugging guide:
echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
sudo gdb -pid $(pidof kwin_wayland) -batch -ex "set logging file
kwin_wayland.gdb" -ex "set logging enabled on" -ex "continue" -ex "thread apply
all backtrace" -ex "quit"
https://cryptpad.fr/code/#/2/code/view/eVZeidlYQb-X3RFqw2Cj0zZna6iVBYs1qZg78m+Y3-Y/embed/
--
You are receiving this mail because:
You are watching all bug changes.
