It is unclear that the screen-blanking time is in addition to setting in gnome-screensaver

Bug #36568 reported by Aaron Whitehouse on 2006-03-25
24
Affects Status Importance Assigned to Milestone
gnome-power
Fix Released
Wishlist
gnome-power-manager (Ubuntu)
Medium
Unassigned

Bug Description

I just upgraded to Dapper Flight 5 and have downloaded all updates to 25/03.

I have set the preferences of GPM to blank the screen after 1min of inactivity (for both on AC and on battery) and, regardless of whether it is on AC or on battery, it sits there without blanking (I left it about 10 mins).

Please let me know any information you require.

Note: This worked on Breezy. Also, if I set the screen to blank when the lid is closed, and I close the lid, it blanks as expected.

Richard Hughes (richard-hughes) wrote :

What's the idle time in gnome-screensaver-preferences?

10 minutes

Richard Hughes (richard-hughes) wrote :

If you wait 12 minutes, does it work? g-p-m's timer of "1 minute" only starts counting when gnome-screensaver declares the session "idle" which is happeneing after 10 minutes of not moving the mouse... maybe this is unclear and should be put into the UI or at least the yelp file.

Ah yes, that was exactly the case. It went off after 10 + 1 minutes and, when I change the time for the screensaver, the blanking time changes with it.

I definitely think you need to make that clearer, I had no idea that they were associated. Perhaps show the total time in GPM (screensaver + X), have some connection to gnome-screensaver so that you can adjust them in concert, or at least change the wording in the message.

Richard Hughes (richard-hughes) wrote :

>I definitely think you need to make that clearer

Can you open an upstream bug please, so the other developers can discuss how best to fix this: http://bugzilla.gnome.org/enter_bug.cgi?product=gnome-power-manager

Please link the upstream bug to this one.

Many thanks.

Richard.

Changed in gnome-power-manager:
status: Unconfirmed → In Progress
Richard Hughes (richard-hughes) wrote :

You might want to try out CVS HEAD, as now the gnome-screensaver time is the start of the gnome-power-preferences slider. I just need to update the FAQ and the yelp file and then this should be good to close.

excuse me but I need to ask you a question:
what would happen in this case:
When I'm connected to the AC I want the display to be put to sleep
after 30 minutes, because when I work it may happen that I skpeak for
a while to my collegues, describing what the monitor shows.
Instead when I'm on battery I need to switch off the display as soon
as possible, to save power.
so this 2 things are conflictuous, because gnome-screensaver time has
to be added!
I thought that disabling it would have been the best solution but...
first of all the preferences depend on gnome-screensaver even if it is
not enabled, but this is not a big problem, since I don't want to
black my screen after 1 minute (which can't be done now)
the sencond problem is that if I want to block the screen after that
period, I can't! because there's no option (even in gconf if I disable
lock_use_screensaver_settings) and if the screensaver is disabled the
screen is not locked!

I think we should reconsider the case that putting the display to
sleep don't have to include screensaver time...

On 4/3/06, Richard Hughes <email address hidden> wrote:
> You might want to try out CVS HEAD, as now the gnome-screensaver time is the start of the gnome-power-preferences slider. I just need to update the FAQ and the yelp file and then this should be good to close.
> --
> It is unclear that the screen-blanking time is in addition to setting in gnome-screensaver
> https://launchpad.net/malone/bugs/36568
>

> When I'm connected to the AC I want the display to be put to sleep
> after 30 minutes, ...
> Instead when I'm on battery I need to switch off the display as soon
> as possible, to save power.

As I understand things, this isn't a problem. You could set the gnome-screensaver preference to 1 minute, the gnome-power-manager battery blanking preference to 1 minute (so it will happen after 2 minutes - 1 + 1) and the gnome-power-manager AC blanking preference to 29 minutes (so it blanks after 29 + 1 = 30 minutes).

I agree that it isn't good, but if you read the 'watched' bug:
http://bugzilla.gnome.org//show_bug.cgi?id=336061
you see that there isn't much that they can do about it at this stage. I too would like it to be independent, but I got a no-can-do on that from upstream.

The locking issue is a different issue and you should file it as a different bug, but I am guessing that being forced to use gnome-screensaver is going to stop it being a problem.

Sorry - I forgot to mention, Nicolo, that you will need to uncheck the box in Gnome-Screensaver saying 'activate the screensaver when session is idle' or you will have the screensaver on for 29 minutes of your AC time!

Because, as you say, you can't have both the screensaver disabled and the 'lock on screensaver' option on, you are correct that there is now no way to make the screen lock when blanking, so perhaps you should file a bug.

Nicolò Chieffo (yelo3) wrote :

unfortunately I can't, because if I do so, when I'm explaining a
slide, which have to be constantly shown on my display, if I don't
move the mouse every minute I get the screen locked!
anyway, if they can't do anything else for now...
but wait a minute... they say they take the idle time from
gnome-screensaver, but of course gnome-screensaver can't ask itself
the idle time, it must ask someone-else for it! and so why don't they
use the same method for gpm??
--
> It is unclear that the screen-blanking time is in addition to setting in gnome-screensaver
> https://launchpad.net/malone/bugs/36568
>

Nicolò Chieffo (yelo3) wrote :

Ah! I read now your second comment! so, you know, I have to change
settings every time I plug/unplug the AC, which is not what a user
wants, in my opinion

moreover, try to do so:
1) uncheck activate the screensaver when session is idle
2) set screensaver time to 2 hours
3) set the "display sleep time" to 1 minute and notice that even if
screensaver is disabled you have to wait 2 hours and 1 minute to get
your display off!

