Summary: | Physical arrangement config data is not stored systemwide, but it should be, since this will never change on a per-user basis | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Tim Richardson <tim> |
Component: | kcm_kscreen | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
Status: | CONFIRMED --- | ||
Severity: | wishlist | CC: | nate, plasma-bugs-null, tim |
Priority: | NOR | Keywords: | usability |
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=382090 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Tim Richardson
2019-04-30 22:14:41 UTC
Are you able to reproduce this issue in Plasma 5.17? When making a new user in 5.17.5, the problem did not occur, but the monitor setup was not cloned from the existing session. The primary monitor was maintained, but the second monitor was incorrectly oriented (it appeared on the wrong side). The closed laptop monitor was disabled. So it was not a broken experience, but it is still not quite right ... it seems to me that the parent sesssion's monitor arrangement should be copied to the new user account. Thanks! This could be Plasma, it could be ksmserver, or it could be KScreen. Putting it in KScreen for now. > it seems to me that the parent sesssion's monitor arrangement should be copied to the new user account
That's not the worst idea, but then they could subtly drift out of sync over time.
Really what we need is for the physical arrangement and orientation to be stored systemwide. Then individual users could configure things like resolution, refresh rate, scale factor etc. according to their taste.
|