the mouse loses the ability to choose the window and input focus to controls (fglrx)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-input-evdev (Ubuntu) |
Expired
|
Medium
|
Unassigned | ||
Bug Description
installed version: ubuntu-
installed russian and english languages
default language is english, for interface
steps to find bug: type russian text in gedit (and in all input boxes in operating system), after it mouse focus captured and not released to other applications, no ability to shoose the other controls and windows
behavior expected: type normally russian text and after select with mouse controls and windows
---
Architecture: amd64
DistroRelease: Ubuntu 10.10
DkmsStatus:
virtualbox-ose, 3.2.8, 2.6.35-22-generic, x86_64: installed
fglrx, 8.780, 2.6.35-22-generic, x86_64: installed
GdmLog2: X: /tmp/.X11-unix has suspicious mode (not 1777) or is not a directory, aborting.
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: ASUSTeK Computer INC. K40AB
NonfreeKernelMo
Package: xserver-
PackageArchitec
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSign
Tags: maverick maverick
Uname: Linux 2.6.35-22-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/20/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 218
dmi.board.
dmi.board.name: K40AB
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.00
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K40AB
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: maverick
architecture: x86_64
kernel: 2.6.35-22-generic
---
Architecture: amd64
DistroRelease: Ubuntu 10.10
DkmsStatus:
virtualbox-ose, 3.2.8, 2.6.35-22-generic, x86_64: installed
fglrx, 8.780, 2.6.35-22-generic, x86_64: installed
GdmLog2: X: /tmp/.X11-unix has suspicious mode (not 1777) or is not a directory, aborting.
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: ASUSTeK Computer INC. K40AB
NonfreeKernelMo
Package: xserver-
PackageArchitec
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSign
Tags: maverick maverick
Uname: Linux 2.6.35-22-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/20/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 218
dmi.board.
dmi.board.name: K40AB
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.00
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K40AB
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: maverick
architecture: x86_64
kernel: 2.6.35-22-generic
description: | updated |
description: | updated |
description: | updated |
Changed in ubuntu: | |
status: | Incomplete → New |
description: | updated |
Changed in xserver-xorg-input-mouse (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in xserver-xorg-input-mouse (Ubuntu): | |
status: | Triaged → Fix Released |
Changed in xserver-xorg-input-mouse (Ubuntu): | |
status: | Fix Released → Incomplete |
Changed in xserver-xorg-input-mouse (Ubuntu): | |
status: | Incomplete → Triaged |
tags: | added: maverick |
affects: | xserver-xorg-input-mouse (Ubuntu) → xorg (Ubuntu) |
summary: |
- the mouse loose the ability to shoose the window and input focus to + the mouse loses the ability to choose the window and input focus to controls |
summary: |
the mouse loses the ability to choose the window and input focus to - controls + controls (fglrx) |
affects: | xorg (Ubuntu) → xserver-xorg-input-evdev (Ubuntu) |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at http:// wiki.ubuntu. com/DebuggingPr ocedures
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!