Jamie Zawinski <[EMAIL PROTECTED]> writes: > You've got some other program running that is grabbing the kbd and > preventing xscreensaver from being able to activate.
Would that also cause the problem with xscreensaver-command -exit, where xscreensaver exits (according to job control), but xscreensaver-command sits and times out without getting a response from xscreensaver? Any idea how to figure out what it is that's causing the problem? I'm not running all that much; typically sawfish, xcompmgr, conky, pidgin, xterm, emacs and iceweasel. And the problem occurs even when I kill everything but sawfish and an xterm. A 'ps -u nowan' shows a few other things (e.g., dbus & gconf stuff for pidgin, ssh-agent, and zsh and screen processes). I'm using xdm and the non-free nvidia driver. By the way, a correction to my original bug report: the keyboard stops working while xscreensaver is attempting to lock, but not the mouse. -- Jeremy Hankins <[EMAIL PROTECTED]> PGP fingerprint: 748F 4D16 538E 75D6 8333 9E10 D212 B5ED 37D0 0A03 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
