Bug 331937 - poll_for_event: assertion !xcb_xlib_threads_sequence_lost fails after editing metadata of a few videos and/or after viewing a few videos
Summary: poll_for_event: assertion !xcb_xlib_threads_sequence_lost fails after editing...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-MetadataEdit (show other bugs)
Version: 3.5.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-10 03:03 UTC by Christian Gottschall
Modified: 2017-07-11 10:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.12.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Gottschall 2014-03-10 03:03:53 UTC
I try to add metadata (description, title, keywords) to a few videos. In order to be sure that I add the correct data, I view the respective video before actually entering metadata. After a few videos (sometimes three, sometimes five), digikam reliably crashes with/after an assertion !xcb_xlib_threads_sequence_lost. ("digikam: xcb_io.c:274: poll_for_event: Zusicherung »!xcb_xlib_threads_sequence_lost« nicht erfüllt.")

On stdout/stderr, I get the following messages:

** (digikam:30930): WARNING **: gstvideo: failed to get caps of pad xvimagesink0:sink
** (digikam:30930): WARNING **: gstvideo: failed to get caps of pad xvimagesink0:sink
[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.
digikam: xcb_io.c:274: poll_for_event: Zusicherung »!xcb_xlib_threads_sequence_lost« nicht erfüllt.

Reproducible: Always

Steps to Reproduce:
1. View a few videos.
2. Edit their metadata (title, comments)
3. go to 1.
Actual Results:  
Digikam crashes with:

[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.
digikam: xcb_io.c:274: poll_for_event: Zusicherung »!xcb_xlib_threads_sequence_lost« nicht erfüllt.

Expected Results:  
Digikam does not crash.
Comment 1 caulier.gilles 2014-03-10 09:32:36 UTC
XCB are not relevant of digiKam. It's another in-deep problem from your installation.

In all case, if there is a digiKAm crash, getting a GDB backtrace must provide advanced information to hack. Read this page for details :

http://www.digikam.org/contrib

Gilles Caulier
Comment 2 caulier.gilles 2015-06-29 17:45:33 UTC
New digiKam 4.11.0 is available with official PKG installer for OSX.

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier
Comment 3 Christian Gottschall 2015-06-29 18:18:09 UTC
This bug seems to have gone with Digikam 4.9.0 as shipped with OpenSUSE Tumbleweed.