https://bugs.kde.org/show_bug.cgi?id=353975
Alexey Chernyak <alexey_...@chernyak.id.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexey_...@chernyak.id.au
--- Comment #193 from Alexey Chernyak <alexey_...@chernyak.id.au> ---
Bug still present in X11 Plasma 5.25.3.
The bug is triggered depending 3 things:
1. Which monitor is set as the X Primary Display for X Screen (not sure if
Wayland has a similar concept)
2. Which monitor wakes up first from sleep
3. Which monitor is configured to have Plasma Taskbar.
Reproducible: Always
Steps to reproduce:
1. Get 2 different monitor models that have different sleep/wakeup latency - in
my case both are DisplayPort with different resolutions. My understanding is
that DisplayPort sleep/wakeup is equivalent to disconnectintg/reconnecting
cable.
2. Set the faster waking monitor as the Primary Display for X Screen - in my
case I can do this with a tick-box in NVIDIA Settings application.
3. Place Plasma Taskbar onto the non-Primary monitor.
4. Leave system idle until both monitors go to sleep - in my case system itself
doesn't sleep, only monitors and no screen locking.
5. Wake monitors up.
Actual Results:
Monitors wake up with Plasma missing - no taskbar, no desktop icons, no
wallpaper, black screen, right click not working. Windows can be dragged
between monitors. Can Alt-Tab between windows. No DrKonqi crash reports.
During first wakeup cycle KDE screens configuration seems to get reconfigured
(depending on monitor wake-up order), and subsequent sleep/wake cycles could
have different results and screen configuration (though taskbar always missing)
depending on each pre-sleep state.
Expected Results:
Plasmashell not to disappear.
Workaround Fix:
Make the slower waking monitor as the Primary Display for the X Screen (in
NVIDIA Settings tool), and have Plasma Taskbar residing on the faster waking
screen. With this configuration every sleep/wakeup cycle works without any
issues.
--
You are receiving this mail because:
You are watching all bug changes.
