GnuPGInterface prints exit statuses incorrectly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnupginterface (Debian) |
Fix Released
|
Unknown
|
|||
gnupginterface (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: python-
duplicity can produce a traceback like this:
Traceback (most recent call last):
File "/usr/bin/
with_
File "/usr/bin/
fn()
File "/usr/bin/
incremental
File "/usr/bin/
bytes_written = write_multivol(
File "/usr/bin/
at_end = gpg.GzipWriteFi
File "/usr/lib/
new_block = block_iter.
File "/usr/lib/
result = self.process(
File "/usr/lib/
for new_path, sig_path in collated:
File "/usr/lib/
relem2 = riter2.next()
File "/usr/lib/
range(
File "/usr/lib/
path = path_iter_
File "/usr/lib/
sigtarobj.
File "/usr/lib/
assert not self.fileobj.
File "/usr/lib/
self.
File "/var/lib/
raise IOError, "GnuPG exited non-zero, with code %d" % (e << 8)
IOError: GnuPG exited non-zero, with code 131072
Regardless of the underlying error, the raise statement in python-
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: python-
PackageArchitec
ProcEnviron:
PATH=(custom, user)
LANG=en_AU.UTF-8
SHELL=/bin/zsh
SourcePackage: gnupginterface
Uname: Linux 2.6.28-8-generic x86_64
Related branches
Changed in gnupginterface (Debian): | |
status: | Unknown → New |
Changed in gnupginterface (Debian): | |
status: | New → Fix Released |
This bug is reported and a patch supplied in Debian Bug report logs - #509415 bugs.debian. org/cgi- bin/bugreport. cgi?bug= 509415
http://
Duplicity backup depends on this module as well. When the correct shift is made, the error is 2, File Not Found, and refers to the non-existence of the ~/.gnupg directory and its necessary files. The workaround for this problem is to run gpg from the command line and let it create the files it needs, then GnuPGInterface will work correctly.