I said:
The problem seems to have been solved by moving my wireless router
closer. That took care of my network flakiness, and as an added bonus
my xscreensaver problems have gone away as well. I couldn't say why
network problems would cause xscreensaver issues... Something about how
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.
The problem seems to have been solved by moving my wireless router
closer. That took care of my network flakiness, and as an added
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
Package: xscreensaver
Version: 5.05-3
Severity: important
When I use xscreensaver-command -lock to lock the screen xscreensaver
(run with -verbose) gives this message:
xscreensaver: 15:20:19: LOCK ClientMessage received; activating and locking.
xscreensaver: 15:20:19: 0: locked mode switching.
You've got some other program running that is grabbing the kbd and
preventing xscreensaver from being able to activate.
--
Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/
[EMAIL PROTECTED] http://www.dnalounge.com/
5 matches
Mail list logo
