[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#680098: marked as done (x11-xkb-utils: Navigation up-arrow not recognized)

Your message dated Thu, 5 Jul 2012 20:19:41 +0200
with message-id <20120705181941.GU6771@radis.cristau.org>
and subject line Re: Bug#680098: x11-xkb-utils: Navigation up-arrow not recognized
has caused the Debian Bug report #680098,
regarding x11-xkb-utils: Navigation up-arrow not recognized
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
680098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680098
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: x11-xkb-utils
Version: 7.7~1
Severity: normal


This behavior started with the Sun Type 7 USB keyboard I normally use,
but I have reproduced it
with another keyboard (Adesso USB PC104 keyboard). 

xev reports no keypress using the up-arrow, only:

FocusOut event, serial 37, synthetic NO, window 0x2c00001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 37, synthetic NO, window 0x2c00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 37, synthetic NO, window 0x0,
    keys:  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
0   

FocusOut event, serial 37, synthetic NO, window 0x2c00001,
    mode NotifyNormal, detail NotifyNonlinear

However, for the down-arrow, xev reports:

KeyPress event, serial 37, synthetic NO, window 0x2c00001,
    root 0xb8, subw 0x0, time 328954299, (109,-16), root:(1469,784),
    state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x2c00001,
    root 0xb8, subw 0x0, time 328954371, (109,-16), root:(1469,784),
    state 0x0, keycode 116 (keysym 0xff54, Down), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages x11-xkb-utils depends on:
ii  libc6        2.13-33
ii  libx11-6     2:1.5.0-1
ii  libxaw7      2:1.0.10-2
ii  libxkbfile1  1:1.0.8-1
ii  libxt6       1:1.1.3-1

x11-xkb-utils recommends no packages.

x11-xkb-utils suggests no packages.

-- no debconf information



-- 
--

----------------------------------------------------------------------
Andrew J Perrin - andrew_perrin@unc.edu - http://perrin.socsci.unc.edu
Associate Professor of Sociology, University of North Carolina
CB#3210, 155 Hamilton Hall, Chapel Hill, NC 27599-3210 USA

--- End Message ---
--- Begin Message --- 
On Thu, Jul  5, 2012 at 10:54:10 -0400, Andrew J Perrin wrote:

> Thank you - the problem is now solved. There was an old .Xmodmap file
> that was misdirecting the keypress.
> 
Good.  Thanks for the followup.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: