Bug#758619: Reportbug closes with mutex locking issue

2014-10-21 Thread Prema
Package: Reportbug Version: 6.5.1 Reportbug crashes with the Attempt to unlock mutex that was not locked Aborted error. 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

Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked

2014-10-19 Thread bugs
-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

Bug#758619: reportbug and pyrenamer problems are not fixed on Jessie

2014-10-13 Thread sp113438
I (on Jessie up-to-date) still have this problems # reportbug Attempt to unlock mutex that was not locked Aborted and # pyrenamer /usr/lib/pymodules/python2.7/pyrenamer/pyrenamer.py:120: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page size is deprecated self.glade_tree =

Bug#758619: reportbug and pyrenamer problems are not fixed on Jessie

2014-10-13 Thread Jonathan Wiltshire
On 2014-10-13 22:43, sp113438 wrote: I (on Jessie up-to-date) still have this problems # reportbug Attempt to unlock mutex that was not locked Aborted and # pyrenamer /usr/lib/pymodules/python2.7/pyrenamer/pyrenamer.py:120: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page

Bug#758619: pyrenamer: Attempt to unlock mutex that was not locked

2014-10-08 Thread sp113438
pyrenamer also gives: Attempt to unlock mutex that was not locked Aborted Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758619: Attempt to unlock mutex that was not locked

2014-10-08 Thread sp113438
It happens on Sid as well as Jessie (amd64). Thanks -- 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

2014-10-07 Thread Thomas Maaß
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

2014-10-03 Thread tester
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

Bug#758619: (no subject)

2014-10-02 Thread twied
fwiw: gftp crashes with the same symptoms, see #763371 - tim Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages reportbug depends on: ii apt 1.0.9.1 ii python

Bug#758619: reportbug: Can confirm, reportbug fails with GTK, not in text mode

2014-10-01 Thread Sebastian Schulze
Package: reportbug Version: 6.5.1 Followup-For: Bug #758619 Dear Maintainer, * What led up to the situation? Trying to report a bug on another package (pidgin-skype), which curiously fails with the exact same error message. Saw this exact same error unable to unlock mutex

Bug#758619: The fix was intended/verified for a non graphical useage

2014-10-01 Thread Eric Valette
At least the fix, solves this use case (at least for me). And as the bug is in pygtk2 which is dead, maybe the bug should be reassigned. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#758619:

2014-10-01 Thread Chris Bainbridge
This bug now exists in Testing (glib2.0-2.42.0 has just been migrated to Testing). reportbug --ui=text xxx still works. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#758619: more complete backtrace

2014-09-22 Thread Simon McVittie
On 21/09/14 22:47, Sandro Tosi wrote: On Thu, Aug 21, 2014 at 10:38 AM, Simon McVittie s...@debian.org wrote: +gtk.set_interactive (0) gtk.gdk.threads_init () sadly this patch didnt fix the problem, and I can replicate it in a clean sid chroot. do you have any other suggestions? The next

Bug#758619: more complete backtrace

2014-09-21 Thread Sandro Tosi
Hello Simon, On Thu, Aug 21, 2014 at 10:38 AM, Simon McVittie s...@debian.org wrote: --- gtk2_ui.py.orig 2014-08-21 09:28:45.375375786 + +++ gtk2_ui.py 2014-08-21 09:29:02.843495121 + @@ -35,6 +35,7 @@ except: has_spell = False +gtk.set_interactive (0)

Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked

2014-09-21 Thread Ben Caradoc-Davies
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

Bug#758619:

2014-09-11 Thread Ludovic Lebègue
Hi Version 6.5.1 is installed on my system and the bug is still there. = apt show reportbug Package: reportbug Version: 6.5.1 Installed-Size: 226 kB Maintainer: Reportbug Maintainers reportbug-ma...@lists.alioth.debian.org

Bug#758619: [reportbug/master] uninstall GTK+ readline hook, this prevent a crash in reportbug; thanks to Eric Valette for the report and to Simon McVittie for the GTK+-side analysis and patch; Closes

2014-09-05 Thread Sandro Tosi
tag 758619 pending tag 758619 pending thanks Date: Thu Sep 4 23:14:37 2014 +0100 Author: Sandro Tosi mo...@debian.org Commit ID: 0d118098881a15a92a089ed20ba3e2eb08cfc4b7 Commit URL:

