Bug 447732 - Rescale upon login causes widgets to move from their usual position
Summary: Rescale upon login causes widgets to move from their usual position
Status: RESOLVED DUPLICATE of bug 449212
Alias: None
Product: plasmashell
Classification: Plasma
Component: Desktop Containment (show other bugs)
Version: 5.23.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Marco Martin
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2021-12-31 10:18 UTC by Lyubomir
Modified: 2022-01-27 15:28 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Before scaling happens (1.91 MB, image/png)
2021-12-31 10:18 UTC, Lyubomir
Details
Plasma scaling issue (1.91 MB, image/png)
2021-12-31 10:19 UTC, Lyubomir
Details
KDE widgets posiiton and notification (1.70 MB, image/png)
2022-01-08 10:06 UTC, Lyubomir
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lyubomir 2021-12-31 10:18:25 UTC
STEPS TO REPRODUCE
1. Use a 1920x1080 display
2. Use 125% display scaling
3. Add "System Monitor sensor" widget to your desktop, in the bottom right corner, as shown in the screenshot "Before scaling happens"
4. Logout
5. Login again

OBSERVED RESULT
During the splash screen or sometimes after the display is shown a display rescale happens and the 100% display scaling changes to 125% display scaling. This causes the "System Monitor sensor" widget to move from it's regular position to the position as shown in the "Plasma scaling issue" screenshot.

EXPECTED RESULT
Upon login "System Monitor sensor" widget stays in its regular position - the bottom right corner.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.2
Kernel Version: 5.15.12-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7,6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Comment 1 Lyubomir 2021-12-31 10:18:50 UTC
Created attachment 144987 [details]
Before scaling happens
Comment 2 Lyubomir 2021-12-31 10:19:17 UTC
Created attachment 144988 [details]
Plasma scaling issue
Comment 3 Lyubomir 2022-01-08 10:06:12 UTC
Created attachment 145215 [details]
KDE widgets posiiton and notification

Not sure if it isn't the notifications fault here - steps are:
1. Splash loading screen shows after clicking login into the SDDM display manager
2. During the splash screen showing there is a rescale and it becomes bigger and more blurry
3. Then it fades away to desktop - at this moment the widgets are at their correct position
4. Then the notifications show up on the left part of the screen for a while, then move to their correct position to the right.
It is that moment when they move to the correct position in the right when the widgets "make place" for the notification.

But please note that if i then go and move the widgets back to the very corner of the screen, where they should be, further notifications don't move the widgets but display over them.

So if it is the notifications - then it's only the first ones right after login that are moving from the left of the screen to the right.
Or it's simply because of the rescale during the splash screen - but if so then why after it fades to desktop the widgets are initially in their correct position?
Comment 4 Marco Martin 2022-01-13 09:34:48 UTC
Happens only on Wayland on on X11 too?
Comment 5 Lyubomir 2022-01-13 17:41:05 UTC
Only on Wayland
Comment 6 Lyubomir 2022-01-13 17:42:43 UTC
I believe there is no such rescale on X11, on X11 the widget does not move away from its position on the first notification.
Comment 7 Lyubomir 2022-01-27 09:54:26 UTC
I've moved the widget into the taskbar itself, now i notice the taskbar is not only blurry, but also rescales itself (starts small, then grows) and covers the bottom part of some apps (i.e. it covers the Firefox find bar & the last line of Konsole).

Not really sure if the rescaling is somehow connected to the widget, will have to experiment some more.
Comment 8 Nate Graham 2022-01-27 15:28:16 UTC

*** This bug has been marked as a duplicate of bug 449212 ***