deja-dup crashed with SIGSEGV in __GI___pthread_mutex_lock()

Bug #1301609 reported by Andy Underhill
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
deja-dup (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Deja-dup has been causing me a lot of problems over the last few days - many instant reboots - no errors, no messages in syslog. This error came about after this evening's set of updates - so a step in the right direction.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: deja-dup 30.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
Uname: Linux 3.13.0-21-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 2 22:03:29 2014
ExecutablePath: /usr/bin/deja-dup
ProcCmdline: deja-dup --backup --auto
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ffec725a414 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7ffec725a414) ok
 source "0x10(%rdi)" (0xff60462fff5e443d) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: deja-dup
StacktraceTop:
 __GI___pthread_mutex_lock (mutex=0x12a8560) at ../nptl/pthread_mutex_lock.c:66
 g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_signal_handlers_destroy () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: deja-dup crashed with SIGSEGV in __GI___pthread_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare sudo

Revision history for this message
Andy Underhill (andy-jjcftv6wldnzq84cskyg) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI___pthread_mutex_lock (mutex=0x12a8560) at ../nptl/pthread_mutex_lock.c:66
 g_mutex_lock (mutex=mutex@entry=0x7ffec82e86a8 <g__g_signal_mutex_lock>) at /build/buildd/glib2.0-2.40.0/./glib/gthread-posix.c:209
 g_signal_handlers_destroy (instance=instance@entry=0x129fcf0) at /build/buildd/glib2.0-2.40.0/./gobject/gsignal.c:2621
 g_object_real_dispose (object=0x129fcf0) at /build/buildd/glib2.0-2.40.0/./gobject/gobject.c:1016
 g_object_unref (_object=0x129fcf0) at /build/buildd/glib2.0-2.40.0/./gobject/gobject.c:3075

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 deja-dup (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Andy Underhill (andy-jjcftv6wldnzq84cskyg) wrote :

Also happens with 3.14 mainline kernel. The backup had progressed a fair way possibly about 20% of 270GB.

Revision history for this message
Michael Terry (mterry) wrote :

Does you still experience this? I'm trying to clean up bugs and this is a bit old with no other reports.

information type: Private → Public
Changed in deja-dup (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for deja-dup (Ubuntu) because there has been no activity for 60 days.]

Changed in deja-dup (Ubuntu):
status: Incomplete → Expired
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.