[power]: gnome-settings-daemon crashed with SIGSEGV in magazine_chain_pop_head()

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

Bug Description

About an hour after logging in, gnome-settings-daemon crashes. Other than files that are thumbnailed, all of my GTK/Gnome icons revert to a "plain sheet" icon. This can be reproduced by logging off/on, and waiting for about an hour.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 17 11:12:43 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f73577a1dfa <g_slice_alloc+490>: mov (%rbx),%rdx
 PC (0x7f73577a1dfa) ok
 source "(%rbx)" (0x6168632d6c6c7566) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slist_prepend () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strsplit () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gpm_upower_get_device_icon () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so
Title: [power]: gnome-settings-daemon crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: Upgraded to precise on 2012-03-08 (39 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare video

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

StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0x1a57110) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:532
 thread_memory_magazine1_alloc (ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:835
 g_slice_alloc (mem_size=16) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:994
 g_slist_prepend (list=0x1b66b40, data=0x1e400b0) at /build/buildd/glib2.0-2.32.1/./glib/gslist.c:265
 g_strsplit (string=0x1e406a0 "battery-full-charged-symbolic;battery-full-charging-symbolic;gpm-battery-full;gpm-battery-100;battery-full-charged;battery-full-charging;", delimiter=0x7f7349f28b24 ";", max_tokens=<optimized out>) at /build/buildd/glib2.0-2.32.1/./glib/gstrfuncs.c:2260

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 gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
summary: - [power]: gnome-settings-daemon crashed with SIGSEGV in g_slice_alloc()
+ [power]: gnome-settings-daemon crashed with SIGSEGV in
+ magazine_chain_pop_head()
tags: removed: need-amd64-retrace
Revision history for this message
Jeremy Melanson (jmelanson) wrote :

Captured debug output from gnome-settings-daemon at the point where my icons go haywire, and whoopsie reports that a problem occurred.

I renamed the gnome-settings-daemon binary to gnome-settings-daemon.bin, then put a shell script wrapper around it. Hence the reason that the log reports gnome-settings-daemon.bin. As such, that can be ignored.

visibility: private → public
Revision history for this message
Jeremy Melanson (jmelanson) wrote :

At one point, it appeared that I was able to get my icons back by killing gnome-settings-daemon. They would appear normal when it restarted. This does not currently seem to be the case.
My GTK style and fonts are ok, however.

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.