Bug 391 - WorkRave does not detect keystrokes on second X screen
Status:
RESOLVED WORKSFORME
Component:
Core :: UNIX
Version:
1.6.0
Hardware:
PC Linux
Importance:
P4 major
Target Milestone:
---
Assignee:
Rob Caelers
URL:
Depends on:
Blocks:
Reported:
May 6 2004 21:18:13 UTC
by:
Joshua Wise
Modified:
Mar 10 2008 20:26:46 UTC
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Rob Caelers | Aug 27 2007 14:03:43 UTC | priority | P2 | P4 |
| Rob Caelers | Mar 10 2008 20:26:46 UTC | status | NEW | RESOLVED |
| resolution | WORKSFORME |
Description
Joshua Wise May 6 2004 21:18:13 UTC
WorkRave seems not to be detecting keystrokes on my second X display (:0.1) when I run it on :0.0. It does detect mouse movement properly. WorkRave does also seem to not detect button pushing on :0.0 (mouse), however it does on :0.1 if I run it on :0.1. Error on startup: X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 28 (X_GrabButton) Serial number of failed request: 1833 Current serial number in output stream: 1834 I tried running WR on both :0.0 and :0.1 simultaneously and enabling the networking support, however WR seems to be against using the ports that I specify, and in any event, it would get wiped out when WR writes its config out. Am I doing something wrong, or have I hit on a bug?
Comment 1
Rob Caelers May 13 2004 10:16:23 UTC
Please check if the record extension is enabled in /etc/X11/XF86Config-4:
Section "Module"
Load "record"
EndSection
Without record, workrave uses a dirty hack to monitor you keyboard.
Both workraves use the same configuration and the same port. You can also use
the environment variable WORKRAVE_PORT to define the port workrave must use.Comment 2
Rob Caelers Mar 10 2008 20:26:46 UTC
I just tested Workrave with multiple screens (instead of Nvidia's twinview) The hack only detects mouse movement, keyboard is not monitored; as you said. The xrecord monitoring detects both. I said this before: the hack will be disabled by default in the near future. closing bug.