Created attachment 150492 [details] 00-system.jpg SUMMARY: Icons and Widgets Move After Logout DESCRIPTION: When using a 4K monitor as the primary display, logging in and back out moves widgets and icons on the desktop file. STEPS TO REPRODUCE 1. Attach a 4K display to the system and boot up. - DO NOT change DPI or global scaling See 01-fonts-dpi.jpg and 02-screens.jpg 2. Set 4K display as primary, see 02-screens.jpg 3. Place widgets on the desktop 4. Logout and back in. OBSERVED RESULT 1. Notice widgets have moved substantially, see 03-manual-widgets.jpg 2. Themed layouts show the same behavior as shown in 04-layout-widgets-pre.jpg and 05-layout-widgets-post.jpg EXPECTED RESULT Widgets should NOT move from their placements. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.3 See 00-system.jpg for more details. ADDITIONAL INFORMATION Running Plasma over X: xserver-xorg/jammy,now 1:7.7+23ubuntu2 This is reproducible over all 5 laptop hardware platforms running this software load. The laptop panel show here is QHD, but we have seen similar behavior with FHD. We have also observed similar behavior on a single panel QHD laptop. Related tickets: 456049 marked duplicate of 425368
Created attachment 150493 [details] 01-fonts-dpi.jpg
Created attachment 150494 [details] 02-screens.jpg
Created attachment 150495 [details] 03-manual-widgets.jpg
Created attachment 150496 [details] 04-layout-widgets-pre.jpg
Created attachment 150497 [details] 05-layout-widgets-post.jpg
Hi Bug Triage: I know this is very similar to other bugs, however, we tried to be as precise as possible and eliminate unknowns to help sort our what could be the issue. For example, we were sure to note our DPI settings (default, not set) and global scale (default, 100%). We also used a very common theme (Breeze Dark) to avoid any interference from any custom layouts. We also reproduced this with manually placed widgets to avoid any possibility that this could be layout-induced. We filed specifically against 5.24.5 LTS, and we added annotated screen shots as well. I hope you find this useful. Sincerely, Mike
This is almost certainly gonna be Bug 413645, which is just a longstanding issue that someone needs to finally fix.
I can reproduce the issue with those steps. It does seem to be the same as Bug 413645. I'll mark it as a duplicate, and make a note in there pointing to a reproducible case here. Thanks! *** This bug has been marked as a duplicate of bug 413645 ***