-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
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
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
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
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
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
6 matches
Mail list logo
