After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 618875 - gnome-display-properties should not allow disabling the only monitor
gnome-display-properties should not allow disabling the only monitor
Status: RESOLVED INCOMPLETE
Product: gnome-control-center
Classification: Core
Component: Display
2.30.x
Other Linux
: Normal major
: ---
Assigned To: Soren Sandmann Pedersen
Control-Center Maintainers
Depends on:
Blocks: randr-tracker
 
 
Reported: 2010-05-17 12:43 UTC by Jean-François Fortin Tam
Modified: 2010-06-15 20:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jean-François Fortin Tam 2010-05-17 12:43:53 UTC 
When there is only one monitor/screen in gnome-display-properties, it makes no sense to have the Enable/Disable radiobutton group.

Disabling the only screen you have makes no sense, but I actually had newbie users report doing exactly that, and, of course, once the screen goes black, panic ensues (and users who see a black screen are not going to wait 30 seconds).

Proposed solution: if there's only one screen shown in gnome-display-properties, set the Enable/disable option group to be gtk insensitive.
Comment 1 Jean-François Fortin Tam 2010-05-17 12:58:13 UTC 
P.s.: this is partially related to bug #560827, in the sense that gnome should reset the monitors if it detects nonsense (like no active monitor at all) at login time... but not quite the same thing, since bug #560827 is about "parsing nonsense" while the bug report here is about not allowing it to happen (in a specific case) in the first place.
Comment 2 Federico Mena Quintero 2010-05-18 17:04:34 UTC 
Hmm, if I only have a single monitor, then the on/off radiobuttons are insensitive.  Is this not working for you?

Can you please provide a screenshot of gnome-display-properties and the output of "xrandr -q"?
Comment 3 Jean-François Fortin Tam 2010-06-15 20:13:36 UTC 
Ok, so the user that reported this to me doesn't have access to that particular computer anymore, so I will not be able to troubleshoot this/provide the requested information (and from my limited testing, this didn't happen on my hardware).