Bug 61829

Summary:	Xorg crash on mouseclick in Inkscape when touchpad is disabled
Product:	xorg	Reporter:	Nils Ole Tippenhauer <noleti>
Component:	Input/evdev	Assignee:	Peter Hutterer <peter.hutterer>
Status:	RESOLVED DUPLICATE	QA Contact:	Xorg Project Team <xorg-team>
Severity:	normal
Priority:	medium	CC:	peter.hutterer
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Nils Ole Tippenhauer 2013-03-05 02:57:52 UTC

This is a replication of a bug at launchpad, which currently affects 20 users[1].

I am opening here in hope for possible feedback from devs. Please note that the bug potentially was fixed in the development versions (see below).

Short summary:
In inkscape, simply clicking on the workspace will crash Xorg, and throw the user back to login screen. For a detailed error message, please refer to the launchpad bug.
This bug seems to be related to disabled touchpads - all affected users used laptops. Enabling the previously disabled touchpad will prevent the crash. For some users, disabling the touchpad via software would not cause the crash, while for others there was no difference. Due to this correlation with input hardware, a bug in inkscape itself seems unlikely.

The bug disappeared with switching to the xorg-edgers ppa in Ubuntu, but it is unclear exactly why. 
The bug was still present in the following xorg-edgers package og xserver-xorg-core:
2:1.13.0+git20120920.70e57668-0ubuntu0ricotz
and disappeared in 
2:1.13.0.901+git20121123+server-1.13-branch.c0e68f8e-0ubuntu0ricotz~quantal


As very similar issues were reported before in launchpad[2] and declared fixed, there might be an underlying root cause which is still open.


Links:
[1]: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1081108 
[2]: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1023004

Comment 1 Peter Hutterer 2013-03-05 03:54:01 UTC

Please, if you already know that the bug was present in 1.13.0 and not anymore in 1.13.0.901, check the git log between those versions. It would have likely taken you less time than filing a new bug.

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

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.