https://bugs.kde.org/show_bug.cgi?id=473734

            Bug ID: 473734
           Summary: Screen not restored after awakening from hibernate
    Classification: Plasma
           Product: kwin
           Version: 5.27.7
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: wayland-generic
          Assignee: kwin-bugs-n...@kde.org
          Reporter: sk.griffi...@gmail.com
  Target Milestone: ---

Created attachment 161164
  --> https://bugs.kde.org/attachment.cgi?id=161164&action=edit
journalctl log

created in response to bug https://bugs.kde.org/show_bug.cgi?id=473235 being
labelled not a bug

In many cases after hibernating/waking from sleep, I get a blank screen. In
past kde versions, switching tty session usually solved the issue. For example,
switching back and forth once would lead to screen with artefacts, then
repeating it couple of times restored the display. In the latest version, no
amount of switching helps, since I can only get screen with artefacts, and only
solutions appear to be restarting kwin, or resetting AMD driver, both of which
end the applications running in that session (which is undesirable).

STEPS TO REPRODUCE
1. Hibernate plasma
2. Restart computer 

OBSERVED RESULT
The screen is blank. On switching between ttys, screen artefacts appear
(unusable with horizontal banding in entire screen). Resolved by restarting
kwin. Replicable about 50% of times. No particular trigger or cause that I
could identify

EXPECTED RESULT
Everything should be restored as normal

SOFTWARE/OS VERSIONS
Linux Kernel Version: 6.4.6-1-MANJARO (64-bit)
AMD driver: amdgpu
Mesa version: 23.0.2-2
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
GPU: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360]

ADDITIONAL INFORMATION
Attaching journalctl from a few minutes before hibernating until restoring
plasma session. Awekening from hibernate starts at Aug 25 01:24:56

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to