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

Bug #960309 reported by Jani Uusitalo
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glib2.0 (Ubuntu)
New
Medium
Unassigned

Bug Description

Happened just now as I was reporting another bug. May or may not have been associated with my Internet connection temporarily going offline for some reason at about the same time. No other conspicuous associated details I have right now but will happily provide if more data is needed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: deja-dup 21.90-0ubuntu1
Uname: Linux 3.3.0-030300rc4-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CheckboxSubmission: 09ae689090491ca53449589269e4bfd8
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Tue Mar 20 17:15:46 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
SegvAnalysis:
 Segfault happened at: 0x7f6c0c59085a <g_settings_backend_dispatch_signal+234>: mov (%rax,%rbx,1),%rax
 PC (0x7f6c0c59085a) ok
 source "(%rax,%rbx,1)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: deja-dup
StacktraceTop:
 g_settings_backend_dispatch_signal (backend=0x6d1010, function_offset=8, name=0x9e9510 "/org/gnome/deja-dup/", data1=0x0, data1_copy=0x7f6c0c590340 <pointer_id>, data1_free=0x7f6c0c590350 <pointer_ignore>, data2=0x0) at /build/buildd/glib2.0-2.31.20/./gio/gsettingsbackend.c:340
 g_settings_backend_path_changed (backend=0x6d1010, path=0x9e9510 "/org/gnome/deja-dup/", origin_tag=0x0) at /build/buildd/glib2.0-2.31.20/./gio/gsettingsbackend.c:496
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 g_simple_async_result_complete (simple=0xc30670) at /build/buildd/glib2.0-2.31.20/./gio/gsimpleasyncresult.c:767
 g_dbus_connection_call_done (source=0x7f6c04008830, result=<optimized out>, user_data=0x7f6c04120090) at /build/buildd/glib2.0-2.31.20/./gio/gdbusconnection.c:5303
Title: deja-dup-monitor crashed with SIGSEGV in g_settings_backend_dispatch_signal()
UpgradeStatus: Upgraded to precise on 2012-03-20 (0 days ago)
UserGroups: adm admin cdrom dialout disk fuse lpadmin plugdev pulse pulse-access sambashare ssh vboxusers video

Revision history for this message
Jani Uusitalo (uusijani) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_settings_backend_dispatch_signal (backend=0x6d1010, function_offset=8, name=0x9e9510 "/org/gnome/deja-dup/", data1=0x0, data1_copy=0x7f6c0c590340 <g_null_settings_backend_get_type+80>, data1_free=0x7f6c0c590350 <g_null_settings_backend_get_type+96>, data2=0x0) at /build/buildd/glib2.0-2.31.22/./gio/gsettingsbackend.c:328
 g_settings_backend_path_changed (backend=<optimized out>, path=0x9e9510 "/org/gnome/deja-dup/", origin_tag=0x0) at /build/buildd/glib2.0-2.31.22/./gio/gsettingsbackend.c:493
 add_match_done (source=0x7f6c04008830, result=0x9e9510, user_data=0x9eca00) at dconfsettingsbackend.c:598
 g_simple_async_result_complete (simple=<optimized out>) at /build/buildd/glib2.0-2.31.22/./gio/gsimpleasyncresult.c:772
 g_dbus_connection_call_done (source=0x7f6c04008830, result=0xc30670, user_data=0x7f6c04120090) at /build/buildd/glib2.0-2.31.22/./gio/gdbusconnection.c:5258

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

This seems to be in the bowels of glib2.0, moving to that package.

affects: deja-dup (Ubuntu) → glib2.0 (Ubuntu)
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.