Bryce suggested running xtrace, and a trace is attached. My interpretation of it is this: xtrace can't totally decode the RECORD extension messages but it can see them happening. Workrave opens a separate server connection for the callbacks, which seems to be how XRecord is documented to work, and in this trace that's (I think) the lines starting with 003:
Around line 998 after initializing connection 003, it sends a RECORD- Request(137, 5) gets a reply, and nothing more on that channel. So that would be consistent with what I saw in gdb in comment 5 above, and seems to show it's not just something in the client or libraries causing the events to be ignored. recordstr.h has 52 #define X_RecordEnableContext 5 /* Enable interception and reporting */ ** Description changed: Binary package hint: workrave + + Workrave is a program to encourage you to take typing breaks. It's + meant to monitor when you're typing or idle, a bit like xscreensaver + might do. This seems to be a new regression in Jaunty: workrave simply doesn't notice any keyboard or mouse input. The countdown stays at 5:00 even as I'm typing, and it doesn't show any mouse usage or keystrokes in the Statistics dialog. So for me, workrave is completely broken. I've checked that it is in Normal mode, and tried changing it in and out of that mode. My settings are attached. + + Regular interaction with it's gtk dialogs works ok. It's just that it's + not getting any RECORD events from the server. ** Attachment added: "workrave.trace" http://launchpadlibrarian.net/23525937/workrave.trace -- workrave doesn't notice input https://bugs.launchpad.net/bugs/332716 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
