key-release events frequently missed

Bug #607350 reported by Kamal Mostafa
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: xorg

Gigabyte "Spring Peak" laptop

[originally reported by Earl Malmrose (earl)]:

Sometimes key-release events are lost. I notice that sometimes when pressing down-arrow to scroll down a heavy webpage, sometimes when I release the down-arrow it keeps scrolling down until I press down-arrow again.

[confirmed by Kamal Mostafa (kamalmostafa) on an identical machine]:

The problem can be also be reproduced in gnome-terminal. Hold down any regular key (e.g. the 'a' key) for a few seconds then release it. Usually the auto-repeat stops as expected but sometimes (about one in twenty times) it does not stop. Tapping any key then stops it.

The problem does NOT seems to occur in a regular text-mode console screen -- only happens in X.

The problem occurs in Ubuntu Lucid and Ubuntu Maverick.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5
Uname: Linux 2.6.35-8-generic x86_64
Architecture: amd64
DRM.card0.DisplayPort.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.DisplayPort.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.DisplayPort.3:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1366x768
 edid-base64: AP///////wAGrywSAAAAAAESAQOAHRB4CvnVlVVUkychUFQAAAABAQEBAQEBAQEBAQEBAQEBJhtWZFAAFjAwIDYAJaQQAAAYAAAADwAAAAAAAAAAAAAAAAAgAAAA/gBBVU8KICAgICAgICAgAAAA/gBCMTMzWFcwMSBWMiAKADU=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Mon Jul 19 10:21:04 2010
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100602.2)
MachineType: GIGABYTE Spring Peak
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-8-generic root=UUID=8d8e9687-b11d-4696-93a8-916476dcf963 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xorg
dmi.bios.date: 03/24/2010
dmi.bios.vendor: GIGABYTE
dmi.bios.version: ASBF0C
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: GA-XXXXXXX
dmi.board.vendor: GIGABYTE
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnGIGABYTE:bvrASBF0C:bd03/24/2010:svnGIGABYTE:pnSpringPeak:pvrASBF0C:rvnGIGABYTE:rnGA-XXXXXXX:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: Spring Peak
dmi.product.version: ASBF0C
dmi.sys.vendor: GIGABYTE
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-8-generic

Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :
description: updated
Revision history for this message
Kamal Mostafa (kamalmostafa) wrote :

Note: the problem occurs with all of these Gigabyte BIOS versions: F06, ASBF07, ASBF0C

Changed in xorg (Ubuntu):
status: New → Confirmed
Bryce Harrington (bryce)
affects: xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Revision history for this message
bugbot (bugbot) wrote :

Hey Kamal,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → Expired
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.