Bug 388051 - Pulling the DP cable when logging off has gui in inconsistent state
Summary: Pulling the DP cable when logging off has gui in inconsistent state
Status: RESOLVED NOT A BUG
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.11.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-19 23:01 UTC by slartibart70
Modified: 2018-01-29 20:43 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description slartibart70 2017-12-19 23:01:11 UTC
Hi,
maybe this is the wrong topic to place this error to, but in lack of a better category....

I have a multimonitor setup, a lenovo t470p and an external, display-port connected fullHD monitor.
Plasma5 is working fine, no problems at all (besides the lack of proper dpi settings for the external screen)

When i finish working, i log off - ready to put my laptop to sleep by closing the lid and putting it into my backpack. Most of the time i forget that the external monitor is still connected to the DP port, which i normally discover _after_ giving the command to log off of plasma.
Pulling the cord in this specific moment (after logging off and before the sddm greeter is displayed) results in a total black screen on the laptop.

Virtual consoles (2 and up) are still available, but i couldn't figure out how to get a graphical login on vk1 back again to life.

If i pull the cord before logging of, all is fine.

Any idea how to resolve this problem?
Or, at least, how to get the sddm gui login working again?
Comment 1 David Edmundson 2018-01-22 10:50:38 UTC
Need some more info:

Is plasma still running?
Is sddm-greeter running?
Is there anything in the SDDM log? (sudo journalctl -f -u sddm)

please reset bug status when replying
Comment 2 slartibart70 2018-01-29 20:43:34 UTC
i have to withdraw the bug.
In the meantime, the update to plasma 5.11.5 does not show the bug any more, at least, i cannot reproduce it.