Bug#758619: Why still not fixed!

2014-09-04 Thread Eric Valette
It means almost nobody can report bug on unstable.  A working patch is available -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#758619: more complete backtrace

2014-08-21 Thread Simon McVittie
forwarded 758619 https://bugzilla.gnome.org/show_bug.cgi?id=735141 found 758619 glib2.0/2.41.2-1 notfound 758619 glib2.0/2.40.0-4 thanks On 20/08/14 22:50, Eric Valette wrote: Because I use the glib/gtk from experimental I guess. Thanks, yes, it's that. Specifically, this change:

Bug#758619: more complete backtrace

2014-08-21 Thread Eric Valette
On 08/21/2014 10:26 AM, Simon McVittie wrote: In particular, the abort on incorrect locking is new; the original plan seems to have been for it to be runtime-optional. I've sent this upstream to ask whether runtime-optional is feasible. Well instead of correcting the symptom, I would

Bug#758619: more complete backtrace

2014-08-21 Thread Eric Valette
On 08/21/2014 10:37 AM, Eric Valette wrote: Searching for the bug, I saw that, in the past, the very same undefined behavior caused crash instead of and assert. http://debian.2.n7.nabble.com/Bug-671785-segfaults-when-running-reportbug-td548240.html meaning the bug is not new and was

Bug#758619: Much simpler code to trigger the problem (extract from bug #671785)

2014-08-21 Thread Eric Valette
On 08/21/2014 10:52 AM, Eric Valette wrote: cat test.py #!/usr/bin/python import gtk gtk.gdk.threads_init() raw_input(If this didn't crash, hit enter.) 2 r-x-ceva6380:~-python test.py If this didn't crash, hit enter.Attempt to unlock mutex that was not locked Aborted #!/usr/bin/python import

Bug#758619: more complete backtrace

2014-08-21 Thread Simon McVittie
# the real bug is #671785 but it's easy to avoid it in reportbug reassign 758619 reportbug tags 758619 + patch thanks On 21/08/14 09:37, Eric Valette wrote: Well instead of correcting the symptom, I would prefer to correct the bug itself. If locking mecahnism is hazardous, then it eman

Bug#758619: more complete backtrace

2014-08-21 Thread Eric Valette
--- gtk2_ui.py.orig 2014-08-21 09:28:45.375375786 + +++ gtk2_ui.py2014-08-21 09:29:02.843495121 + @@ -35,6 +35,7 @@ except: has_spell = False +gtk.set_interactive (0) gtk.gdk.threads_init () import sys I confirm this also fixes the bug for me. Thanks for

Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked

2014-08-20 Thread Simon McVittie
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

Bug#758619: requested additional info

2014-08-20 Thread VALETTE Eric OLNC/OLPS
reportbug --template libgtk2.0-0 *** Welcome to reportbug.  Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect.

Bug#758619: more complete backtrace

2014-08-20 Thread VALETTE Eric OLNC/OLPS
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

Bug#758619: more complete backtrace

2014-08-20 Thread Simon McVittie
Did you upgrade a package recently that could have triggered this, i.e. related to Python, GLib, Gtk 2 or reportbug? I would be interested to know why this is new. Some analysis below. I think this is probably a pygtk bug, but there is a workaround that reportbug could use. On 20/08/14 12:15,

Bug#758619: more complete backtrace

2014-08-20 Thread Eric Valette
On 20/08/2014 22:46, Simon McVittie wrote: Did you upgrade a package recently that could have triggered this, i.e. related to Python, GLib, Gtk 2 or reportbug? I would be interested to know why this is new. Because I use the glib/gtk from experimental I guess. And you could have noticed it by

Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked

2014-08-19 Thread Jan Binder
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

Bug#758619: [Reportbug-maint] reportbug is broken due to glib

2014-08-19 Thread Sandro Tosi
control: reassign -1 libglib2.0-0 control: affects -1 reportbug Hello, thanks for the trace; I'm forwarding this info to the bug report and reassign it to glib. Regards, Sandro On Mon, Aug 18, 2014 at 4:13 PM, VALETTE Eric OLNC/OLPS eric2.vale...@orange.com wrote: gdb --args python