Starting a new backup results with a AttributeError: 'NoneType' object has no attribute 'name' error ...

Bug #368456 reported by Jean-Philippe LECHÊNE
This bug report is a duplicate of:  Bug #368062: Unable to make a backup.. Edit Remove
2
Affects Status Importance Assigned to Milestone
Déjà Dup
New
Undecided
Unassigned

Bug Description

Dejadup version: 9.1
Duplicity version: 0.5.16
OS: Jaunty 9.04 i386
Type of backup: on an external (ext4 formatted) usb drive.

Hello,

I've rectenly installed a fresh Jaunty OS on my laptop. I used to use dejadup to make my everyday backup.
It ran find until last week or so.
Then it started to systematically show an error as soon as it tries to make new backup.

Please find below the end of the debugging file produced with DEJA_DUP_DEBUG=1 deja-dup launched with a new backup.

Feel free to ask if you need more information to track down this issue or to point me to the right direction if I've done something incorrect.

Thanks in advance for your help !

...
DUPLICITY: INFO 1
DUPLICITY: . Main action: collection-status

DUPLICITY: INFO 1
DUPLICITY: . /usr/bin/python 2.6.2 (release26-maint, Apr 19 2009, 01:56:41)
DUPLICITY: . [GCC 4.3.3]

DUPLICITY: INFO 1
DUPLICITY: . duplicity 0.5.16 (April 21, 2009)

DUPLICITY: INFO 1
DUPLICITY: . Linux jean-philippe-laptop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686

DUPLICITY: DEBUG 1
DUPLICITY: . 0 files exist on backend

DUPLICITY: DEBUG 1
DUPLICITY: . Extracting backup chains from list of files: []

DUPLICITY: INFO 3
DUPLICITY: backend LocalBackend
DUPLICITY: archive-dir None
DUPLICITY: orphaned-sets-num 0
DUPLICITY: incomplete-sets-num 0
DUPLICITY: . Collection Status
DUPLICITY: . -----------------
DUPLICITY: . Connecting with backend: LocalBackend
DUPLICITY: . Archive dir: None
DUPLICITY: .
DUPLICITY: . Found 0 backup chains without signatures.
DUPLICITY: . No backup chains with active signatures found
DUPLICITY: . No orphaned or incomplete backup sets found.

DUPLICITY: NOTICE 1
DUPLICITY: . Last full backup date: none

DUPLICITY: INFO 1
DUPLICITY: . Using temporary directory /tmp/duplicity-f0xw9R-tempdir

DUPLICITY: DEBUG 1
DUPLICITY: . Registering (mktemp) temporary file /tmp/duplicity-f0xw9R-tempdir/mktemp-T6hQxa-1

DUPLICITY: DEBUG 1
DUPLICITY: . Removing still remembered temporary file /tmp/duplicity-f0xw9R-tempdir/mktemp-T6hQxa-1

DUPLICITY: ERROR 30 AttributeError
DUPLICITY: . Traceback (most recent call last):
DUPLICITY: . File "/usr/bin/duplicity", line 828, in <module>
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/duplicity", line 821, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/duplicity", line 795, in main
DUPLICITY: . full_backup(col_stats)
DUPLICITY: . File "/usr/bin/duplicity", line 336, in full_backup
DUPLICITY: . bytes_written = write_multivol("full", tarblock_iter, globals.backend)
DUPLICITY: . File "/usr/bin/duplicity", line 205, in write_multivol
DUPLICITY: . mf = manifest.Manifest().set_dirinfo()
DUPLICITY: . File "/usr/lib/python2.6/dist-packages/duplicity/manifest.py", line 54, in set_dirinfo
DUPLICITY: . self.local_dirname = globals.local_path.name
DUPLICITY: . AttributeError: 'NoneType' object has no attribute 'name'
DUPLICITY: .

** (deja-dup:13087): DEBUG: DuplicityInstance.vala:429: duplicity (13093) exited with value 30

Revision history for this message
Jean-Philippe LECHÊNE (jphlechene) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.