[1.1.0] Linux: JXGrabkey: [xcb] Unknown sequence number while processing queue

Bug #1518895 reported by RaiMan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SikuliX
Won't Fix
Undecided
Unassigned

Bug Description

I keep getting the following error irregularly while running sikuli tests:

[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
java: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)

I am importing a class from a module and it uses the __init__ method to call a function that adds hotkeys and the complementary __del__ method to remove the hotkeys.

I noticed this issue on github (https://github.com/RaiMan/SikuliX-2014/issues/144), but I am running 1.0.1 because I haven't migrated to 1.1.x yet.

Is there an alternative for 1.0.1 to runsikulix?
Or /
Do you just know how to fix this problem?

Revision history for this message
RaiMan (raimund-hocke) wrote :

This is still pending, but again looking into the debug output in the issue, I now realized this:

[error] Hot key conflicts
[error] HotkeyManager: addHotkey: failed

so in the issue case, this might be the problem.

I remember jxgrabkey having some problems with this.

Is there a way to check what hotkeys are implemented and conditionally add the hot keys with try except?

not with the SikuliX builtin features.

But if this error happens, the addHotkey() should return false.

RaiMan (raimund-hocke)
Changed in sikuli:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.