gnome-settings-daemon crashed with SIGSEGV

Bug #551809 reported by Milan Bouchet-Valat on 2010-03-30
944
This bug affects 213 people
Affects Status Importance Assigned to Milestone
GTK+
New
Critical
gtk+2.0 (Ubuntu)
High
Canonical Desktop Team
Nominated for Lucid by Milan Bouchet-Valat
Maverick
High
Unassigned
Natty
High
Canonical Desktop Team

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

Milan Bouchet-Valat (nalimilan) wrote :
visibility: private → public

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)

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Milan Bouchet-Valat (nalimilan) wrote :

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) wrote :

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

Changed in gnome-settings-daemon (Ubuntu):
importance: Medium → High
status: New → Triaged
miked (miked11) wrote :

Lucid Lynx Beta 1 10.04 ix386.iso

chris_blues (chris.blues) wrote :

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) wrote :

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

CPKS (c-1) wrote :

Happened just after upgrade.

Erik B. Andersen (azendale) wrote :

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

tags: added: amd64

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.

Changed in gnome-settings-daemon:
status: Unknown → New
Changed in gnome-settings-daemon:
importance: Unknown → Critical
affects: gnome-settings-daemon → gtk
Pedro Villavicencio (pedro) wrote :

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

affects: gnome-settings-daemon (Ubuntu) → gtk+2.0 (Ubuntu)
Changed in gtk+2.0 (Ubuntu):
milestone: none → ubuntu-10.10

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) wrote :

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

Changed in gtk+2.0 (Ubuntu):
assignee: nobody → Ted Gould (ted)
Rodrigo Tobar (rtobarc) wrote :

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

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

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
>

Changed in gtk+2.0 (Ubuntu):
milestone: ubuntu-10.10 → maverick-updates
Sitsofe Wheeler (sitsofe) wrote :

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) wrote :

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

Rod Boyle (1...rod) wrote :

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.

Ted Gould (ted) on 2011-03-28
Changed in gtk+2.0 (Ubuntu):
assignee: Ted Gould (ted) → nobody
Changed in gtk+2.0 (Ubuntu Maverick):
milestone: none → maverick-updates
Changed in gtk+2.0 (Ubuntu):
milestone: maverick-updates → none
Changed in gtk+2.0 (Ubuntu Maverick):
status: New → Triaged
importance: Undecided → High
Changed in gtk+2.0 (Ubuntu Natty):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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