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

StacktraceTop:IA__g_slice_alloc (mem_size=12)
IA__g_list_append (list=0x0, data=0x8bb5f80)
_gdk_event_queue_append (display=0x8b4e000, event=0x8bb5f80)
_gdk_events_queue (display=0x8b4e000)
gdk_event_dispatch (source=0x8b57f80, callback=0,

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

I'm getting this same error on an upgrade to 12.10.

I'm seeing this several times a day in Quantal. I'll try with Valgrind, give me some time ..

I haven't noticed getting this while using pulseaudio,but I usually have vlc open and constantly watching something with audio. The only other common denominator, at least for me, is that I always get this while logged in using OpenBox. It's always after a gnome-settings-daemon error that my theme drops into something resembling Windows 95. I think what's happening is that my these support is dropped. What this has to do with pulse, is beyond me but the error always inculpates the gnome-settings-daemon.

I ran g-s-d through valgrind for 2 days now, and the issues seems to have happened twice during the night, which is consistent with what I though was my experience without valgrind as well. May have something to do with turning off or locking the screen when the laptop is not in use - there is nothing else happening over night that I know of.

I piped the command through tee in order to also catch g-s-d's own debug log:

G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gnome-settings-daemon debug | tee gnome-settings-daemon-with-valgrind-debug.log

Both log files are attached

I forgot to mention that these logs are from one overnight run, I discarded the logs from the first night.

Also somehow the dashes in front of the debug option where lost when copying the valgrind command from the terminal. For the sake of correctness her it is again, sorry for spam:

G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gnome-settings-daemon --debug | tee gnome-settings-daemon-with-valgrind-debug.log