Bug 456497 - Icons and Widgets Move on Second Monitor
Summary: Icons and Widgets Move on Second Monitor
Status: RESOLVED DUPLICATE of bug 413645
Alias: None
Product: plasmashell
Classification: Plasma
Component: Desktop Containment (show other bugs)
Version: 5.24.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-09 03:09 UTC by Michael Mikowski
Modified: 2022-07-21 19:31 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
00-system.jpg (66.64 KB, image/jpeg)
2022-07-09 03:09 UTC, Michael Mikowski 		Details
01-fonts-dpi.jpg (56.51 KB, image/jpeg)
2022-07-09 03:10 UTC, Michael Mikowski 		Details
02-screens.jpg (53.18 KB, image/jpeg)
2022-07-09 03:10 UTC, Michael Mikowski 		Details
03-manual-widgets.jpg (85.72 KB, image/jpeg)
2022-07-09 03:12 UTC, Michael Mikowski 		Details
04-layout-widgets-pre.jpg (86.29 KB, image/jpeg)
2022-07-09 03:13 UTC, Michael Mikowski 		Details
05-layout-widgets-post.jpg (84.81 KB, image/jpeg)
2022-07-09 03:13 UTC, Michael Mikowski 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Mikowski 2022-07-09 03:09:57 UTC 
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
Comment 1 Michael Mikowski 2022-07-09 03:10:29 UTC 
Created attachment 150493 [details]
01-fonts-dpi.jpg
Comment 2 Michael Mikowski 2022-07-09 03:10:57 UTC 
Created attachment 150494 [details]
02-screens.jpg
Comment 3 Michael Mikowski 2022-07-09 03:12:46 UTC 
Created attachment 150495 [details]
03-manual-widgets.jpg
Comment 4 Michael Mikowski 2022-07-09 03:13:22 UTC 
Created attachment 150496 [details]
04-layout-widgets-pre.jpg
Comment 5 Michael Mikowski 2022-07-09 03:13:47 UTC 
Created attachment 150497 [details]
05-layout-widgets-post.jpg
Comment 6 Michael Mikowski 2022-07-12 00:20:24 UTC 
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
Comment 7 Nate Graham 2022-07-13 21:05:00 UTC 
This is almost certainly gonna be Bug 413645, which is just a longstanding issue that someone needs to finally fix.
Comment 8 Nate Graham 2022-07-21 19:31:28 UTC 
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 ***