When enabling the pidgin-blinklight plugin my Pidgin crashes. Perhaps the backtrace below will help.

#0  0x00007f7a713c4107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00007f7a713c54e8 in __GI_abort () at abort.c:89
#2  0x00007f7a713bd226 in __assert_fail_base (fmt=0x7f7a714f3ce8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
    assertion=assertion@entry=0x7f7a74086f60 "!xcb_xlib_threads_sequence_lost", file=file@entry=0x7f7a74086dab "../../src/xcb_io.c", line=line@entry=274,
    function=function@entry=0x7f7a74087266 "poll_for_event") at assert.c:92
#3  0x00007f7a713bd2d2 in __GI___assert_fail (assertion=0x7f7a74086f60 "!xcb_xlib_threads_sequence_lost", file=0x7f7a74086dab "../../src/xcb_io.c", line=274,
    function=0x7f7a74087266 "poll_for_event") at assert.c:101
#4  0x00007f7a74013a79 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#5  0x00007f7a74013b2b in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#6  0x00007f7a74013e3d in _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7  0x00007f7a74005777 in XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#8  0x00007f7a72ef5c42 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
#9  0x00007f7a71fda8c1 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f7a71fdae83 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f7a71fdb272 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f7a73284597 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#13 0x00005634162fe557 in main (argc=1, argv=0x7ffcb7c29118) at /tmp/buildd/pidgin-2.10.11/./pidgin/gtkmain.c:937

This is on a Thinkpad T-430.

Hi,

thanks for the report. Unfortunately, I cannot reproduce it here. When
exactly does the crash happen? When you install the plugin? When you
enable the plugin in the pidgin settings?

Greetings,
Joachim

Unreproducible bugs are the worst. :/

The crash occurs when I enable the plugin in the Pidgin settings
(Tools → Plugins).

I should have mentioned in the initial report that the `thinkpad_acpi`
module is loaded and Fn+Space will turn on the "thinklight".

If there's anything that you'd like me to try, or if more information is
required, please do not hesitate to let me know.

Hi,

Am Freitag, den 02.10.2015, 23:01 +0000 schrieb kytv:

indeed.
yourself... Here are some ideas:

Create a new user (with an pristine home directory) and see if you can
reproduce it.

See if other plugins need to be enabled for it to happen.

I am also a bit surprised by the traceback: pidgin-blinklight does not
really need to interact with X11. The error seems to be related to
threading, which my plugin also does not do (I believe).

Greetings,
Joachim

On Sat, Oct 03, 2015 at 09:57:26AM +0200, Joachim Breitner wrote:

Thanks for the quick replies. :)

I can. :(

I've currently got the following packages matching '*pidgin*' installed:

    ii  pidgin              2.10.11-1    amd64        graphical multi-protocol instant messaging client for X
    ii  pidgin-blinklight   0.11.1-2     amd64        Blinks your ThinkPad's ThinkLight upon new messages
    ii  pidgin-data         2.10.11-1    all          multi-protocol instant messaging client - data files
    ii  pidgin-dbg          2.10.11-1    amd64        Debugging symbols for Pidgin
    ii  pidgin-otr          4.0.1-1      amd64        Off-the-Record Messaging plugin for Pidgin
    ii  pidgin-themes       0.2-1        all          Smiley themes collection for pidgin

In the new/pristine user profile I made sure that none of the  plugins were
enabled. I then put the check in the box for Pidgin-Blinklight and I got
the crash that I originally reported.

I don't know what's going on there. :/

The output on the console:

    [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.
    pidgin: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
    Aborted
    [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.
    pidgin: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

For the heck of it I tried to make a binNMU package to ensure it's built
against the current dependencies in Debian Jessie but the crashing
persists.