I couldn't find any time to dig deeper into the problem, and since I'm not an expert in the X I'm afraid it would take me lot of time and efforts.
The strace output was not very informative and setting up X for debugging was really troublesome since I'm using a debian based system and apt forced to upgrade quite a lot of packages that I can't afford at this moment. All I found is that the random error is associated with a particular hardware in my system. When the key pressed is associated with an script that directly or indirectly triggers an "write output" to the usb2serial device (based on a pl2303 chipset) the problem randomly arise. It doesn't repeat in any other circumstance, just when sending data out to the /dev/ttyUSB0 (pl2303 usb2serial) device. For now, I solved the issue ussing a custom C program that directly reads to /dev/input/event"N" completly bypassing the X system. (For anyone interested I used a custom modifyied version of logkeys -http://code.google.com/p/logkeys/-. It also has the advantage of beeing able to differentiate between different input devices, while the disadvantage of beeing more "linux-centric") Regards, Enrique On Fri, Dec 3, 2010 at 2:07 AM, Pat Kane <[email protected]> wrote: > On Thu, Dec 2, 2010 at 3:23 AM, ENRIQUE ARIZON BENITO wrote: > > Still I don't known if that really has anything to do with the infinte > > random loop I observe. > > When your X server gets stuck connect to the X process with gdb > step through procedure calls. I'd also run "strace" on the X process. > > Adam Jackson (ajax) submitted a bug fix a while back that might interesting: > > http://patchwork.freedesktop.org/patch/1703/ > > Pat > ---- > _______________________________________________ [email protected]: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: [email protected]
