Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, I have had the same problem, reportbug has not launched, and when I tried from command line, I got the messages Attempt to unlock mutex that was not locked Aborted I found that bug 763690 claims to have a patch to this. Z - --- System information. --- Architecture: amd64 Kernel: Linux 3.16-2-amd64 Debian Release: jessie/sid 500 testing-updates ftp.uk.debian.org 500 testing security.debian.org 500 testing ftp.uk.debian.org 500 testing deb.bitmask.net 500 stable deb.bitmask.net 1 experimentalftp.uk.debian.org - --- Package information. --- Depends (Version) | Installed ===-+-=== python (= 2.6) | 2.7.8-1 apt | 1.0.9.3 python-reportbug (= 6.5.0+nmu1) | 6.5.1 python (= 2.6) | 2.7.8-1 python-support (= 0.90.0) | 1.0.15 apt | 1.0.9.3 python-debian | 0.1.24 python-debianbts| 1.12 Package's Recommends field is empty. Suggests (Version) | Installed -+- postfix | OR exim4| 4.84-2 OR mail-transport-agent | gnupg| 1.4.18-4 OR pgp | debconf-utils ( 1.1.0) | debsums (= 2.0.47) | file ( 1.30) | 1:5.19-2 dlocate | python-urwid | python-gtk2 | 2.24.0-4 python-vte | 1:0.28.2-5 python-gtkspell | 2.25.3-13 xdg-utils| 1.1.0~rc1+git20111210-7.1 emacs22-bin-common | OR emacs23-bin-common | claws-mail(= 3.8.0) | reportbug| 6.5.1 - --- Output from package bug script --- reportbug_version 6.4.4 mode standard ui gtk2 realname Z email b...@theloosespoke.org.uk no-cc header X-Debbugs-CC: b...@theloosespoke.org.uk smtphost reportbug.debian.org -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJUQ3J5AAoJEC8Z0Emvryki5QEIAJd3ht2DOm8Dgf32xE8fNoQl +G1wvriZXyXYdH5FbctHTFoHrmQHFn43sQXTjy8JSMfpextQXir2fIHij0aRtdmw ZCVxIHng+sW1A/0X2azDIsv+LVOgo2rPagoemDmZrf/p6phhoi3Ic1JbbfHf2ENT Slzg/eClr4g1CBN63MRcpBIv1tuZ88IGwW3D4mTIGQMJSXIH0gB+yjM2ZkBkaeQn 67/CC2xmOdDIMks6qIf3vB7VDVHDmzOiJl/8IlfbeTHZ+dCJmFbi0ZLyRtiJIFeJ ePJ961mX3fBl/XNSTKaUikkPCz+guyqCaqI1Qxm7GTLW6yCx1PbIlZaABf2GIj4= =2Ie9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
It seems, that there a several applications with that error. pyrenamer and gftp also have that issue. Thomas -- gpg-id: ccdbc2cf https://www.setho.org/people signature.asc Description: OpenPGP digital signature
Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
Package: reportbug Version: 6.5.1 Followup-For: Bug #758619 What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Environment settings: INTERFACE=text ** /home/tester/.reportbugrc: reportbug_version 6.4.4 mode novice ui gtk2 no-cc header X-Debbugs-CC: tester@localhost.localdomain smtphost reportbug.debian.org -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages reportbug depends on: ii apt 1.0.9.2 ii python2.7.8-1 ii python-reportbug 6.5.1 pn python:anynone reportbug recommends no packages. Versions of packages reportbug suggests: ii claws-mail 3.10.1-4 pn debconf-utils none ii debsums2.0.52+nmu2 pn dlocatenone ii emacs23-bin-common 23.4+1-4.1+b1 ii exim4 4.84-2 ii exim4-daemon-light [mail-transport-agent] 4.84-2 ii file 1:5.19-2 ii gnupg 1.4.18-4 ii python-gtk22.24.0-4 ii python-gtkspell2.25.3-13 pn python-urwid none ii python-vte 1:0.28.2-5 ii xdg-utils 1.1.0~rc1+git20111210-7.1 Versions of packages python-reportbug depends on: ii apt 1.0.9.2 ii python-debian 0.1.23 ii python-debianbts 1.12 pn python:anynone python-reportbug suggests no packages. -- Configuration Files: /etc/reportbug.conf changed: submit query-bts cc config-files compress email humbe...@example.com smtphost reportbug.debian.org verify -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
This grave bug is still present in reportbug 6.5.1 on fully patched sid, preventing all bug reporting: $ reportbug Attempt to unlock mutex that was not locked Aborted Kind regards, -- Ben Caradoc-Davies b...@wintersun.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
On Tue, 19 Aug 2014 at 12:08:39 +0200, Jan Binder wrote: reportbug just aborts with exit code 134 when it is started. ... Attempt to unlock mutex that was not locked I can't reproduce this: reportbug reportbug (with the default text-mode UI) and reportbug --ui=gtk2 reportbug both seem to work fine here. For those who can reproduce it, a backtrace with libgtk2.0-0-dbg, libglib2.0-0-dbg and python-gtk2-dbg installed, using thread apply all bt instead of just bt, would be useful information. It would also be useful if someone who can reproduce this could send the output of these commands run in a terminal: reportbug --template libgtk2.0-0 reportbug --template reportbug which I think will work despite this bug. On Tue, 19 Aug 2014 at 11:15:31 +0100, Sandro Tosi forwarded: (gdb) bt #0 0x76f28407 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x76f297e8 in __GI_abort () at abort.c:89 #2 0x72cdc85d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x719f4bbf in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #4 0x720a7d54 in ?? () from /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/_gtk.so #5 0x74148a99 in ?? () from /usr/lib/python2.7/lib-dynload/readline.x86_64-linux-gnu.so #6 0x00448d04 in PyOS_Readline () This looks more like a bug in Gtk2 or python-gtk2 than a GLib bug. Frame 3 is in gtk_main(), frame 2 is in GLib which just issued a message Attempt to unlock mutex that was not locked, and frame 1 is abort(): this indicates that it was probably frame 3 (gtk_main()) that behaved incorrectly. The only way to address this bug from within GLib would be to remove the check that says unlocking a mutex that isn't locked is not allowed, or reduce it from fatal to non-fatal but keep the spam to stderr. If something is unlocking a mutex that isn't locked, that's a symptom of a serious multi-threading bug somewhere (which could equally easily manifest as a thread releasing a lock that it does not actually hold, causing unsafe actions elsewhere), so I think it is correct that it is fatal to make it as visible as possible. I notice with some trepidation that /usr/share/pyshared/reportbug/ui/gtk2_ui.py uses both Gtk and threads. I wonder whether the root cause of this bug might be something like the first use of Gtk2 happened to be from a non-main thread? S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
Package: reportbug Version: 6.5.0+nmu1 Severity: grave reportbug just aborts with exit code 134 when it is started. $ reportbug Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. Attempt to unlock mutex that was not locked zsh: abort reportbug -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
