Bug 58525 - Syndaemon behavior when no synaptics device is found
Summary: Syndaemon behavior when no synaptics device is found
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/synaptics (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: Peter Hutterer
QA Contact:
URL: https://bugs.launchpad.net/ubuntu/+so...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-19 16:53 UTC by Ahmed Shams
Modified: 2013-11-03 22:57 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Ahmed Shams 2012-12-19 16:53:47 UTC
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
Comment 1 Peter Hutterer 2012-12-20 00:39:55 UTC
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.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.