Bug 54934 - Crash on XGrabDevice() of deactivated synaptics device
Summary: Crash on XGrabDevice() of deactivated synaptics device
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/Input/Core (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
: 53263 61829 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-09-14 16:02 UTC by Owen Taylor
Modified: 2013-03-05 03:54 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Owen Taylor 2012-09-14 16:02:25 UTC 
I have the touchpad on my Thinkpad deactivated by default.

If I do any manipulations in Inkscape (using GTK+ 2 with XInput support enabled) without activating the touchpad, it tries to grab all pointer devices with XGrabDevice() and the grab on the touchpad device crashes the X server with a backtrace pointing to dix/events.c:ActivateKeyboardGrab()

    if (grabinfo->grab)
        oldWin = grabinfo->grab->window;
    else if (keybd->focus)
        oldWin = keybd->focus->win;
    else
>       oldWin = keybd->spriteInfo->sprite->win;

So probably spriteInfo or sprite is NULL. (ActivateKeyboardGrab is commented as the normal grab activation function for extension devices.)
Comment 1 Peter Hutterer 2012-09-27 06:14:03 UTC 
*** Bug 53263 has been marked as a duplicate of this bug. ***
Comment 2 Peter Hutterer 2012-09-28 02:28:11 UTC 
http://patchwork.freedesktop.org/patch/12102/
Comment 3 Peter Hutterer 2012-10-08 01:48:42 UTC 
commit 9d6b8365702e4648e793fea21ad22f7174558680
Author: Peter Hutterer <peter.hutterer@who-t.net>
Date:   Fri Sep 28 11:49:29 2012 +1000

    dix: fix crash on XI 1.x grabs on disabled devices.  (#54934)
Comment 4 Peter Hutterer 2013-03-05 03:54:01 UTC 
*** Bug 61829 has been marked as a duplicate of this bug. ***

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.