deja-dup-monitor crashed with SIGSEGV in g_variant_unref()

Bug #829643 reported by Matthew Paul Thomas
50
This bug affects 10 people
Affects Status Importance Assigned to Milestone
deja-dup (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Apport says:

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: deja-dup 19.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Wed Aug 17 14:25:06 2011
ExecutablePath: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64+mac (20110705.1)
ProcCmdline: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb888d834e9 <g_variant_unref+9>: lock xadd %eax,0x24(%rdi)
 PC (0x7fb888d834e9) ok
 source "%eax" ok
 destination "0x24(%rdi)" (0x00000024) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: deja-dup
StacktraceTop:
 g_variant_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_settings_get_string () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: deja-dup-monitor crashed with SIGSEGV in g_variant_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Matthew Paul Thomas (mpt) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_variant_unref (value=0x0) at /build/buildd/glib2.0-2.29.16/./glib/gvariant-core.c:617
 g_settings_get_string (settings=<optimized out>, key=<optimized out>) at /build/buildd/glib2.0-2.29.16/./gio/gsettings.c:1770
 deja_dup_update_last_run_timestamp (type=DEJA_DUP_TIMESTAMP_TYPE_NONE) at CommonUtils.c:243
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.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
visibility: private → public
Revision history for this message
Michael Terry (mterry) wrote :

Hrm. This stack trace is impossible. Memory must have gotten corrupted before it crashed...

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

Is this reproducable? I can't do much without being able to hit it myself.

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