-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
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 =
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
Your message dated Fri, 10 Oct 2014 18:19:02 +
with message-id e1xcemm-00064e...@franck.debian.org
and subject line Bug#758619: fixed in gtk+2.0 2.24.25-1
has caused the Debian Bug report #758619,
regarding reportbug fails with Attempt to unlock mutex that was not locked
to be marked as done.
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
___
Reportbug-maint mailing list
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 for
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)
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-maint@lists.alioth.debian.org
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:
Your message dated Fri, 05 Sep 2014 21:52:24 +
with message-id e1xq1qe-0005ej...@franck.debian.org
and subject line Bug#758619: fixed in reportbug 6.5.1
has caused the Debian Bug report #758619,
regarding reportbug fails with Attempt to unlock mutex that was not locked
to be marked as done.
It means almost nobody can report bug on unstable.
A working patch is available
-- eric
___
Reportbug-maint mailing list
Reportbug-maint@lists.alioth.debian.org
# 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
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,
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
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
15 matches
Mail list logo
