Syndaemon behavior when no synaptics device is found

Bug #723786 reported by Rainfly_X
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Xserver Xorg Input Synaptics
Won't Fix
Medium
xserver-xorg-input-synaptics (Ubuntu)
New
Wishlist
Unassigned

Bug Description

Binary package hint: xserver-xorg-input-synaptics

Syndaemon is a powerful and wonderful tool that allows you to, among many other things, prevent accidental clicking when you're trying to type.

But no matter how many times we solve the "synaptics device not found" bug for synaptics devices, new, old, or just plain odd devices are gonna get left out in the cold. So I recommend that syndaemon be made capable of working with unclassified "mice" that show up as "ImPS/2 Generic Wheel Mouse," by spitting out a warning that it's going to use a device that doesn't look like a synaptics device, give the name, and then give the user a Y/N option whether to continue.

This would make syndaemon a lot more useful to people who are still waiting for bugfixes on their touchpads, or even people with regular mice in some scenarios (I'm thinking, really persistantly bothersome cats). It would certainly make my life a lot more livable, since I have a very sensitive and obnoxiously placed touchpad that ends up registering clicks all the time when I'm trying to type.

Revision history for this message
In , Ahmed Shams (ashams) wrote :

This suggestion was reported to launchpad bug tracker for synaptics touchpad by Rainfly_X:
Syndaemon is a powerful and wonderful tool that allows you to, among many other things, prevent accidental clicking when you're trying to type.

But no matter how many times we solve the "synaptics device not found" bug for synaptics devices, new, old, or just plain odd devices are gonna get left out in the cold. So I recommend that syndaemon be made capable of working with unclassified "mice" that show up as "ImPS/2 Generic Wheel Mouse," by spitting out a warning that it's going to use a device that doesn't look like a synaptics device, give the name, and then give the user a Y/N option whether to continue.

This would make syndaemon a lot more useful to people who are still waiting for bugfixes on their touchpads, or even people with regular mice in some scenarios (I'm thinking, really persistantly bothersome cats). It would certainly make my life a lot more livable, since I have a very sensitive and obnoxiously placed touchpad that ends up registering clicks all the time when I'm trying to type.

lp bug #723786
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/723786

Revision history for this message
Ahmed Shams (ashams) wrote :
Changed in xserver-xorg-input-synaptics (Ubuntu):
importance: Undecided → Wishlist
Changed in xserver-xorg-input-synaptics:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
In , Peter Hutterer (peter-hutterer) wrote :

syndaemon currently uses a synaptics-only property to disable the touchpad. this property disables the touchpad in-driver. a similar property exists on all devices but that would disable the device completely, potentially interfering with the desktop environment. this would require testing to ensure it doesn't break anything.

other than that, syndaemon would need a commandline switch to let the user specify the device. right now it looks for the synaptics pad, which in your case would not work.

if you have patches, I'd likely merge them if there not too invasive.

Changed in xserver-xorg-input-synaptics:
status: Confirmed → Won't Fix
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.