--
It is unclear that the screen-blanking time is in addition to setting
in gnome-screensaver
https://launchpad.net/malone/bugs/36568

Guys, have you read the yelp help file, particulally the "Screen Locking" section?

Apologies Richard, the yelp file does explain how to lock the screen.

I have done a lot of thinking about this bug since I posted it and I think that I have come up with an optimal solution. Let me first explain what I see as the essential problem:
- It would make more sense to all involved if g-p-m had nothing to do with gnome-screensaver, but that isn't possible because g-p-m wants to use the gnome-screensaver monitor for whether the session is idle. The gnome-screensaver is essentially a binary announcement which only occurs once the setting has been idle for the time set in the screensaver settings, so it is only after this time that gpm can start counting.

Wouldn't it be an ideal solution if gnome-screensaver could be modified to announce (via DBUS or otherwise) how many minutes there had been no activity. Every minute there could be a:
Inactivity = 60
Inactivity = 120
...

This would mean that the screensaver could be set to come on (or become 'idle') at whatever time, but gpm could independently watch this channel and perform power management functions irrespective of the settings for the screensaver. This would allow gpm to avoid duplicated effort and use the idle from gnome-screensaver, but would give the benefits of independence. What are your thoughts on this approach?

Nicolò Chieffo (yelo3) wrote :

my thought is that indipendency is the to be resolved as soon as
possible, and any approach is welcome :)

On 4/4/06, Luna-Tick <email address hidden> wrote:
> Apologies Richard, the yelp file does explain how to lock the screen.
>
> I have done a lot of thinking about this bug since I posted it and I think that I have come up with an optimal solution. Let me first explain what I see as the essential problem:
> - It would make more sense to all involved if g-p-m had nothing to do with gnome-screensaver, but that isn't possible because g-p-m wants to use the gnome-screensaver monitor for whether the session is idle. The gnome-screensaver is essentially a binary announcement which only occurs once the setting has been idle for the time set in the screensaver settings, so it is only after this time that gpm can start counting.
>
> Wouldn't it be an ideal solution if gnome-screensaver could be modified to announce (via DBUS or otherwise) how many minutes there had been no activity. Every minute there could be a:
> Inactivity = 60
> Inactivity = 120
> ...
>
> This would mean that the screensaver could be set to come on (or become 'idle') at whatever time, but gpm could independently watch this channel and perform power management functions irrespective of the settings for the screensaver. This would allow gpm to avoid duplicated effort and use the idle from gnome-screensaver, but would give the benefits of independence. What are your thoughts on this approach?
> --
> It is unclear that the screen-blanking time is in addition to setting in gnome-screensaver
> https://launchpad.net/malone/bugs/36568
>

See the remote bug. A fix has been released which means that GPM displays the total time from inactivity to blanking, rather than that additional to gnome-screensaver's time.

Changed in gnome-power-manager:
status: In Progress → Fix Committed

This has made it into Edgy - as I wrote upstream, I would prefer it if GPM was not constrained by Gnome-Screensaver's setting, but at least it is now included in the time displayed.

Changed in gnome-power-manager:
status: Fix Committed → Fix Released
Marcelo Atie (marceloatie) wrote :

I prefer 5,
so i think that be able to put a value up to 1 will be ok to everyone

Changed in gnome-power:
importance: Unknown → Wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.