Want to make use of the inhibition logic shall take an inhibitor lockĭate: Wed, 00:36:56 +0100 On Tue, at 03:06:36PM -0800, Jamie Zawinski wrote:
Suspend, and delay the suspend until that's complete. > It proceeds not to actually mention any one of those nicer interfaces.Ī screen lock tool wants to bring up the screen lock right before > resume, there are much nicer interfaces available. > applications want to be notified of system suspend/hibernation and > intended for local use only and should be considered hacks. > Note that scripts or binaries dropped in /lib/systemd/system-sleep/ are > is to put something in /lib/systemd/system-sleep/, yet the systemd-sleep > Fun fact: the latter method I found is already obsolete. It proceeds not to actually mention any one of those nicer interfaces.ĭate: Sun, 22:51:18 +0100 On Sun, at 10:39:10PM +0100, Josip Rodin wrote: Resume, there are much nicer interfaces available.
IfĪpplications want to be notified of system suspend/hibernation and Intended for local use only and should be considered hacks. Note that scripts or binaries dropped in /lib/systemd/system-sleep/ are Is to put something in /lib/systemd/system-sleep/, yet the systemd-sleep laptops suspending isn't really a niche use case these days.įun fact: the latter method I found is already obsolete. > provide examples, and add some package relationships to indicate what should > The xscreensaver package should probably document some of these options, > * a pm-utils package which provides a hooking mechanism in > * a xss-lock package that subscribes to Linux power events more > trying to use to get this working, e.g.: > Apparently there's a whole little cottage industry of ways people have been I also gather that there is little agreement between the various Linux distros as to what that script is called or how you install it.Īnother workaround, of course, is to lock your screen before closing the lid.ĭate: Sun, 22:39:10 +0100 On Sun, at 07:21:52PM +0100, Josip Rodin wrote: I gather that some Linux systems have a way for a script to run between steps 2 and 3, to run "xscreensaver-command -lock" and wait for it to complete before halting the CPU, which would solve this problem. What you are experiencing is the gap between steps 7 and 10. Ii google-chrome-stable [ii iceweasel [pn qcam | streamer ĭate: Sun, 12:29:26 -0700 So what's happening is this:ħ: X server redraws the previous screen contents.Ĩ: oh hey, the screen is still not locked, because the machine is just like it was before, except now the disk is thrashing.ĩ: eventually xscreensaver gets scheduled again, and notices that the clock has jumped.ġ0: xscreensaver says "oh shit!" and locks the screen. Versions of packages xscreensaver suggests: Versions of packages xscreensaver recommends: Versions of packages xscreensaver depends on: Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Thanks for looking into this, and thanks for your work on xscreensaverĪPT policy: (500, 'testing-updates'), (500, 'testing') Issue, especially for laptop user who's likely to use suspend and have (theoretically even kill the screensaver daemon) before the screenĪctually goes to screensaver+lock (again, in that split second not there is a half-second during which the scrennsaver+lock is notĪctive, meaning 1- one can see the contents of the desktop and openĪpplications 2- one can actually interact and issue a command have xscreensaver started with lock after n minutes
0 kommentar(er)
