duplicity crashed with SIGSEGV in g_file_copy()

Bug #1156766 reported by Till Kamppeter
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
duplicity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: duplicity 0.6.21-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-13.22+tja1-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Mon Mar 18 19:43:50 2013
ExecutablePath: /usr/bin/duplicity
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
ProcCmdline: /usr/bin/python /usr/bin/duplicity --include=/home/username/.cache/deja-dup/metadata --exclude=/home/username/photos --exclude=/home/username/Downloads --exclude=/home/username/.local/share/Trash --exclude=/home/username/.cache/deja-dup/tmp --exclude=/home/username/.xsession-errors --exclude=/home/username/.thumbnails --exclude=/home/username/.Private --exclude=/home/username/.gvfs --exclude=/home/username/.adobe/Flash_Player/AssetCache --exclude=/home/username/.cache/deja-dup --exclude=/home/username/.cache --include=/home/username --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp --exclude=/tmp --exclude=** --gio --volsize=25 / ftp://anonymous@lacie-2big/Public/backup --no-encryption --verbosity=9 --gpg-options=--no-use-agent --archive-dir=/home/username/.cache/deja-dup --tempdir=/home/username/.cache/deja-dup/tmp --log-fd=21
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa73a974b95 <g_file_copy+389>: mov (%rax),%eax
 PC (0x7fa73a974b95) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: duplicity
StacktraceTop:
 g_file_copy () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_callable_info_invoke () from /usr/lib/libgirepository-1.0.so.1
 g_function_info_invoke () from /usr/lib/libgirepository-1.0.so.1
Title: duplicity crashed with SIGSEGV in g_file_copy()
UpgradeStatus: Upgraded to raring on 2012-10-19 (150 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in duplicity (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for duplicity: package version 0.6.21-0ubuntu1 dbgsym version 0.6.19-0ubuntu2.2
libpython2.7-stdlib version 2.7.3-16ubuntu2 required, but 2.7.3-16ubuntu1 is available
libpython2.7-minimal version 2.7.3-16ubuntu2 required, but 2.7.3-16ubuntu1 is available
python2.7-minimal version 2.7.3-16ubuntu2 required, but 2.7.3-16ubuntu1 is available
python2.7 version 2.7.3-16ubuntu2 required, but 2.7.3-16ubuntu1 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
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.