Mouse and Keyboard keep focus in one window

Bug #747585 reported by Jo Vik
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

This bug occurs sporadically. It has never appeared in the recovery mode with simple graphics. From what I have found on the web it's connected to event issues (button remains as pressed in the system; release event seems to be missed by Ubuntu)

Let's say I try to view a video clip on YouTube. Afterwards I can use my cursor in Opera and click it's buttons and etc. But if I move cursor to Ubuntu menu and click - nothing happens. Alt+tab also seems not to work. I have to unplug and plug mouse cable to be able to use it once again.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-28-generic 2.6.35-28.49
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jv 1749 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xe9300000 irq 47'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,1458a102,00100101'
   Controls : 38
   Simple ctrls : 21
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xe5010000 irq 48'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100100'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Fri Apr 1 19:50:14 2011
Frequency: Once a day.
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007.1)
MachineType: Gigabyte Technology Co., Ltd. EP45-DS3R
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic root=UUID=2653c680-6655-4eef-be64-247065dcc99d ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.38.5
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 08/18/2008
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: EP45-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd08/18/2008:svnGigabyteTechnologyCo.,Ltd.:pnEP45-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-DS3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EP45-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Jo Vik (jovik-pl+launchpad) wrote :
description: updated
Revision history for this message
TJ (tj) wrote :

On a Mythbuntu (Xubuntu 10.04 Lucid) system I noticed this begin with 2.6.32-29.

Booting to 2.6.32-28 resolves the issue.

I cannot see anything in the Changelog that indicates a change that would affect the input events.

The effect is as described by the original reporter - focus is captured by one window or application, and despite being able to click on other windows or the system menus, there is no response. I found that by clicking the middle and/or right buttons in the window that has captured focus, and without dismissing the resulting context menu pop-up, moving to another window or the system menu, I am able to then left-click to select. That gets dicey when the system menu captures focus though, getting out seems more difficult.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Jo Vik (jovik-pl+launchpad) wrote :

I've located the problem in my case. Apparently my mouse buttons wared-off (8 years old Logitech), which leaded to sporadic short circuits. However, Mac OS X and Vista seem to handle issue much better. Now I'm using a new mouse and so far - no problems.

I found a thread with similar issue on one of the forums. It turns out this problem is above Linux distributions because it's related to X.org. Here is Google Translate of the thread:
http://translate.google.com/translate?js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&sl=pl&tl=en&u=http%3A%2F%2Fforum.linux.pl%2Fviewtopic.php%3Fid%3D17388%26action%3Dnew&act=url

You can try to edit your xorg.conf file.

Revision history for this message
penalvch (penalvch) wrote :

Jo Vik, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (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.