Bug 7343 - Ungrab/DISABLEGRAB and ClearGrab/CLOSECLIENT don't work
Summary: Ungrab/DISABLEGRAB and ClearGrab/CLOSECLIENT don't work
Status: RESOLVED DUPLICATE of bug 7097
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.1 (2006.05)
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
Keywords: patch, regression
Depends on:
Reported: 2006-06-27 17:52 UTC by Karl Tomlinson
Modified: 2006-07-04 04:11 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

correct case in XkbDDXPrivate (1.05 KB, patch)
2006-06-27 17:55 UTC, Karl Tomlinson
no flags Details | Splinter Review

Description Karl Tomlinson 2006-06-27 17:52:50 UTC
Apparently caused by this change:


where strcmp is used instead of strcasecmp, but the cases don't match as
indicated in the log messages:

RADEONHandleMessage(0, "KeyEventMessage", "ClsGrb", retmsg)
RADEONHandleMessage(0, "KeyEventMessage", "Ungrab", retmsg)

(AllowDeactivateGrabs and AllowClosedownGrabs are on.)
Comment 1 Karl Tomlinson 2006-06-27 17:55:42 UTC
Created attachment 6061 [details] [review]
correct case in XkbDDXPrivate





it looks like this patch is appropriate.

This fixes Ungrab and ClearGrab, tested with xmag.

I don't use +/-vmode so haven't tested these.
Comment 2 Karl Tomlinson 2006-06-27 18:01:15 UTC
Also, if anyone could tell me if there is a way to tell what process is holding 
an active input grab, that would be very helpful for me trying to work out why 
I need to do an Ungrab occasionally after VT switch.

(The same processes appear to be running after a ClearGrab in this case.)
Comment 3 Daniel Stone 2006-07-04 04:11:37 UTC

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

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.