Bug 488170 - Starting the system with the main monitor and turning on a second monitor after that, misaligns the desktop background. Just a visual bug, everything is still fully functional.
Summary: Starting the system with the main monitor and turning on a second monitor aft...
Status: RESOLVED DUPLICATE of bug 487717
Alias: None
Product: plasmashell
Classification: Plasma
Component: "Manage Desktop and Panels" window (show other bugs)
Version: git-stable-Plasma/6.1
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-07 16:36 UTC by Sodium
Modified: 2024-06-10 19:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Both monitors, left one with the misaligned background (3.84 MB, image/png)
2024-06-07 16:47 UTC, Sodium
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sodium 2024-06-07 16:36:14 UTC
SUMMARY
Starting the system with the main monitor and turning on a second monitor after that, misaligns the desktop background. Just a visual bug, everything is still fully functional.

STEPS TO REPRODUCE
1. Starting the system + KDE on the main monitor
2. Turning on the second monitor after start
3. 

OBSERVED RESULT
Background misaligned on the second desktop

EXPECTED RESULT
Background should be covering the whole second desktop

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.9.3-arch1-1 (64-bit) 
(available in About System)
KDE Plasma Version: 6.0.90
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION
Wayland with the Nvidia 555 beta drivers, issue wasn't present in the stable versions.
Comment 1 Sodium 2024-06-07 16:47:35 UTC
Created attachment 170231 [details]
Both monitors, left one with the misaligned background
Comment 2 Nate Graham 2024-06-10 19:21:02 UTC
Looks like the same root cause as Bug 487717, which will be fixed in the final release of Plasma 6.1. However if after upgrading to Plasma 6.1, you discover that this issue is still present, feel free to re-open this bugzilla ticket. Thanks a lot!

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