Bug 339558 - Display module in System Settings should automatically set size to disabled when device is unplugged
Summary: Display module in System Settings should automatically set size to disabled w...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_randr (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-01 05:58 UTC by DrSlony
Modified: 2015-01-22 12:09 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description DrSlony 2014-10-01 05:58:07 UTC 
Unplugging a secondary monitor is unnecessarily complicated by having to go back to the Display module and setting the device's size to "disabled", otherwise if we just pull the cable out the device is left as enabled which can cause errors in other programs.
The program should be smart enough to automatically disable a device when it's unplugged.

Reproducible: Always
Comment 1 DrSlony 2014-10-02 06:55:47 UTC 
When I wrote this report, I only had the old "Display" module installed. Now I installed kscreen-1.0.71 and libkscreen-1.0.5.

Using kscreen the TV does automatically get disabled when unplugged without me having to manually disable it.  I confirm this by a lack of error message when applying a profile using dispcalGUI, whereas before there was an error message about the second display device missing. If the old Display module is being abandoned in favor of kscreen, then this bug report can be closed.
Comment 2 David Edmundson 2015-01-22 12:09:32 UTC 
Thanks for reporting your bug.

Since reporting Krandr has since been replaced by KScreen. It is available in the Plasma 4 series, and is default in Plasma 5 onwards.

I hope this solves your issue. If you still have a problem after upgrading please reopen a new bug under kscreen.

Thanks