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