Bug 1318706 - Test case failure: driver loading
Summary: Test case failure: driver loading
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-drv-synaptics
Version: 6.8
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Peter Hutterer
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-17 14:38 UTC by Tomas Hudziec
Modified: 2016-09-12 15:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-12 15:20:42 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tomas Hudziec 2016-03-17 14:38:30 UTC 
Filed from caserun https://tcms.engineering.redhat.com/run/273975/

Version-Release number of selected component (if applicable):
RHEL-6.8-20160218.n.0
xorg-x11-drv-synaptics-1.8.3-1.el6.x86_64

Steps to Reproduce: 
Obtain a laptop with synaptic-compatible touchpad.

Make sure that xorg.conf include synaptic as an input device driver.

 1. Start your laptop.
 2. Watch Xorg.log

Actual results: 
two bugs appear in Xorg.0.log:
(!!) BUG: Device "SynPS/2 Synaptics TouchPad" received a double tracking ID 0 in slot 0.
(!!) BUG: Device "SynPS/2 Synaptics TouchPad" received a double tracking ID 3 in slot 1.

Expected results:
No crashes or errors regarding synaptic should appear.
Comment 2 Peter Hutterer 2016-04-04 05:25:32 UTC 
do you have the xorg logs from that run? Was this with a virtual device or something present?

you should only get that message when you receive events, and if you get ids in two slots then this would indicate two-finger scrolling or something.


Note that this is an error sent by libevdev (i.e. below synaptics) and it indicates a bad event sequence from the kernel. That can happen with virtual devices easily.
Comment 3 Tomas Pelka 2016-09-12 15:20:42 UTC 
I don't think this is an issue anymore.
Note You need to log in before you can comment on or make changes to this bug.