Bug 444581 - [Multi-monitor] Mispositioned content of splash screen (not only splash is affected though)
Summary: [Multi-monitor] Mispositioned content of splash screen (not only splash is af...
Status: RESOLVED LATER
Alias: None
Product: KScreen
Classification: Plasma
Component: common (other bugs)
Version First Reported In: 5.23.2
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-29 06:00 UTC by Vladimir Yerilov
Modified: 2021-10-29 11:04 UTC (History)
0 users

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


Attachments
a cropped and resized screenshot of the right screen (198.34 KB, image/png)
2021-10-29 06:00 UTC, Vladimir Yerilov
Details
monitors configuration (82.28 KB, image/png)
2021-10-29 06:02 UTC, Vladimir Yerilov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Yerilov 2021-10-29 06:00:32 UTC
Created attachment 142987 [details]
a cropped and resized screenshot of the right screen

SUMMARY
If there's an empty space between screens, Plasma acts weird when logging in: the content of another monitor is shifted filling that gap. It's easily observable when using a splash screen, but reproducible even without that.

STEPS TO REPRODUCE
1. Set your screens to have a space between them.
2. Log out.
3. Log in.

OBSERVED RESULT
See that there's a panel in the top-right corner? Below that there's a pile of desktop wallpaper. The area to the left is covered by the splash screen. Every time I log in this happens. Turning splash off can't help because when it's off Plasma wallpaper acts the same way.

EXPECTED RESULT
Kscreen settings (including screens' position) should be honored from the very beginning of Plasma start-up.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Vladimir Yerilov 2021-10-29 06:02:37 UTC
Created attachment 142988 [details]
monitors configuration

This is a configuration of screens that results in this weird behavior I described above.
Comment 2 Vladimir Yerilov 2021-10-29 11:04:59 UTC
Strange, now it's gone.
All I did was updating qt5-wayland (unlikely related, because the issue was observed in X session) and downgrading nvidia driver from 495 to 470 series -- probably has no relation too since this is an Optimus laptop and it is Intel's iGPU job to render the desktop, not Nvidia's dGPU one.