Bug 399956 - On a newly installed system, multiple display arrangement is not remembered after restart
Summary: On a newly installed system, multiple display arrangement is not remembered a...
Status: RESOLVED DUPLICATE of bug 398816
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.13.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-18 03:47 UTC by Tyson Tan
Modified: 2018-10-18 19:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tyson Tan 2018-10-18 03:47:38 UTC
SUMMARY
On a newly installed system, multiple display arrangement is not remembered after restart. Display arrangement buttons are being displayed upon every login, as if a new monitor is being connected while the system is running.

To rectify this, user must click the display arrangement button once, like "Unify" but not "Keep unchanged". After that the arrangement can be remembered. If the user press "Keep unchanged" button, the same thing will happen every time upon login.

STEPS TO REPRODUCE
1. Fresh install Manjaro 17.1.12 KDE on a multiple display PC
2. Change display arrangement in System Settings
3. Restart

OBSERVED RESULT
Display arrangement is not remembered. Display arrangement buttons are being displayed upon every login, as if a new monitor is being connected while the system is running.

To rectify this, user must click the display arrangement button once, like "Unify" but not "Keep unchanged". After that the arrangement can be remembered. If the user press "Keep unchanged" button, the same thing will happen every time upon login.

EXPECTED RESULT
On a newly installed system, multiple display arrangement is remembered after restart

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2018-10-18 19:54:01 UTC

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