SikuliX

[xcb] Unknown sequence number while processing queue

Asked by Karl

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?

Question information

Language:
English Edit question
Status:
Solved
For:
SikuliX Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
RaiMan (raimund-hocke) said : 		#1

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.

Just check.

Revision history for this message
Karl (k-d) said : 		#2

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

Revision history for this message
RaiMan (raimund-hocke) said : 		#3

not with the SikuliX builtin features.

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

Revision history for this message
Karl (k-d) said : 		#4

Both of our installs are 32-bit. This may be an accomplice.

Revision history for this message
Karl (k-d) said : 		#5

I thought 64-bit solved the problem, but the error has occurred -- just less frequently.

Revision history for this message
RaiMan (raimund-hocke) said : 		#6

I made it a bug.