[Reportbug-maint] Bug#758619: Reportbug closes with mutex locking issue

Prema premum at gmail.com
Tue Oct 21 07:29:47 UTC 2014

Package: Reportbug
Version: 6.5.1

Reportbug crashes with the
 "Attempt to unlock mutex that was not locked

The backtrace for the same is

 gdb --args python /usr/bin/reportbug -b --no-check-available libpulse0

GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i586-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from python...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/python /usr/bin/reportbug -b
--no-check-available libpulse0
[Thread debugging using libthread_db enabled]
Using host libthread_db library
Gtk-Message: Failed to load module "canberra-gtk-module"
[New Thread 0xadb09b40 (LWP 25300)]
Attempt to unlock mutex that was not locked

Program received signal SIGABRT, Aborted.
0xb7fde424 in __kernel_vsyscall ()
(gdb) thread apply all bt

Thread 2 (Thread 0xadb09b40 (LWP 25300)):
#0  0xb7fde424 in __kernel_vsyscall ()
#1  0xb7e6350b in poll () at ../sysdeps/unix/syscall-template.S:81
#2  0xb6fc70b0 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb6fb8054 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb6fb8479 in g_main_loop_run () from
#5  0xb63d5955 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#6  0xb6fdf3da in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb7fa2efb in start_thread (arg=0xadb09b40) at pthread_create.c:309
#8  0xb7e6dd4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129

Thread 1 (Thread 0xb7d82700 (LWP 25294)):
#0  0xb7fde424 in __kernel_vsyscall ()
#1  0xb7db2267 in __GI_raise (sig=sig at entry=6) at
#2  0xb7db3923 in __GI_abort () at abort.c:89
#3  0xb6ffdb20 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb6665f74 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
#5  0xb67b2bc5 in gtk_dialog_run () from
#6  0xb6cb9283 in ?? () from
#7  0x08107c0c in PyEval_EvalFrameEx ()
#8  0x081078db in PyEval_EvalFrameEx ()
#9  0x081078db in PyEval_EvalFrameEx ()
#10 0x08105f4d in PyEval_EvalCodeEx ()
#11 0x0813a88c in ?? ()
#12 0x08131578 in PyRun_FileExFlags ()
#13 0x08130725 in PyRun_SimpleFileExFlags ()
#14 0x080daaa7 in Py_Main ()
#15 0x080da50b in main ()
(gdb) quit

Is there any patch available for this issue.

Prema S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/reportbug-maint/attachments/20141021/5af82f04/attachment.html>

More information about the Reportbug-maint mailing list