[requestsync] crashed, doesn't handle gpg signing failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-dev-tools (Ubuntu) |
Fix Released
|
Medium
|
Stefano Rivera |
Bug Description
Binary package hint: ubuntu-dev-tools
Do you want to edit the report [y/N]? n
You need a passphrase to unlock the secret key for
user: "Martin-Éric Racine <email address hidden>"
1024-bit DSA key, ID 1E0CB9CD, created 2003-10-26
gpg: problem with the agent: IPC write error
gpg: Salasana ei kelpaa; yritä uudestaan ...
You need a passphrase to unlock the secret key for
user: "Martin-Éric Racine <email address hidden>"
1024-bit DSA key, ID 1E0CB9CD, created 2003-10-26
gpg: problem with the agent: Not supported
gpg: no default secret key: General error
gpg: [stdin]: clearsign failed: General error
Traceback (most recent call last):
File "/usr/bin/
mailBug(srcpkg, subscribe, status, title, report, options.keyid)
File "/usr/lib/
assert gpg.returncode == 0
AssertionError
ProblemType: Crash
Architecture: i386
Date: Thu Mar 11 13:42:45 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/
InterpreterPath: /usr/bin/python2.6
Package: ubuntu-dev-tools 0.95
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=fi_FI.UTF-8
LANGUAGE=
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: ubuntu-dev-tools
Title: requestsync crashed with AssertionError in mailBug()
Uname: Linux 2.6.32-15-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse-access scanner src sudo tape video
tags: | removed: need-duplicate-check |
summary: |
- requestsync crashed with AssertionError in mailBug() + [requestsync] crashed with AssertionError in mailBug() |
Changed in ubuntu-dev-tools (Ubuntu): | |
importance: | Undecided → Medium |
summary: |
- [requestsync] crashed with AssertionError in mailBug() + [requestsync] crashed, doesn't handle gpg signing failure |
Thank you for helping to improve Mythbuntu by opening this ticket. I am marking this ticket as confirmed because it appears to have enough information to help the developers understand the problem. It is possible I am wrong and another more experienced triager or developer may adjust the status of the ticket to "incomplete" and request additional information.