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 663719 - cannot leave screen running
cannot leave screen running
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Power
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: Richard Hughes
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-11-09 18:25 UTC by Pierre Ossman
Modified: 2013-02-11 13:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pierre Ossman 2011-11-09 18:25:02 UTC
The screen "Turn off after" setting does not have a "never" option, which it really should. I often have the laptop sitting on the desk next to me with something running that I want to be able to continue monitoring, without having to wiggle the pointer now and then.

It should also be possible to configure different policy for when the machine is on battery and when it is on AC, as the need to save power is different.
Comment 1 stench 2011-12-09 21:56:10 UTC
I have found and tested a workaround, since the devs will probably decide that this isn't a bug. 

You can suspend the processes named gnome-power-manager and gnome-screensaver. You will find both running, and you need to suspend both. This can be done from the System Monitor, or from the command line (Terminal).
Comment 2 collura 2012-01-16 22:33:30 UTC
all i know is that i have a lot of users that arent going to be able 
to navigate a dconf editor and change 
the org.gnome.desktop.screensaver.lock-delay item
or suspend a process. ;')

the way those users seem to be able to access it using the main settings gui has 
  turnoff: 1m, ... , 1h
  lock: 30s, 1m, ... , 1h

maybe a way could be to have a passthrough in the settings gui so they dont have
to figure out what other program the need to launch and figure out where
they need to navigate to in the dconf editor or mess with processes?

so if the user selects 'custom' from a main settings gui pulldown 
a second set of pulldowns one with 0..999 and and one with units h/m/s

they could put in the value right there and they are done
without any menu navigation or terminal windows.

user sees it as easy peasy compared to current ways :')
Comment 3 Sam Thursfield 2013-02-06 23:39:32 UTC
There is a clear need for a "Never" option for the "Turn screen off when inactive for..." setting. Some users are able to turn their screen off manually and do not need a daemon to do it for them at the wrong time.

Although we can inhibit turning off the screen when e.g. a movie is playing, this is just a crude heuristic and we cannot rely on it for all use cases. A maximised browser window and no input may mean the user has gone to lunch, or that they are using the web page for reference while doing some activity outside the computer. There's no way automatic way to find out, so there needs to be a manual override and setting the "Turn screen off..." option to "Never" is the obvious answer.
Comment 4 Nathan Eady 2013-02-07 17:01:01 UTC
I've got another use case:  public-use computers (for library catalog or for internet or whatever) at a public library.  If the screen goes blank people don't realize it's available for use, at which point the system may just about as well shut down for the night.  I can fix this in dconf now that I know what the setting is, but having a "never" option would save every single person who runs into this issue 5-10 minutes of research.

The list of choices also seems odd.  I'd consider "2 minutes" and "3 minutes" to be far too similar to warrant the inclusion of both, and the same for "5 minutes" and "10 minutes", but I wonder why there aren't options for 5 hours and 12 hours.
Comment 5 Bastien Nocera 2013-02-11 13:35:54 UTC
GNOME 3.8's Power panel will have a "Never" option for the "Blank Screen" option.