Bug 387865 - [feature request] Save various screens' profiles
Summary: [feature request] Save various screens' profiles
Status: RESOLVED NOT A BUG
Alias: None
Product: KScreen
Classification: Plasma
Component: libkscreen (other bugs)
Version First Reported In: 5.11.4
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-13 08:12 UTC by lejocelyn
Modified: 2017-12-13 10:32 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lejocelyn 2017-12-13 08:12:08 UTC
It would be nice to be able save various screens' settings profiles to allow users that move with their laptop to different office/desk situations not to have to configure each time their laptop's settings.

Example : At home I have a small secondary screen on the left of my desk. At work, I have a large secondary screen on the right of my desk. Every time I move with my laptop from home to my office, I have to configure the screens' settings. It would be nice to be able to save various screen display settings and select them. Or, in a more intuitive way, to have the software remember screen display settings depending on the screen connected (well, I'll fill a bug on this because quite often, kscreen does not refresh the screen plugged or unplugged, keeping the displayed settings from the previous screen unplugged, not the actual plugged).
Comment 1 Sebastian Kügler 2017-12-13 10:32:34 UTC
Thanks for the report!

This is done automatically. The configuration is saved as a hash of your screens connected, so it should be remembered for every individual setup you have configured at least once.

The fact that it doesn't work for you can have multiple reasons, if you're complaining that the screens are not always automatically refreshed or enabled, I'd first and foremost check that, it we don't get a "screen connected" or "setup changed" event, we can't load and apply the correct configuration.

So much for the background, and how it *should* work. Could you look at the following page and collect the debug information asked for there:

https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information

Ideally, tail -f kscreen.log while you're plugging and unplugging a screen and see what happens, there should be quite some output just by plugging in a screen, and if nothing happens then, we have the culprit. Otherwise, we know at least that we should react to something, and then maybe the reason is in the logs.

I'll close this bugreport since it's really not very useful, instead, I would like to you file a new bugreport once you collected above information.