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

Bug #1284436 reported by Paul Oppenheim
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Crash on login

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 x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Feb 24 16:31:07 2014
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationDate: Installed on 2014-02-17 (7 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140121.1)
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: 0x7f15e4a28838 <main_arena+216>: sub %cl,0x7f15e4a2(%rax)
 PC (0x7f15e4a28838) in non-executable VMA region: 0x7f15e4a28000-0x7f15e4a2a000 rw-p /lib/x86_64-linux-gnu/libc-2.18.so
 source "%cl" ok
 destination "0x7f15e4a2(%rax)" (0x7f1663b86cda) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason:
 executing writable VMA /lib/x86_64-linux-gnu/libc-2.18.so
 writing unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 main_arena () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-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
Paul Oppenheim (pauloppenheim) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 main_arena () from /tmp/apport_sandbox_FQDCq3/lib/x86_64-linux-gnu/libc.so.6
 dconf_gdbus_method_call_done (source=<optimized out>, result=0x7f15cc008d00, user_data=0x22a7e90) at dconf-gdbus-thread.c:231
 g_simple_async_result_complete (simple=0x7f15cc008d00) at /build/buildd/glib2.0-2.39.90/./gio/gsimpleasyncresult.c:763
 g_dbus_connection_call_done (source=<optimized out>, result=<optimized out>, user_data=0x7f15cc009e30) at /build/buildd/glib2.0-2.39.90/./gio/gdbusconnection.c:5498
 g_simple_async_result_complete (simple=0x7f15cc008e50) at /build/buildd/glib2.0-2.39.90/./gio/gsimpleasyncresult.c:763

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-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.