| 1 |
Hi! |
| 2 |
|
| 3 |
On Fri, Jun 01, 2012 at 07:08:27PM -0700, Chris Stankevitz wrote: |
| 4 |
> Can someone recommend an approach to identify the culprit? |
| 5 |
|
| 6 |
Create a script like ~/bin/loghotkey: |
| 7 |
#!/bin/sh |
| 8 |
echo pressed >> /tmp/hotkey.log |
| 9 |
and run this script instead of browser on same hotkey. After each hot key |
| 10 |
press check is new line appended to /tmp/hotkey.log. |
| 11 |
|
| 12 |
If it is added, then your keyboard is ok, and it's probably browser fail |
| 13 |
to start occasionally. In this case you can modify this script like: |
| 14 |
#!/bin/sh |
| 15 |
echo starting browser >> /tmp/hotkey.log |
| 16 |
/path/to/your/browser >> /tmp/hotkey.log 2>&1 |
| 17 |
echo exiting browser >> /tmp/hotkey.log |
| 18 |
and check what's going on. |
| 19 |
|
| 20 |
If it's not added, then problem can be with your keyboard. In this case |
| 21 |
you can try using some other completely different hotkey (like ctrl+a |
| 22 |
instead of win+b) and see is that helps. Also, you can try to use xkbevd, |
| 23 |
xkbwatch, and other similar tools to trace keyboard events. And, finally, |
| 24 |
try another keyboard. |
| 25 |
|
| 26 |
-- |
| 27 |
WBR, Alex. |
Archives