From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <gentoo-dev-return-14386-arch-gentoo-dev=gentoo.org@lists.gentoo.org> Received: (qmail 9725 invoked from network); 23 Jul 2004 07:47:58 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 23 Jul 2004 07:47:58 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1Bnumb-0004ly-6y for arch-gentoo-dev@lists.gentoo.org; Fri, 23 Jul 2004 07:47:57 +0000 Received: (qmail 26286 invoked by uid 89); 23 Jul 2004 07:47:56 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: <mailto:gentoo-dev@gentoo.org> List-Help: <mailto:gentoo-dev-help@gentoo.org> List-Unsubscribe: <mailto:gentoo-dev-unsubscribe@gentoo.org> List-Subscribe: <mailto:gentoo-dev-subscribe@gentoo.org> List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org> X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 998 invoked from network); 23 Jul 2004 07:47:56 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Date: Fri, 23 Jul 2004 00:47:52 -0700 Organization: Sometimes Message-ID: <pan.2004.07.23.07.47.51.730874@cox.net> References: <200407221939.28868.norberto+gentoo-dev@bensa.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1250 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-230-66-58.ph.ph.cox.net User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table) Sender: news <news@sea.gmane.org> Subject: [gentoo-dev] Re: xorg-x11-6.7.0-r2, XF86Standby: keysym 0x0, NoSymbol X-Archives-Salt: b3d05bce-06c3-404e-9afe-13f7a3074e0b X-Archives-Hash: 8969002a976af0c889e0981e8d8c99cd Norberto Bensa posted <200407221939.28868.norberto+gentoo-dev@bensa.ath.cx>, excerpted below, on Thu, 22 Jul 2004 19:39:28 -0300: > Hello, > > did anything related to keyboards changed in xorg-x11-6.7.0-r2 since -r1? > > I can't seem to make my "Suspend" key work (it was in -r1) Keyboard is a > Microsoft Natural Keyboard Pro. > > xev says: > > KeyPress event, serial 26, synthetic NO, window 0x3000001, > root 0x8d, subw 0x0, time 4882596, (763,521), root:(838,567), state > 0x10, keycode 225 (keysym 0x0, NoSymbol), same_screen YES, > XLookupString gives 0 bytes: > XmbLookupString gives 0 bytes: > XFilterEvent returns: False > > KeyRelease event, serial 29, synthetic NO, window 0x3000001, > root 0x8d, subw 0x0, time 4882687, (763,521), root:(838,567), state > 0x10, keycode 225 (keysym 0x0, NoSymbol), same_screen YES, > XLookupString gives 0 bytes: > > > Yes, I've updated every file in /usr/X11R6/lib/X11/xkb... I thought it was just me! Logitech Cordless Desktop Pro, here. It's supposed to use the same keysym, XF86Standby, assigned to <I5F>, in /etc/X11/xkb/symbols/inet, which is assigned to kernel keycode 223 in /etc/X11/xkb/keycodes/xfree86, as the MS keyboards. That standby key seems to be the ONE key that has been standardized out of the lot of extra keycodes/keysyms on the "internet" keyboards. Now, as with you, xev is telling me the key is emitting keycode 225, assigned <I61> in inet, but not assigned a non-generic keysym for ANY of the internet keyboards, thus the NoSymbol error. There's a catch, however. It's possible its the kernel, because as I said the XFree/Xorg documentation says the keycodes come from the kernel. I'll boot back to Mandrake and XFree (I use the same kernel on both, and just switched from Mandrake, which I still have on dual-boot), and run xev there to double-check, but last I knew, it was working, there. I had assumed my keyboard was going bad and was now reading the code for that key differently. I was just going to change my configuration manually and obviously have already done some research in that direction. However, if it's happening to you to, also on Xorg, it's gotta either be xorg or as I said, possibly the kernel. Which kernel are you running? I'm running 2.6.7 straight off of kernel.org (thus, no gentoo or other patches), here. When we get this figured out, it should be filed as a bug, tho it's probably upstream, and since xorg is supposed to be coming out with another release in August, it's likely they've fixed it by now (assuming it's xorg and not the kernel). I'll followup with some more info l8r. -- Duncan - List replies preferred. No HTML msgs. "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -- Benjamin Franklin -- gentoo-dev@gentoo.org mailing list