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

Bug #554280 reported by Nicolás Lichtmaier
226
This bug affects 45 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

I haven't done anything wrong! Not my fault! =)

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-settings-daemon 2.30.0-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Apr 2 18:28:48 2010
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon --gconf-prefix=/apps/gdm/simple-greeter/settings-manager-plugins
ProcEnviron:
 LANG=es_AR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/false
 LANGUAGE=es_AR:es
SegvAnalysis:
 Segfault happened at: 0x7fb218c49260 <g_str_hash>: movsbl (%rdi),%eax
 PC (0x7fb218c49260) ok
 source "(%rdi)" (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:
 g_str_hash () from /lib/libglib-2.0.so.0
 g_hash_table_lookup () from /lib/libglib-2.0.so.0
 theme_dir_get_icon_suffix (
 theme_lookup_icon (
 choose_icon (icon_theme=<value optimized out>,
Title: gnome-settings-daemon crashed with SIGSEGV in g_str_hash()
UserGroups:

Revision history for this message
Nicolás Lichtmaier (niqueco) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_str_hash () from /lib/libglib-2.0.so.0
 g_hash_table_lookup () from /lib/libglib-2.0.so.0
 theme_dir_get_icon_suffix (
 choose_icon (icon_theme=<value optimized out>,
 ensure_pixbuf_for_gicon (image=0xe0f8b0)

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
tags: removed: need-amd64-retrace
Revision history for this message
Antono Vasiljev (antono) wrote :

Crashes right after login

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
Antono Vasiljev (antono)
tags: added: i386
Antono Vasiljev (antono)
tags: added: natty
Revision history for this message
Carsten (carsten-tschense) wrote :

Same with maverick.

Revision history for this message
ike (ikeahloe) wrote :

definitely an annoying problem in natty, not sure what extra information i can provide/devs need

Revision history for this message
Lord_Phoenix (lord-phoenix-rus) wrote :

Disableing UbuntuOne client from Startup solves the issue. Reverting to previous UbuntuOne client version also solves issue

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gnome-settings-daemon (Ubuntu):
importance: Medium → Low
status: Confirmed → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

the crash there should be fixed in natty, comment #8 seems a different bug and should be opened against ubuntuoneclient-gnome

Revision history for this message
David Ayers (ayers) wrote :

If this bug has already been reported is there a different report that this one should be marked duplicate of?
I'd like to subscribe to the real report to track the fix for maverick and to update my landscape support case to point the actual report.

Thanks!

Revision history for this message
Sebastien Bacher (seb128) wrote :

it has likely been fixed in that upload

libappindicator (0.3.0-0ubuntu1) natty; urgency=low

  * New upstream release.
    * Don't use GIcon with GtkStatusIcon (LP: #708118) (LP: #729150)

though several crashers got fixed in natty which leaded to different stacktrace so it's not trivial to match one crash to the fix which adressed it

Revision history for this message
Sebastien Bacher (seb128) wrote :

there was bug #708188 as well

Revision history for this message
David Ayers (ayers) wrote :

Thanks for the pointers. Yet I can confirm that installing:
sudo aptitude install libappindicator1/maverick-proposed python-appindicator/maverick-proposed
(and rebooting)
does /not/ solve the issue:
ayers@schiefer:~$ apt-cache policy libappindicator1
libappindicator1:
  Installiert: 0.2.9-0ubuntu1.1
  Kandidat: 0.2.9-0ubuntu1.1
  Versionstabelle:
 *** 0.2.9-0ubuntu1.1 0
        400 http://at.archive.ubuntu.com/ubuntu/ maverick-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     0.2.9-0ubuntu1 0
        500 http://at.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages

and since bug #708188 also point to libappindicator and this is actually associated with gnome-session-daemon, I hope you don't mind me changing the status to confirmed.

I'd rather not give feedback to the libappinidicator reports since those are not the crashes I'm seeing. My crash is 100% reproducible and always effects gnome-settings-daemon.

Of course I'd be happy to test other packages if there is reason to believe that are related.

Changed in gnome-settings-daemon (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

David is your bug one of the duplicate? it would help having a new crash description, note that the issue is not supposed to be fixed in 10.10 with the current updates, what desktop environment do you use?

Changed in gnome-settings-daemon (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
David Ayers (ayers) wrote :

Hello Sebastien, I was subscribed to this bug after ubuntu-bug (or apport?) pointed me to this issue due to my crash report in:
/var/crash/_usr_lib_gnome-settings-daemon_gnome-settings-daemon.1000.crash

Yes, I'm using 10.10 (maverick) and I'm using default GNOME with the default Ambient them yet smaller fonts than the default. Note that the original report was for 10.4 LTS (lucid), so a fix in natty probably won't help most affected people.

Please let me know if I should open new report.

Revision history for this message
Sebastien Bacher (seb128) wrote :

so it's happening at any login for you? opening a new bug from a recent .crash with the .xsession-errors from the cycle would be useful, the other issues were mostly happening when indicator-applet is not configured which seems to not be your case if you use the standard configuration, they also don't happen at login so it could be a different bug

Revision history for this message
Tr4sK (tr4sk) wrote :

Disabled Ubuntu one service solve the problem for me.

Revision history for this message
David Ayers (ayers) wrote :

Yes, this happens on every login.

OK, I have opened bug #746566 (I haven't set it to public yet since I'm not sure what all I should delete before doing so). Also if you have access to landscape cases, you can find a similar crash report in case #00016589 and I suppose you should have access to all the configuration of the system via landscape. If not let me know what you need.

Thanks!

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks David for opening a new bug, your issue is an ubuntuone crash, the trigger seems to be your account being over quota there

Revision history for this message
Ingo Gerth (igerth) wrote :

It has not been noted here yet I think, but when this bug occurs my theme is set to a Windows 95-ish Gnome standard theme, including the icons. Thus for me it is bye-bye Ambiance right now.

Revision history for this message
David Ayers (ayers) wrote :

Hello Ingo, if you open System->Settings->Appearance then you ambiance theme will be restored for most applications (notable exception is Nautilus). ... at least until the next ubuntuone sync that trips your quota occurs.

Revision history for this message
David Ayers (ayers) wrote :

I have extended my Ubuntuone subscription by 20 GB but the crash still happens. So this seems unrelated to tripping the quota.

Revision history for this message
Ingo Gerth (igerth) wrote :

Interesting! Thanks for letting me know of the workaround. Indeed I have reached the 2/2GB limit of my Ubuntu One account.

I would like to ask how this bug can only have such a low priority. This particular one has been around for a year now and nobody is assigned to it, although it completely breaks the end-user experience.

Revision history for this message
David Ayers (ayers) wrote :

Hello Ingo,

I think the issue is that this particular bug is about theming:

StacktraceTop:
 g_str_hash () from /lib/libglib-2.0.so.0
 g_hash_table_lookup () from /lib/libglib-2.0.so.0
 theme_dir_get_icon_suffix (
 choose_icon (icon_theme=<value optimized out>,
 ensure_pixbuf_for_gicon (image=0xe0f8b0)

but our bug about Ubuntuone... it's just that apport is not smart enough to tell the difference. Please have a look at bug #744383 which has the trace that I have:

StacktraceTop:
 g_str_hash (v=0x0) at /build/buildd/glib2.0-2.26.1/glib/gstring.c:134
 g_hash_table_lookup (hash_table=0x95a44c0, key=0x0)
 quota_exceeded_callback (daemon=0x95bb7b0,
 g_cclosure_marshal_VOID__POINTER (closure=0x967beb8,
 g_closure_invoke (closure=0x967beb8, return_value=0x0,

And that bug indeed has a high priority and is actively being worked on.

So think we were just lead to the wrong old report that has similar symptoms.

Revision history for this message
chiefbutz (chiefbutz) wrote :

Here is my error report

Revision history for this message
Sebastien Bacher (seb128) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-settings-daemon (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-settings-daemon (Ubuntu):
status: Incomplete → Expired
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.