gnome-settings-daemon crashed with SIGSEGV in main_arena()

Bug #1286334 reported by Erick Brunzell
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Medium
Unassigned

Bug Description

I got this automated bug report while logging into gnome-flashback w/metacity for the first time in Ubuntu GNOME Trusty.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-settings-daemon 3.8.6.1-0ubuntu9
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic i686
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
CrashCounter: 1
CurrentDesktop: GNOME
Date: Fri Feb 28 14:33:52 2014
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationDate: Installed on 2014-02-26 (2 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha i386 (20140226)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0xb6ef3468 <main_arena+72>: pusha
 PC (0xb6ef3468) in non-executable VMA region: 0xb6ef3000-0xb6ef4000 rw-p /lib/i386-linux-gnu/libc-2.19.so
 Stack memory exhausted (SP below stack segment)
SegvReason: executing writable VMA /lib/i386-linux-gnu/libc-2.19.so
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 main_arena () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so
 ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so
 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in main_arena()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Erick Brunzell (lbsolost) wrote :
information type: Private → Public
Revision history for this message
Erick Brunzell (lbsolost) wrote :

Subsequent boots do not produce this error, so it's just a one time thing upon logging into flashback w/metacity for the first time. Therefore I think it should be considered a very low priority bug.

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

StacktraceTop:
 main_arena () from /tmp/apport_sandbox_0LTnDp/lib/i386-linux-gnu/libc.so.6
 dconf_engine_call_handle_reply (handle=handle@entry=0x97dda48, parameter=0x978e0a8, error=0x0) at dconf-engine.c:724
 dconf_gdbus_method_call_done (source=0xb5904590, result=0x969ad30, user_data=0x97dda48) at dconf-gdbus-thread.c:231
 g_simple_async_result_complete (simple=0x969ad30) at /build/buildd/glib2.0-2.39.90/./gio/gsimpleasyncresult.c:763
 g_dbus_connection_call_done (source=0xb5904590, result=0x970aea8, user_data=0xb59020a8) at /build/buildd/glib2.0-2.39.90/./gio/gdbusconnection.c:5498

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 gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-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.