Comment 14 for bug 36568
Revision history for this message
| Aaron Whitehouse (aaron-whitehouse) wrote | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
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?