Ubuntu
rdiff-backup package

[apport] rdiff-backup crashed with AttributeError in isinccompressed()

Bug #110471 reported by SergeyS on 2007-04-27

This bug report is a duplicate of: Bug #96258: [apport] rdiff-backup crashed with AttributeError in isinccompressed(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	rdiff-backup (Ubuntu)	Confirmed	Undecided	Andrew Ash

Bug Description

Binary package hint: rdiff-backup

Crashed at startup

ProblemType: Crash
Architecture: i386
Date: Fri Apr 27 10:32:13 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/rdiff-backup
InterpreterPath: /usr/bin/python2.5
Package: rdiff-backup 1.1.5-3build1
PackageArchitecture: i386
ProcCmdline: /usr/bin/python /usr/bin/rdiff-backup --exclude-special-files /home/sergey/.gnupg /home/sergey/Desktop/Important/backup/gnupg-settings
ProcCwd: /home/sergey
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
LANG=ru_RU.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/rdiff-backup', '--exclude-special-files', '/home/sergey/.gnupg', '/home/sergey/Desktop/Important/backup/gnupg-settings']
SourcePackage: rdiff-backup
Uname: Linux kubsergeys 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Revision history for this message

SergeyS (ssedreev) wrote on 2007-04-27:

Dependencies.txt Edit (885 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (7.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (709 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (1.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Andrew Ash (ash211) wrote on 2007-05-04:

Thanks for your bug report. Please try to obtain a backtrace <http://wiki.ubuntu.com/DebuggingProgramCrash> and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in rdiff-backup:
assignee:	nobody → ash211
status:	Unconfirmed → Needs Info

Revision history for this message

Richard Birnie (rbirnie-deactivatedaccount) wrote on 2007-05-06:

SergeyS,

Looking at the traceback from your error this seems to be a known issue that is being tracked as bug 96258. You can follow the discussion there. I noticed you have two other bug reports that are identical to this one. If you have filed the bug once there is no need to make a new report every time it occurs. I will mark all 3 as duplicates of bug 96258.