1. Summary
  2. Files
  3. Support
  4. Report Spam
  5. Create account
  6. Log in

Ticket #6 (closed defect: incomplete)

Opened 5 years ago

Last modified 4 years ago

Easystroke crashes when trying to add an application

Reported by: fragestunde Owned by: thjaeger
Priority: major Keywords: crash
Cc: thjaeger, fragestunde

Description

When trying an application (in my case nautilus) to easystroke for
application-dependend gestures, easystroke crashes with following
messages:

XError: BadValue? (integer parameter out of range for operation): X_UngrabButton
XError: BadValue? (integer parameter out of range for operation): X_UngrabButton
XError: BadValue? (integer parameter out of range for operation): X_UngrabButton
Fehler: Ein Grab ist fehlgeschlagen. Breche Geste ab...
Fehler: A grab failed
Fehler: A grab failed
easystroke: ../../src/xcb_io.c:176: process_responses: Assertion `!(req && current_request && !(((long) (req->sequence) - (long) (current_request)) <= 0))' failed.
Aborted

The german text means sth like: "A grab failed. Canceling gesture"
"Fehler" means "error"

This happens with the easystroke-package from the Ubuntu-repositories
(0.4.1.1) as well as with the package from sourceforge (0.4.9)

When starting easystroke there are some strange messages too, although
they don't prevent it from running:

Fehler: An XInput grab failed
Fehler: An XInput grab failed
Fehler: An XInput grab failed
Fehler: An XInput grab failed
Fehler: An XInput grab failed
Fehler: An XInput grab failed
Fehler: A grab failed
Fehler: A grab failed
Fehler: A grab failed

Change History

Changed 5 years ago by thjaeger

This is a hard problem to debug. There is probably some application running that already has a grab on the buttons (window manager perhaps?). The only way I know to get the server to reveal what application that is is to attach a gdb session to X and then break on XGrabDevice() button and inspect the server's internal data structures.

I would recommend you kill as many processes that could be responsible for this and see if this problem disappears.

The crash is a bug in the server or libX11/libXi, but also very mysterious.

Changed 4 years ago by thjaeger

  • cc thjaeger, fragestunde added

Changed 4 years ago by thjaeger

  • status changed from new to closed
  • resolution set to incomplete

Closing due to inactivity.

Note: See TracTickets for help on using tickets.