The latest xscreensaver has been activating on me in the middle of various 
full-screen SDL games, when I use keyboard-only controls. The exact 
behavior varies:

  armagetron: Full-screen window minimizes (showing the desktop), screen 
  immediately fades to black, hack starts running

  neverball: Game repeatedly pauses of its own volition, but stays up (I 
  can unpause it each time and continue, but it's bloody annoying); output 
  from "-verbose -no-capture" indicates unsuccessful attempts to grab the 
  keyboard and pointer

  trackballs: No visible effect on game; same log output as w/neverball

  gltron: same as trackballs

Also, on more than one occasion, my mouse cursor disappeared after I quit 
the game. Keyboard input worked fine, but there was no pointer, and all 
mouse clicks/movement were ignored. I was able to regain the pointer after 
xscreensaver kicked on again (much to my relief). I have not been able to 
reproduce this behavior reliably; some sort of input grab race condition, 
perhaps?

Xscreensaver built from source does not display any of this behavior, and 
the program log output indicates /proc/interrupts support---missing from 
the Debian-built package. (This is confirmed by the buildd log.)

The configure script checks for /proc/interrupts support with the following 
snippet:

  AC_CACHE_CHECK([whether /proc/interrupts contains keyboard data],
    ac_cv_have_proc_interrupts,
    [ac_cv_have_proc_interrupts=no
     if grep 'keyboard\|i8042' /proc/interrupts >/dev/null 2>&1 ; then
       ac_cv_have_proc_interrupts=yes
     fi
    ])

The buildd, it appears, is working in an environment where the above 
condition is false. Passing --with-proc-interrupts to the configure script 
doesn't look like it'll do the trick; I believe you'll have to set the 
cachevar to bypass the /proc check.

(That, in itself, might be considered a bug---that it is not possible to 
build /proc/interrupts support without the actual file unless one resorts 
to such subterfuge...)


--Daniel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to