https://bugs.kde.org/show_bug.cgi?id=476341
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xaver.h...@gmail.com
Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org
Product|plasmashell |kwin
Summary|After disabling laptop |After disabling laptop
|screen while external |screen while external
|screen is connected, |screen is connected,
|re-enabling laptop screen |re-enabling laptop screen
|makes it lose its Plasma |using KScreen KCM (not the
|containment until system is |applet) makes it lose its
|rebooted |Plasma containment until
| |system is rebooted
Target Milestone|1.0 |---
Component|Desktop Containment |multi-screen
--- Comment #4 from Nate Graham <n...@kde.org> ---
Found the way to reproduce it reliably:
1. Have a laptop (it has a 4k screen normally run at 200% scale)
2. Plug in an external HDMI screen, either directly, or via a DisplayPort
dongle (doesn't seem to make a difference)
3. Use the KScreen applet to invoke "Switch to External Screen" mode. The
laptop screen correctly turns off
4. Open the KScreen KCM (*not* the applet) and manually re-enable the disabled
laptop screen
5. Experiencing the freeze described in Bug 476342; switch to another VT and
then back to recover
Result: the laptop screen is turned on, but its' lost its containment. So what
happens to the Plasma containment is different when enabling that containment's
screen from the KCM vs using the applet's "Extend to left" or "Extend to right"
feature.
--
You are receiving this mail because:
You are watching all bug changes.
