Bug 451449

Summary:	Wayland desktop panel doesn't follow primary screen when external primary screen is turned off and back on again
Product:	[Plasma] plasmashell	Reporter:	galder <lemmyg>
Component:	Containment	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	aleixpol, nate, notmart
Priority:	NOR	Keywords:	wayland-only
Version First Reported In:	5.24.90
Target Milestone:	1.0
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	5.27
Sentry Crash Report:

Description galder 2022-03-13 13:49:12 UTC

SUMMARY
My setup is one laptop screen and a external monitor(primary screen) and just a single desktop panel.
When I start the session the  panel appears in the external monitor what is correct.
When I disconnect the monitor, the panel moves to the laptop screen what is correct too.
But when I connect again the external external screen the panel doesn't move automatically to the external screen(primary). Stays in my laptop screen. Finally forcing me to restart the session in other to relocate the panel the correct position.



STEPS TO REPRODUCE
1. disconnect the external screen(primary).
2. the panel moves to the laptop screen.
3. reconnect the external screen(primary).
4. the panel stays in the laptop screen.

OBSERVED RESULT
the panel stays in the laptop screen(Wayland)

EXPECTED RESULT
the panel moved automatically to the external screen(primary) as it does in x11

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.10
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-35-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630

ADDITIONAL INFORMATION

Comment 1 galder 2022-06-12 19:25:41 UTC

This issue still exists in 5.25.0

Comment 2 Nate Graham 2023-04-27 16:15:04 UTC

This should be fixed as of Plasma 5.27; can you test again? If not, I'll troubleshoot it in detail with you.

Comment 3 galder 2023-04-27 16:23:22 UTC

yep, is fixed in 5.27.

Regards,
Galder

Comment 4 Nate Graham 2023-04-27 16:25:40 UTC

Great!