Hi, You may or may not consider this a bug, but I've figured out that calling xmodmap while xnee is recording will cause xnee to stop outputing new events.
How to reproduce: $ xnee --k-log --record --all-events > foo.log & $ wc -l foo.log 82 foo.log $ wc -l foo.log 85 foo.log $ xmodmap -e 'clear Lock' $ wc -l foo.log 136 foo.log $ wc -l foo.log 136 foo.log $ killall xnee $ rm foo.log I personally don't see this as being very problematic, but I would have preferred xnee to halt or output a message instead of stalling. I also wanted to point out this behaviour in case other people saw their long-running xnee sessions hang mysteriously and wondered what could cause it. - Samuel Gélineau
_______________________________________________ Bug-xnee mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-xnee
