Bug 485921 - Gap between two external displays appearing every time when closing the laptop
Summary: Gap between two external displays appearing every time when closing the laptop
Status: RESOLVED DUPLICATE of bug 507702
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_kscreen (other bugs)
Version First Reported In: 5.27.11
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-21 20:05 UTC by Adam
Modified: 2025-08-26 21:15 UTC (History)
2 users (show)

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

Attachments
setup after closing laptop. (71.22 KB, image/png)
2024-04-21 20:05 UTC, Adam 		Details
setup before (77.52 KB, image/png)
2024-04-21 20:06 UTC, Adam 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Adam 2024-04-21 20:05:38 UTC 
Created attachment 168761 [details]
setup after closing laptop.

SUMMARY
I have a setup with 2 external displays and one from my laptop. I only use opened laptop for bootup, then I immediately close it. Every time, since some update, there is a gap between my external monitors after I close the laptop. I need to readjust it manually by pulling the second monitor next to the 1st one.  I attached the screenshots with display setup with and without built-in display. In the 3 display setup my built-in screen is to the left, not even between externals.

OBSERVED RESULT
Setting for two external displays not saving up correctly, gap appearing every time after closing the laptop built-in display.

EXPECTED RESULT
Setting of two external displays saved.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION
Fedora Linux 39
Comment 1 Adam 2024-04-21 20:06:10 UTC 
Created attachment 168762 [details]
setup before
Comment 2 Nate Graham 2025-08-26 21:15:04 UTC 

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