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 708413 - no longer able to disable screen via control center display settings
no longer able to disable screen via control center display settings
Status: RESOLVED DUPLICATE of bug 707570
Product: gnome-control-center
Classification: Core
Component: Display
3.9.x
Other Linux
: Normal normal
: ---
Assigned To: Debarshi Ray
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-09-19 20:34 UTC by Jonathon Conte
Modified: 2013-09-19 22:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jonathon Conte 2013-09-19 20:34:35 UTC
I'm running a testing version of Fedora 20 with GNOME Control Center 3.9.91. I have a laptop with Intel graphics and an external monitor connected via VGA.

In GNOME 3.8, the display settings allowed me to turn my laptop's integrated LCD panel off when my external monitor was connected. This setting was saved and automatically applied upon connecting the external monitor. When the external monitor was disconnected, GNOME automatically re-enabled my laptop's internal LCD panel. Everything worked perfectly.

After upgrading to GNOME 3.9, my monitor settings were either lost or ignored and the new Displays applet no longer gives me the ability to turn off a screen.

If I close my laptop's lid as a work-around for this regression, I no longer have access to my laptop's keyboard and touchpad (which I use). Also, my laptop does not seem to have a Function button on the keyboard that allows me to disable the laptop's screen. Finally, my laptop's wireless antenna is located in its lid so I get better reception when the lid is open.

Please enable a way to disable screens via the GNOME Control Center so that the feature that was present in GNOME 3.8 continues to work. Also, please ensure this setting is saved and automatically re-applied upon configuration changes the same way as before.
Comment 1 Debarshi Ray 2013-09-19 22:09:14 UTC

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