From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SakEw-0007Gb-V9 for garchives@archives.gentoo.org; Sat, 02 Jun 2012 09:03:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5BC4EE08C6 for ; Sat, 2 Jun 2012 09:03:18 +0000 (UTC) Received: from powerman.name (powerman.name [85.90.198.1]) by pigeon.gentoo.org (Postfix) with ESMTP id 9E685E0763 for ; Sat, 2 Jun 2012 06:05:10 +0000 (UTC) Received: (qmail 11569 invoked by uid 1000); 2 Jun 2012 06:05:09 -0000 Date: Sat, 2 Jun 2012 09:05:09 +0300 From: Alex Efros To: gentoo-desktop@lists.gentoo.org Subject: Re: [gentoo-desktop] Help troubleshooting keyboard shortcut Message-ID: <20120602060509.GD25247@home.power> Mail-Followup-To: gentoo-desktop@lists.gentoo.org References: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-desktop@lists.gentoo.org Reply-to: gentoo-desktop@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: http://powerman.name/ User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 824243b1-daf6-460d-b856-ec780e4d1236 X-Archives-Hash: 70fbca947d7e49096e48625a9ae31815 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.