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

StacktraceTop:IA__g_datalist_id_set_data_full (datalist=0x81e1018, key_id=50, data=0x0, destroy_func=0)
g_object_real_dispose (object=0x81e1010)
gtk_object_dispose (gobject=0x81e1010) at /build/buildd/gtk+2.0-2.12.7/gtk/gtkobject.c:423
gtk_widget_dispose (object=0x81e1010) at /build/buildd/gtk+2.0-2.12.7/gtk/gtkwidget.c:7854
gtk_window_dispose (object=0x81e1010) at /build/buildd/gtk+2.0-2.12.7/gtk/gtkwindow.c:1968

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=514324

confirmed. 8.04 hardy 2.6.24-7 / gateway mt-3422
crash on startup

This is a Fujitsu A series A6020

fujitsu Lifebook A series A6020**

i got the same "gnome-settings-daemon crashed with SIGSEGV in g_datalist_id_set_data_full()" while playing a movie in totem and pressing the volume-down button to adjust the volume, the settings daemon crashed, and restarted. (the volume didn't go down as normal, so I held down the button)

Confirmed on ThinkPad T40. Pressing volume-down during login resulted in hanging volume notification (standard metacity popup). Crash report notification popped after which volume controls resumed normal operation with fancy transparent compiz volume notification popups.

I pressed Volume Down on my Sony Vaio VGN-AR250G during startup and saw this same crash.

Happened on amd64 also. I've attached the crash file (archived). Hope this helps. BTW I also pressed Volume Down (Vaio VGN-CR120E) while the startup sound was playing.

Upon reading this, I remembered that I was also pressing the volume-down button. This was on a Zepto 6625WD Intel 2,4 duo 64bit.
Good luck:)

Same here, crashed on startup. I remember that a had pressed the volume UP button before.

Same here, crashed on startup. Dell Inspiron E1405. Was pressing volume up on start-up.

Happened with a Macbook v.3.1 (Santa Rosa), too. (arch amd64)

i pressed the volume down button on my lenovo R60 and BOOM ..it crashed!

i did nothing :-( on a maxdata pc with 2,8 MHz Intel Pentium 4 HT CPU, old nvidia graphic-card with two screens (one not supported)

I think I was using the volume shortcuts while rhythmbox was playing, too.

Hey, I figured out a reliable way to reproduce the bug and make it crash! :)

I don't know if this works with compiz (most likely), but I did this using composite metacity. The trick is to enable/disable the composite manager in metacity, and then press the volume keys. When it is uncrashed, you can reactivate (or deactivate) the composite option (depending on what you did first) and make it crash again by hitting the volume keys.

Rinse, repeat.

I confirm that when i press the volume keys with compiz and hardy alpha 6
the bug is reproduced.
regards
guna

On Fri, Mar 7, 2008 at 8:16 PM, Jean-François Fortin Tam <email address hidden>
wrote:

> Hey, I figured out a reliable way to reproduce the bug and make it
> crash! :)
>
> I don't know if this works with compiz (most likely), but I did this
> using composite metacity. The trick is to enable/disable the composite
> manager in metacity, and then press the volume keys. When it is
> uncrashed, you can reactivate (or deactivate) the composite option
> (depending on what you did first) and make it crash again by hitting the
> volume keys.
>
> Rinse, repeat.
>
> --
> gnome-settings-daemon crashed with SIGSEGV in
> g_datalist_id_set_data_full()
> https://bugs.launchpad.net/bugs/188562
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
C.R.Gunasekar
21, Padmavati Nagar, Station Road
Agraharam, KORATTUR
Chennai - India- 600076
Ph (+91) 44 26512584 Mob: (+91) 9444409954

I confirm that when starting up and pressing the volume DOWN key on my HP nx7400 laptop with intel core 2 duo (T7200) i reproduced this bug.

regards,
Matthias

I tried to toggle the volume with the Laptop's (LG XNote LM50a) volume key, but nothing happened. I then tried by using the volume-applet, and while decreasing the volume, it looked like my theme changed from human to default (then back again). After that, it threw the error.

I remember that I also muted audio but manually using the volume applet in panel because I really hate, that computer always (few times after update) shouts when started. Yes, I also have a laptop (Dell Inspiron 8500). Still crashed on startup.

I also was playing with the keyboard audio keys when it crashed, I muted the audio during the logon sound using the keyboard function keys

everything was working correctly, fresh boot, copied some files around, watching a video... volume keys working...

this was with compiz...

then I noticed the vertical sync was out causing tearing on the video so, annoyed, I stopped the video, went to Appearance prefs and disabled visual effects... metacity started...

then went back to the movie... pressed the volume key... waited a few seconds, then the crash dialog came up.

so:

1. start up computer normally with compiz enabled
2. keys working ok
3. disable compiz (which enabled metacity)
4. start up movie player
5. try to adjust volume
6. gnome-settings-manager CRASH

gnome-settings-daemon sorry

Live CD - multimedia keyboard.

As logon music played I turned knob to lower volume and this didn't work. It immediately crashed.

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Well I've been using hardy release for a while now and have not seen this, so it may be fixed.

I can confirm that this is not fixed.

gnome-settings-daemon crashed and then apport wanted to send a bug report about:
"gnome-settings-daemon crashed with SIGSEGV in g_datalist_id_set_data_full()"

So instead of filing a dublicate, I make a comment here to say it's not fixed.

After the crash occurs, dmesg tells me: "[20160.789767] gnome-settings-[5512]: segfault at aaaaaaac eip b76453dd esp bffec360 error 4"

there is no recent duplicate and upstream closed the bug, if somebody still get the issue in hardy or intrepid use apport to send a bug and an updated stacktrace

I got this just now, on Ubuntu GNOME 14.04 with Gnome 3.10, so it seems it hasnt quite been resolved.