Ubuntu
gnome-control-center package

Mouse preferences: cannot set threshold = 0

Bug #366800 reported by ThomasN
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Wishlist
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-control-center

Description: Ubuntu 9.04
Release: 9.04
Architecture: i386
Version: 1:2.26.0-0ubuntu3

Many laptop users with a Synaptics trackpoint / touchstyk have reported very slow pointer motion when using the trackpoint (also called touchstyk).
One way to work around the problem is to:
xset m 4 0
in a terminal or .xsession
However, this setting gets cancelled by gnome as soon as one leaves X or suspend/resumes.
A better work around is to start gconf-editor and navigate to:
desktop/gnome/peripherals/mouse
and set:
motion_acceleration 4
motion_threshold 0

BUG TO FIX: Mouse preferences should enable lowest Sensitivity to go to 0 instead of 1.
Even better would be to associate a numerical value to the slider position so we know what xset we are at.

Thank you.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

Changed in gnome-control-center (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
ThomasN (tnetter) wrote : Re: [Bug 366800] Re: Mouse preferences: cannot set threshold = 0

Hello Sebastien,

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please answer these questions:
>
> * Is this reproducible?

Every time on my HP 2510p. Probably reproducible on all laptops that have
a Synaptics TouchStyk (several HP laptop models). Thinkpad owners don't
have this problem because they have a specific driver for their
TrackPoint.

> * If so, what specific steps should we take to recreate this bug?

It's more of a feature request. Please enable Mouse Preferences to use the
whole range of values provided by xset, i.e. Sensitivity should go all the
way down to zero instead of 1.

Thank you.

>
> This will help us to find and resolve the problem.
>
> ** Changed in: gnome-control-center (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: gnome-control-center (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: gnome-control-center (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
>
> --
> Mouse preferences: cannot set threshold = 0
> https://bugs.launchpad.net/bugs/366800
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

is the issue specific to touchpads?

Changed in gnome-control-center (Ubuntu):
importance: Low → Wishlist
status: Incomplete → New
Revision history for this message
ThomasN (tnetter) wrote :

> is the issue specific to touchpads?

No. I experience the bug with a Synaptics TouchStyk. Any user who needs a
threshold/Sensitivity of 0 cannot set it using Gnome Mouse Preferences.
The people who programmed the Mouse Preferences thought that
threshold/Sensitivity starts at 1. But in fact it starts at 0 (see man
xset). It is a programming error in that the programmers did not use the
full set of specifications.

>
> ** Changed in: gnome-control-center (Ubuntu)
> Importance: Low => Wishlist
>
> ** Changed in: gnome-control-center (Ubuntu)
> Status: Incomplete => New
>
> --
> Mouse preferences: cannot set threshold = 0
> https://bugs.launchpad.net/bugs/366800
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>

Revision history for this message
Traz (traz) wrote :

Since Ubuntu Jaunty, mouse threshold has a different behaviour. I'm sure you didn't have this problem in previous versions with threshold=1.

This problem is also in Karmic.

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

Other bug subscribers

Remote bug watches

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