Bug 473220 - When displays wake up and one screen has been deactivated previously, screen layout not correctly restored until plasmashell is restarted
Summary: When displays wake up and one screen has been deactivated previously, screen ...
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Containment (other bugs)
Version First Reported In: master
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: multiscreen
: 474224 (view as bug list)
Depends on:
Blocks:
 
Reported: 2023-08-09 18:11 UTC by Malte
Modified: 2025-08-09 03:46 UTC (History)
5 users (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 Malte 2023-08-09 18:11:24 UTC
SUMMARY
I'm have 4 displays attached to my GPU: 3x Displayport for the screens in my office and 1x HDMI with a long cable to the TV in the next room. (So I can watch movies, play games in the living room in the evening)
When working on my PC I deactivate the HDMI screen as I can't see the TV and don't want to have windows, mouse etc "vanish" to a different room.
But when leave the PC for a break and return with the session locked and the displays put into sleep, and unlock the session, the screen/desktop configurations are completely messed up.

STEPS TO REPRODUCE
1. Run Plasmashell Wayland with 4 screens (haven't tested with 3 or 2, but might work as well)
2. Configure backgrounds, control bar etc. to your liking
3. Deactivate one screen in the System Settings (4->3 screens (or 3->2 screens or 2->1 screen))
4. Let the Screen Lock activate and the Screens go to sleep (Energy Savings Settings)
5. Make some inputs on the PC to wake the screens up and unlock the session

OBSERVED RESULT
The Desktop is not restored to its state before locking/screens turned off. The screens and their configuration might be shifted to different physical displays or completely missing.

Running "plasmashell --replace &" in the terminal does restore the correct configuration.
When all screens are activated, the correct desktop configuration is always restored.

EXPECTED RESULT
Even when screens are turned off, the configured desktop layout should be restored.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20230808
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.4.8-1-default (64-bit)
Graphics Platform: Wayland
Processors: 8 ร— AMD Ryzen 5 2400G with Radeon Vega Graphics
Memory: 31.2 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2023-08-09 18:40:26 UTC
See https://bugs.kde.org/show_bug.cgi?id=467422#c8, which was caused by a bad DP->HDMI cable. But in the case you're only using DP->DP and HDMI->HDMI cables, right?

Also has echoes of Bug 462316 and Bug 469192.
Comment 2 Malte 2023-08-09 18:51:26 UTC
Yeah, 3x DP<->DP cables and 1x HDMI<->HDMI cable.

Also, all screens work 100% fine when they are enabled. And it also works fine when all screens are activated in the System Settings.
Comment 3 Nate Graham 2023-08-09 19:02:27 UTC
Thanks!
Comment 4 Marco Martin 2023-08-25 13:40:15 UTC
can you compare with plasma6? (for instance with a neon unstable live image) to see if the issue still happens there, it would help narrowing the issue
Comment 5 Nate Graham 2023-08-25 13:47:37 UTC
.
Comment 6 Nate Graham 2023-09-07 16:36:13 UTC
*** Bug 474224 has been marked as a duplicate of this bug. ***
Comment 7 manrusin 2023-09-08 08:30:41 UTC
(In reply to Marco Martin from comment #4)
> can you compare with plasma6? (for instance with a neon unstable live image)
> to see if the issue still happens there, it would help narrowing the issue

Tested on live image kde neon unstable from 2023-09-07

Partially broken:
The desktop icons auto-aligned, but animations works fine

After unlocking got 3 plasmashell crashreports and all cannot be generated.
Comment 8 Nate Graham 2023-09-08 17:01:42 UTC
Ok, thanks for testing! But it sounds like those are different issues from what was originally reported here, though. We'd like to know if Malte is able to reproduce the issue in Plasma 6.
Comment 9 Bug Janitor Service 2023-09-23 03:46:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2023-10-08 03:46:10 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 11 Malte 2023-10-15 22:52:46 UTC
Sorry, didn't have time to come back to this issue until now.

I've just tested with the neon-unstable-20231015-1119 build and can confirm that the problem still exists with latest Plasma 6, so reopening.
Comment 12 TraceyC 2025-07-10 22:18:20 UTC
I'm sorry we weren't able to get to this report until now. Are you still seeing this bug with Plasma 6.4.2 or later? Thanks.
Comment 13 Bug Janitor Service 2025-07-25 03:46:40 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 14 Bug Janitor Service 2025-08-09 03:46:46 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.