Re: [Bug-xnee] xmodmap stalls xnee --record

[Henrik Sandklef]

hi
 and thanks for your report.

You're using an old version of Xnee. The name xnee for the program 
hasn't been there for a while.  Can you update to 3.02?

... and then do:

 cnee --data-to-record 100 --record --device-event-range 2-6 
--delivered-event-range 7-31 --request-range 1-120 --error-range 1-17


We can now reproduce your reported error.... and to be honest I have no 
idea why this happens.

There's an old synch bug which really has to be solved before this 
one.... hopefully soon.


/hesa



Gelineau,Samuel [Montreal] wrote:
> 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
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-xnee