Bug 682593 - "Wrong event type 0" regular crash in Rawhide.
Summary: "Wrong event type 0" regular crash in Rawhide.
Keywords:
Status: CLOSED DUPLICATE of bug 688693
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-synaptics
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-07 00:01 UTC by Chris Ball
Modified: 2018-04-11 10:55 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-07-07 03:23:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg log containing crash (35.51 KB, text/plain)
2011-03-07 00:03 UTC, Chris Ball
no flags Details

Description Chris Ball 2011-03-07 00:01:59 UTC
Description of problem:

About three times a day (say, once every three hours of use) I get an Xorg SEGV with "Wrong event type 0" in the backtrace.  I think it's probably coming from the synaptics driver.

Version-Release number of selected component (if applicable):

ThinkPad W510.  No input devices other than the mouse/keyboard plugged in.

xorg-x11-server-Xorg-1.10.0-1.fc16.x86_64
xorg-x11-drv-nouveau-0.0.16-21.20110224gitbc5dec2.fc16.x86_64
xorg-x11-drv-synaptics-1.4.0-1.fc16.x86_64

How reproducible:

Not reproducible on demand, but I'd find out whether a fix worked after a day or two.

Steps to Reproduce:
1. Touch my ThinkPad's trackpoint or touchpad
2. If the bug happens, X will crash with the attached log.

Additional info:

The crash *only* ever happens at the start of a mouse movement -- never while just typing, or when the mouse pointer isn't moving.

Comment 1 Chris Ball 2011-03-07 00:03:17 UTC
Created attachment 482565 [details]
Xorg log containing crash

Comment 2 Matěj Cepl 2011-03-13 00:48:37 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Looking at https://fedoraproject.org/wiki/Xorg/Input_Triage_Algorithm, I have couple of pieces of data which can help us to debug this issue:

* your X server config file (/etc/X11/xorg.conf, if available, or any files in /etc/X11/xorg.conf.d/),
* log from evtest (the device seems to be /dev/input/event4),
* output of the dmesg command (especially if you can get to the console of the computer after the crash but before reboot; you can try to press Ctrl-Alt-F2 or via ssh), and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 3 Peter Hutterer 2011-06-21 04:35:37 UTC
Chris, could this be a dupe of #688693?

Comment 4 Peter Hutterer 2011-07-07 03:23:37 UTC
Pretending this is a dupe, please un-duplicate if that's not the case.

*** This bug has been marked as a duplicate of bug 688693 ***


Note You need to log in before you can comment on or make changes to this bug.