linuxdcpp assert failure: linuxdcpp: ../../src/xcb_io.c:140: dequeue_pending_request: Проверочное утверждение «req == dpy->xcb->pending_requests» не выполнено.

[Michael Sinchenko]

Binary package hint: linuxdcpp

 1

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: linuxdcpp 1.0.3-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
NonfreeKernelModules: wl
Architecture: i386
AssertionMessage: linuxdcpp: ../../src/xcb_io.c:140: dequeue_pending_request: Проверочное утверждение «req == dpy->xcb->pending_requests» не выполнено.
CrashCounter: 1
Date: Sun Apr 3 09:38:47 2011
ExecutablePath: /usr/bin/linuxdcpp
ProcCmdline: linuxdcpp
ProcEnviron:
 LANGUAGE=ru_RU:en
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: linuxdcpp
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: linuxdcpp assert failure: linuxdcpp: ../../src/xcb_io.c:140: dequeue_pending_request: Проверочное утверждение «req == dpy->xcb->pending_requests» не выполнено.
UpgradeStatus: Upgraded to natty on 2011-03-25 (9 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Steven Sheehy (steven-sheehy)]

This looks pretty similar to bug #502673. Regardless, we no longer call gdk_flush() in our latest code so you shouldn't experience this issue. Please try our PPA to confirm it is no longer an issue:

https://launchpad.net/~linuxdcpp-team/+archive/ppa

[Maia Everett (linneris)]

I can confirm this crash. Perhaps it would make sense to release a SRU for Natty to fix it, since it makes the application unusable.

Steven, would it be possible to get a minimal patch to backport the fix to the version in Natty?

[Maia Everett (linneris)]

This issue still persists in release 1.1.0.

[Steven Sheehy (steven-sheehy)]

This is just one of many crashing bugs fixed in 1.1.0. I would prefer to get 1.1.0 into natty than hack a patch for 1.0.3. I see you merged 1.1.0 into 11.10 but marked as invalid for 11.04. Is it not possible to upgrade it for natty as well? There are some security related bugs fixed in the DC++ core as well so I think it makes sense to upgrade natty.

[Steven Sheehy (steven-sheehy)]

Hmm...missed the part where you said it persists in 1.1.0. Can you provide a stacktrace (with debugs preferably), because I'm guessing it's different since we don't call gdk_flush() anymore. Thus I still think this is fixed in 1.1.0.

[Maia Everett (linneris)]

Here is the backtrace from gdb:

Starting program: /usr/bin/linuxdcpp
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffedea8700 (LWP 2367)]
[New Thread 0x7fffed6a7700 (LWP 2368)]
[Thread 0x7fffed6a7700 (LWP 2368) exited]
[New Thread 0x7fffed6a7700 (LWP 2369)]
[New Thread 0x7fffecea6700 (LWP 2370)]
[New Thread 0x7fffec6a5700 (LWP 2371)]
[New Thread 0x7fffebc9e700 (LWP 2372)]
[New Thread 0x7fffeb49d700 (LWP 2373)]

(linuxdcpp:2362): GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' failed
[New Thread 0x7fffe8d0e700 (LWP 2381)]
linuxdcpp: ../../src/xcb_io.c:140: dequeue_pending_request: Проверочное утверждение «req == dpy->xcb->pending_requests» не выполнено.

Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffecea6700 (LWP 2370)]
0x00007ffff4ac7d05 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x00007ffff4ac7d05 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007ffff4acbab6 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x00007ffff4ac07c5 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
#3 0x00007ffff6eb9ac1 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#4 0x00007ffff6eba9ec in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#5 0x00007ffff6f07d16 in XkbGetState () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#6 0x00007ffff5fba414 in gdk_keymap_get_direction () from /usr/lib/libgdk-x11-2.0.so.0
#7 0x00007ffff63fa6ca in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#8 0x00007ffff63fe04c in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#9 0x00007ffff63fe199 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#10 0x00007ffff63fe3d9 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x00007ffff5acb81c in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x00007ffff5adce1f in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x00007ffff5ae6258 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x00007ffff5ae641f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x00007ffff645e8bc in gtk_widget_set_scroll_adjustments () from /usr/lib/libgtk-x11-2.0.so.0
#16 0x00007ffff63a61d5 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#17 0x00007ffff5acb81c in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x00007ffff5adc7e3 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#19 0x00007ffff5ae6258 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#20 0x00007ffff5ae641f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x00007ffff6a66af5 in glade_standard_build_children () from /usr/lib/libglade-2.0.so.0
#22 0x00007ffff6a6562c in glade_xml_set_common_params () from /usr/lib/libglade-2.0.so.0
#23 0x00007ffff6a65a76 in glade_xml_build_widget () from /usr/lib/libglade-2.0.so.0
#24 0x00007ffff6a6c871 in ?? () from /usr/lib/libglade-2.0.so.0
#25 0x00007ffff6a6562c in glade_xml_set_common_params () from /usr/lib/libglade-2.0.so.0
#26 0x00007ffff6a65a76 in glade_xml_build_widget () from /usr/lib/libglade-2.0.so.0
#27 0x00007ffff6a66ab4 in glade_standard_build_children () from /usr/lib/libglade-2.0.so.0
#...

[Maia Everett (linneris)]

If it helps, I run linuxdcpp under KDE 4.6.2 in Natty, with KWin in compositing mode, with the NVIDIA proprietary driver.

[Razzloss (razzloss)]

What gtk theme do you use (there at least used to be setting for this in KDE systemsettings, but couldn't find it immediately in 4.4.5)? And does this happen if you change the gtk theme?

--RZ

[Maia Everett (linneris)]

I reproduced this bug with the Oxygen, Adwaita and Raleigh GTK themes.

[Steven Sheehy (steven-sheehy)]

Doesn't look like the same issue to me since the stacktrace is completely different. Regardless, it seems to be some sort of library issue and not caused by linuxdcpp. There have been various library issues before with people running linuxdcpp using theme engines on non-GTK+ based desktop environments. This issue originates when loading the glade xml via libglade, so moving to GtkBuilder will as a side effect fix this issue, but I'm not sure that libglade is the actual cause.

[Steven Sheehy (steven-sheehy)]

As I've said, the issue in the original description has been fixed in 1.1.0. The issue with libglade is a separate bug, which will be tracked via bug #836117.

[Chinmay Rajhans (rajhanschinmay)]

Getting this error most of the times:

linuxdcpp: ../../src/xcb_io.c:140: dequeue_pending_request: Assertion `req == dpy->xcb->pending_requests' failed.

Using Ubuntu 11.04 version and linuxdcpp 1.0.3 or core version 0.698.

Kindly post a possible solution.
Thank you.

[dino99 (9d9)]

eol reached https://wiki.ubuntu.com/Releases