duplicity crashed with SIGSEGV in g_file_copy()

Bug #1436958 reported by Dave Morley
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
duplicity (Ubuntu)
New
Medium
Unassigned

Bug Description

mterry just for you:

Here is the upload from the crash that takes out my desktop on restoring from ssh

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: duplicity 0.7.01-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 26 17:13:58 2015
ExecutablePath: /usr/bin/duplicity
InstallationDate: Installed on 2015-03-26 (0 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/duplicity restore --gio --time=2015-03-26T09:13:09Z --force sftp://<email address hidden>/home/username/deja-dup / --verbosity=9 --gpg-options=--no-use-agent --archive-dir=/home/username/.cache/deja-dup --tempdir=/tmp --log-fd=20
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc67c432492 <g_file_copy+546>: mov (%rax),%eax
 PC (0x7fc67c432492) 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
 ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
 ?? () from /usr/lib/python2.7/dist-packages/gi/_gi.so
Title: duplicity crashed with SIGSEGV in g_file_copy()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Dave Morley (davmor2) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_file_copy (source=0x7fc674009f20, destination=0x21389a0, flags=(G_FILE_COPY_ALL_METADATA | G_FILE_COPY_TARGET_DEFAULT_PERMS | unknown: 2738445248), cancellable=0x0, progress_callback=0x22493e0, progress_callback_data=0x0, error=0x7fffa3395f20) at /build/buildd/glib2.0-2.43.92/./gio/gfile.c:3383
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=<optimized out>, fn=<optimized out>, rvalue=0x7fffa3395e70, avalue=0x20b0d00) at ../src/x86/ffi64.c:525
 pygi_invoke_c_callable (function_cache=0x21ed870, state=0x7fffa3395ee0, py_args=0x7fffa3395be8, py_kwargs=0x7fc67c43244b <g_file_copy+475>) at ../../gi/pygi-invoke.c:628
 pygi_function_cache_invoke (function_cache=<optimized out>, py_args=py_args@entry=0x7fc67df39460, py_kwargs=py_kwargs@entry=0x0) at ../../gi/pygi-cache.c:793

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):
importance: Undecided → Medium
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.