Summary: | syndaemon doesn't work | ||
---|---|---|---|
Product: | xorg | Reporter: | Ondrej Holy <oholy> |
Component: | Input/synaptics | Assignee: | Peter Hutterer <peter.hutterer> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | bugzilla, peter.hutterer |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Ondrej Holy
2014-10-08 09:29:39 UTC
checked this again and it works as expected here on 1.7.6, the same version the reporter in the GNOME bug has. Unfortunately, reporter has moved to a different desktop environment and cannot seem to reproduce the issue there. I'm having this issue with Lenovo Thinkpad T440s, latest Fedora 21 with all updates applied. What info can I share with you in order to figure out what is causing this bug? $ sudo ps aux|grep synd valent 13564 0.0 0.0 23368 2568 ? S 19:09 0:00 syndaemon -i 1.0 -t -K -R valent 13593 0.0 0.0 112996 2484 pts/0 S+ 19:10 0:00 grep --color=auto synd valent@frajer src$ And tapping isn't workign, but moving the cursor and clicking (pressing the touchpad on new Lonovo 2013 models is equal to button press because there are no more dedicated buttons) if I kill that process and run "syndaemon -i 1.0 -K -R" then curson is not being moved while typing. right, the difference here is the -t flag though. so afaict syndaemon behaves correctly, don't you agree? I agree, synaptic daemon works correctly but who ever thought these are sane defaults is very, very wrong. re-closing. fwiw, things change over time and defaults that make sense at some point may not in the future. No need to assume malice here. specifically: you have a T440 where it's very likely to accidentally touch the touchpad and move the pointer. That's different to previous smaller touchpads so the default now just doesn't work as originally intended. |
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.