Bluetooth mouse is extremely sensitive despite sensitivity and acceleration set to minimum
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
I am using an Apple Magic Mouse (bluetooth) with a MacBook Air (late 2010) running an up-to-date installation of Ubuntu 12.04. Despite setting both acceleration and sensitivity to the minimum settings in the Control Centre, the mouse is extremely sensitive when used on the built-in (11") display. Please note the following:
1) The trackpad sensitivity is fine
2) The mouse sensitivity is decent when used on a large external display (22")
I would be happy to provide further details, but I was unsure against which package to report the issue or how to collect relevant debugging information.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-
ProcVersionSign
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Tue Jun 12 12:38:02 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64+mac (20120425.1)
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANGUAGE=en_ZA:en
LANG=en_ZA.UTF-8
SourcePackage: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
XsessionErrors:
(nm-applet:1842): GdkPixbuf-CRITICAL **: gdk_pixbuf_
(compiz:1823): GConf-CRITICAL **: gconf_client_
(gnome-
(gnome-
usr_lib_
activity-
deja-dup 22.0-0ubuntu2
gnome-bluetooth 3.2.2-0ubuntu5
indicator-datetime 0.3.94-0ubuntu2
affects: | gnome-control-center (Ubuntu) → xorg-server (Ubuntu) |
Eduard Grebe, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http:// cdimage. ubuntu. com/daily- live/current/ .
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 (not the daily folder) following https:/ /wiki.ubuntu. com/KernelMainl ineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: fixed-upstream fixed-upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested. For example: fixed-upstream- v3.13-rc4
kernel-
This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag: testing
needs-upstream-
If the mainline kernel does not fix this bug, please add the following tags: bug-exists- upstream bug-exists- upstream- VERSION- NUMBER
kernel-
kernel-
As well, please remove the tag: testing
needs-upstream-
Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.