Ubuntu
xserver-xorg-input-synaptics package

  1. Bug #774978
  2. Comment #52

Comment 52 for bug 774978

Revision history for this message
Bryce Harrington (bryce) wrote :

Directions on gathering full traces are here:

  http://wiki.ubuntu.com/X/Backtracing

From what I've seen, the easy Apport approach doesn't seem to work with this class of crash for some odd reason, so you'll probably need to use the gdb method. Install debug symbol packages for the xserver, intel driver, and libdrm2 as a minimum.

If you have this same crash, you should see a line with librecord.so towards the top of the stack. You should also see a CallCallbacks entry and possibly an entry for libpthread.so. If you don't see librecord.so at all, then you almost certainly have some unrelated crash, particularly if you have the 12.1 -synaptics installed, restarted X, and it still crashed.

Aside from the 12.1 package, there are also several workarounds which seem effective in preventing the crash:
  a. Turn off the "Disable touchpad while typing" option in the mouse settings gui
  b. Uninstall xserver-xorg-input-synaptics
  c. Rename the /usr/lib/xorg/modules/extensions/librecord.so to prevent the module from even loading

iFred, re-reviewing all the information you've provided, and especially the fact that you tried renaming librecord.so, I think you have some other unrelated crash bug. Please file a new bug report via 'ubuntu-bug xorg', and collect a full backtrace and attach to that bug report.

All X crash bugs basically have exactly the same symptoms - you're suddenly dropped back to the login screen, and some crude backtrace is listed in your Xorg.0.log. But those Xorg.0.log crash dumps are generally fairly worthless; sometimes it is enough to spot dupe bugs, but often (like in these cases) there can be some ambiguity. So it's unfortunately quite easy to confuse one person's crash with another (I even get them confused.) Full backtraces are needed to be absolutely sure. These provide exactly which line numbers and functions in each file were involved, and usually even shows the values of different variables. Often with the full traces a skilled eye can spot the flaw right off the bat. The Xorg.0.log crash dumps don't have any of this information.