Your message dated Thu, 15 May 2008 12:17:52 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#481262: Info received (Bug#481262: Info received 
(xorg: does  not read control  keys or  numlock or capslock  keys with nvidia 
driver))
has caused the Debian Bug report #481262,
regarding xorg: does not read control keys or numlock or capslock keys with 
nvidia driver
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 [EMAIL PROTECTED]
immediately.)


-- 
481262: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481262
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: xorg
Version: 1:7.3+10
Severity: grave
Justification: renders package unusable


This happened right after I upgraded to the xorg version in the latest system 
update.

unsatisfactory workaround - switching to the vesa driver.

the subject is adequately descriptive - except that the SHIFT KEY also fails.. 
If I didn't 
have VMware Server running with a Windows VM so I could enter my root password 
with an upper 
case letter in it and hadn't had a copy of Kwrite with desktop icon set to open 
as root,  I 
wouldn't have been able to get into xorg.conf in order to change the driver 
setting to vesa.

In my opinion, an inexperienced user would not only be unable to get into root, 
but very 
possibly wouldn't even be able to file a bug report. 

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'unstable'), (150, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (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 xorg depends on:
ii  gnome-terminal [x-t 2.22.1-1             The GNOME 2 terminal emulator appl
ii  konsole [x-terminal 4:3.5.9.dfsg.1-2+b1  X terminal emulator for KDE
ii  libgl1-mesa-glx [li 7.0.3-1              A free implementation of the OpenG
ii  libglu1-mesa        7.0.3-1              The OpenGL utility library (GLU)
ii  x11-apps            7.3+1                X applications
ii  x11-session-utils   7.3+1                X session utilities
ii  x11-utils           7.3+1                X11 utilities
ii  x11-xfs-utils       7.3+1                X font server utilities
ii  x11-xkb-utils       7.3+1                X11 XKB utilities
ii  x11-xserver-utils   7.3+2                X server utilities
ii  xauth               1:1.0.3-1            X authentication utility
ii  xfonts-100dpi       1:1.0.0-4            100 dpi fonts for X
ii  xfonts-75dpi        1:1.0.0-4            75 dpi fonts for X
ii  xfonts-base         1:1.0.0-5            standard fonts for X
ii  xfonts-scalable     1:1.0.0-6            scalable fonts for X
ii  xfonts-utils        1:1.0.1-2            X Window System font utility progr
ii  xinit               1.0.8-1              X server initialisation tool
ii  xkb-data            1.2~cvs.20080501.1-1 X Keyboard Extension (XKB) configu
ii  xserver-xorg        1:7.3+10             the X.Org X server
ii  xterm [x-terminal-e 235-1                X terminal emulator

Versions of packages xorg recommends:
ii  xorg-docs                     1:1.4-2    Miscellaneous documentation for th

-- no debconf information



--- End Message ---
--- Begin Message ---
On Thu, May 15, 2008 at 02:42:42 -0700, A.Lizard wrote:

> At 01:24 AM 5/15/08, you wrote:
>> On Wed, May 14, 2008 at 20:49:58 -0700, A.Lizard wrote:
>>
>> > The keys have reappeared except for scroll-lock, and they work on both
>> > vesa and nvidia drivers. Numlock still does not work on a VMware Server
>> > Windows VM. However, I use scroll-lock so infrequently that I don't know
>> > whether or not it this is normal. I'm totally confused about this.
>> >
>> Does this mean we can close this bug?
>
> I think so. I'll reopen it if I think it's indicated.
>
Thanks, doing that with this message.

Cheers,
Julien


--- End Message ---

Reply via email to