Bug 1121143
| Summary: | change in behaviour of touchpad (phantom) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Peter F. Patel-Schneider <pfpschneider> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 20 | CC: | gansalmon, hdegoede, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2014-07-19 13:54:48 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Peter F. Patel-Schneider
2014-07-18 13:23:07 UTC
Created attachment 919091 [details]
evemu-record /dev/input/event4 under current Fedora 20 (3.15)
I clicked on the touchpad.
While maintaining the click I swiped (touch-drag-release) with a second finger four or so times.
Created attachment 919092 [details]
evemu-record /dev/input/event4 under older Fedora 20 (3.14.7)
Same finger actions as the other attachment. (Click-hold and four swipes)
Created attachment 919102 [details]
synclient output
I guess that the kernel messages about the mouse had scrolled out of dmesg's range. Here is better information: idefix ~> dmesg | grep mouse [ 1.238433] mousedev: PS/2 mouse device common for all mice [ 1.892926] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xd00123/0x840300/0x126c00, board id: 2132, fw id: 1180104 Going back to 3.14.7 changes the behaviour back to the expected one. Hi, (In reply to Peter F. Patel-Schneider from comment #4) > I guess that the kernel messages about the mouse had scrolled out of dmesg's > range. Here is better information: > > idefix ~> dmesg | grep mouse > [ 1.238433] mousedev: PS/2 mouse device common for all mice > [ 1.892926] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: > 0x1e2b1, caps: 0xd00123/0x840300/0x126c00, board id: 2132, fw id: 1180104 > > Going back to 3.14.7 changes the behaviour back to the expected one. So your only booting the old resp. the new kernel to make the problem come and go, no other changes, right ? Can you do "cat /sys/bus/pnp/devices/00\:*/id" (under either kernel) and copy and paste the output here please ? Yes, precisely. The only change was to boot into the older kernel. No other changes, not even modifying any kernel options. In 3.14.7-200 kernel idefix ~> cat /sys/bus/pnp/devices/00\:*/id PNP0200 INT0800 PNP0103 PNP0c02 PNP0b00 INT3f0d PNP0c02 PNP0303 SYN2b2c SYN2b00 SYN0002 PNP0f13 PNP0c02 PNP0c02 Hi, Are you sure you where running the wrong kernel when making the first evemu-record.log ? Both logs look fine and more or less identical. Then again I've been looking at the changelog of the kernel and there is nothing which would explain this there, so it does make some sort of sense that they are both fine ... Can you do "dmesg" with the new kernel after reproducing the problem and see if there is anything which stands out there ? Regards, Hans So I booted back into 3.15.5-200 and the problem is gone. I'm attributing this to update gremlins. I did notice the problem immediately after upgrading so maybe there was some problem due to running software that was supposed to be for a different kernel. Anyway thanks for your help and sorry for taking up your time. Could be some process was eating up a lot of cpu on the first boot after the update, see the mail to Peter I CC-ed you on. Anyways lets close this then. |