gnome-settings-daemon crashed with SIGSEGV

[Milan Bouchet-Valat]

Binary package hint: gnome-settings-daemon

No clue about what happened, hope this is useful and the trace will be good.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-settings-daemon 2.29.92-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic i686
Architecture: i386
Date: Tue Mar 30 17:46:55 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_GB:en
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x5c100b: movsbl (%edx),%eax
 PC (0x005c100b) ok
 source "(%edx)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape video

[Apport retracing service (apport)]

StacktraceTop:
 find_image_offset (cache=<value optimized out>,
 _gtk_icon_cache_get_icon_flags (cache=0x8848fe8,
 theme_dir_get_icon_suffix (dir=<value optimized out>,
 choose_icon (icon_theme=<value optimized out>,
 ensure_pixbuf_for_gicon (image=0x87dd860)

[Milan Bouchet-Valat (nalimilan)]

Looks like the icon name is not filled correctly:
theme_dir_get_icon_suffix (dir=<value optimized out>, icon_name=0x1 <Address 0x1 out of bounds>, has_icon_file=0x0)

[Milan Bouchet-Valat (nalimilan)]

I've been able to reproduce the same crash after/while upgrading. So I confirm my own bug (bad, bad!).

[miked (miked11)]

Lucid Lynx Beta 1 10.04 ix386.iso

[chris_blues (chris.blues)]

Same here on a fresh Lucid-Install. Also gconfd-2+xorg runs with 60% CPU-usage all the time (on a 2x2,6GHz-machine!!!). Maybe this is related?

[yurx cherio (cherio)]

Also happens when connecting to Lucid via NX Server (neatx).

[CPKS (c-1)]

Happened just after upgrade.

[Erik B. Andersen (azendale)]

I can confirm that this bug happened to me on amd64.

[Milan Bouchet-Valat (nalimilan)]

Thanks, but we don't need confirmation from every person experiencing this bug. You can just mark yourself as affected at the top of the page, and subscribe to the report.

[Pedro Villavicencio (pedro)]

upstream report was reassigned to gtk+, doing the same with this one.

[Milan Bouchet-Valat (nalimilan)]

A few reports against gnome-power-manager show the very same backtrace, which confirms the bug is in libappindicator using GtkStatusIcon (whichever the culprit), not in gnome-settings-daemon. See bug 63334, and upstream report for "explanations".

[Joost Ringoot (joost)]

after using update manager and (as required by update manager) rebooting I got this when I tried to install the remaining update: GRUB

[Rodrigo Tobar (rtobarc)]

Just to support Milan's comment, I'm attaching a stacktrace of gnome-power-manager crashing for the same reason, on maverick, i386

[Milan Bouchet-Valat (nalimilan)]

Installing today's upgrades, I reproduced the crash of gnome-power-manager again. I'm attaching the relevant part of /var/log/dpkg.log, in the hope we'll be able to find what's the kind of package that causes the crash. So, if you trigger the bug after running upgrades, please also attach your /var/log/dpkg.log for the current day, thanks!

In the packages I upgraded, there are notably:
- X.org, mesa, libdrm and Co. from xorg-edgers PPA
- cairo and pixman
- python
- gnome-exe-thumbnailer
- shotwell
- software-center
- desktopcouch and ubuntuone-client

[mperry (mpmilestogo)]

I have not seen this bug through about 2 updates now. The issue was
occurring almost daily until the last round of updates. Now I have not seen
a gnome-power-manager crash in 3 days. If I catch one, I'll reply with the
log.

On Thu, Sep 30, 2010 at 2:47 PM, Milan Bouchet-Valat <email address hidden>wrote:

> Installing today's upgrades, I reproduced the crash of gnome-power-
> manager again. I'm attaching the relevant part of /var/log/dpkg.log, in
> the hope we'll be able to find what's the kind of package that causes
> the crash. So, if you trigger the bug after running upgrades, please
> also attach your /var/log/dpkg.log for the current day, thanks!
>
> In the packages I upgraded, there are notably:
> - X.org, mesa, libdrm and Co. from xorg-edgers PPA
> - cairo and pixman
> - python
> - gnome-exe-thumbnailer
> - shotwell
> - software-center
> - desktopcouch and ubuntuone-client
>
> ** Attachment added: "Upgrade triggering the crash"
>
> https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/551809/+attachment/1659848/+files/upgrades
>
> --
> gnome-settings-daemon crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/551809
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (641681).
>
> Status in GTK+ GUI Toolkit: New
> Status in “gtk+2.0” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: gnome-settings-daemon
>
> No clue about what happened, hope this is useful and the trace will be
> good.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 10.04
> Package: gnome-settings-daemon 2.29.92-0ubuntu4
> ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
> Uname: Linux 2.6.32-18-generic i686
> Architecture: i386
> Date: Tue Mar 30 17:46:55 2010
> EcryptfsInUse: Yes
> ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
> ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
> ProcEnviron:
> LANGUAGE=fr_FR:fr:en_GB:en
> LANG=fr_FR.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x5c100b: movsbl (%edx),%eax
> PC (0x005c100b) ok
> source "(%edx)" (0x00000001) not located in a known VMA region (needed
> readable region)!
> destination "%eax" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: gnome-settings-daemon
> StacktraceTop:
> ?? () from /usr/lib/libgtk-x11-2.0.so.0
> ?? () from /usr/lib/libgtk-x11-2.0.so.0
> ?? () from /usr/lib/libgtk-x11-2.0.so.0
> ?? () from /usr/lib/libgtk-x11-2.0.so.0
> ?? () from /usr/lib/libgtk-x11-2.0.so.0
> Title: gnome-settings-daemon crashed with SIGSEGV
> UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin
> netdev plugdev sambashare scanner tape video
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gtk/+bug/551809/+subscribe
>

[Sitsofe Wheeler (sitsofe)]

This just happened to me with an updated Ubuntu Lucid when I was updating packages including a PPA for Xorg while on battery. Rather strangely at one point I had two battery indicators in gnome-panel/indicator-applet (with one smaller than the other) even though I have only one battery but after the crash only one remained....

[jhansonxi (jhansonxi)]

@Sitsofe Wheeler: The duplicate indicators may be bug #439448.

[Rod Boyle (1...rod)]

This is happening to me on !0.10 Maverick, I was simply changing some settings for Swift Switcher plug-in in ConpizConfig settings manager when the error occurred.