numpad 0 (zero) does not work

Bug #743337 reported by Šarūnas Valaškevičius
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xkeyboard-config (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: xorg

while numlock is on, all numbers work ok, except 0. this happens only in X windows - console (tty[1-6]) works ok.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xorg 1:7.6~3ubuntu11
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: kwin
DRM.card0.HDMI.A.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Sat Mar 26 23:51:31 2011
DistUpgraded: Log time: 2011-03-24 20:48:46.595648
DistroCodename: natty
DistroVariant: kubuntu
DkmsStatus:
 virtualbox-ose, 4.0.4, 2.6.38-7-generic, x86_64: installed
 virtualbox-ose, 4.0.4, 2.6.35-28-generic, x86_64: installed
GraphicsCard:
 ATI Technologies Inc RV730XT [Radeon HD 4670] [1002:9490] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:0294]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: System manufacturer P5Q-PRO
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LANGUAGE=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=1df426be-8b6b-45af-b780-df5ca5084f85 ro quiet splash vt.handoff=7
Renderer: Unknown
SourcePackage: xorg
UpgradeStatus: Upgraded to natty on 2011-03-24 (2 days ago)
dmi.bios.date: 07/10/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1004
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1004:bd07/10/2008:svnSystemmanufacturer:pnP5Q-PRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q-PRO
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.4git20110322-0ubuntu5
version.libdrm2: libdrm2 2.4.23-1ubuntu5
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6

Revision history for this message
Šarūnas Valaškevičius (rakatan) wrote :
Revision history for this message
Šarūnas Valaškevičius (rakatan) wrote :

somehow it started to work again. will notify again if it stops (possibly with more info).

Changed in xorg (Ubuntu):
status: New → Incomplete
bugbot (bugbot)
affects: xorg (Ubuntu) → xserver-xorg-video-ati (Ubuntu)
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

reopen the bug if it happens again

affects: xserver-xorg-video-ati (Ubuntu) → xkeyboard-config (Ubuntu)
Changed in xkeyboard-config (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Šarūnas Valaškevičius (rakatan) wrote :

it seems it fails just sometimes - I noticed it not working again in chrome, opened kmail to find this bug nr, and it started to work. even in the same instance of chrome.

I would appreciate any thoughts of what should I use to get more info or how should I debug it?..
why is it 0 only, that ignores the numlock? and why just sometimes? (and also I dont know how to force it to stop working for debugging :) )

I could leave some logging script running, but what should it check?

Revision history for this message
Šarūnas Valaškevičius (rakatan) wrote :

(pls see my last comment)

Changed in xkeyboard-config (Ubuntu):
status: Invalid → New
Revision history for this message
tulskiy (tulskiy) wrote :

I had this problem, I changed keyboard model from generic to my keyboard, it started to work. Today it failed again, I changed keyboard model back. Works so far.

Revision history for this message
Šarūnas Valaškevičius (rakatan) wrote :

hi, works ok long time already.. probably some update fixed it :) (I already forgot about this issue :) )

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.