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

            Bug ID: 408677
           Summary: Screen sometimes comes up black from suspend when
                    suspending with external screen connected
           Product: kwin
           Version: 5.14.5
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: kwin-bugs-n...@kde.org
          Reporter: p...@ralfj.de
  Target Milestone: ---

SUMMARY
Sometimes, when I (in quick succession) unplug the external screen and suspend
my laptop by closing the lid, when I resume the laptop, the internal screen is
just black.

This is a critical bug that leads to data loss because I have to hard-kill the
KDE session.


STEPS TO REPRODUCE
1. Have an external screen connected and but the desktop exclusively there (so
the internal screen is disabled).
2. Unplug the screen and suspend the machine in quick succession. Unfortunately
I have not found a way to reproduce this.
3. Resume the machine.

OBSERVED RESULT
The internal screen comes back black.


EXPECTED RESULT
The internal screen should be enabled properly when coming back from suspend.

SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux 10
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-5-amd64
OS Type: 64-bit

ADDITIONAL INFORMATION

Connecting an external screen to HDMI shows that the image is still on that
port. But of course when I am traveling at that point, I don't usually have an
external screen in my luggage...

Ctrl-Alt-Fn still switches to a normal terminal session, but switching back to
X11 does not fix the issue. I can blindly unlock the screen, open a terminal
and type "touch xx" to see (in the terminal) that this actually happens. But I
found no way to enable the screen so far. I tried "xrandr -q".  ("xbacklight"
does not work at all on my laptop so I couldn't try that.)

I have used Gnome on this laptop for a year and this has not happened a single
time. Hence I think that this is an issue in KDE, not in the drivers.

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

Reply via email to