abrt 1.0.0 detected a crash. Attached file: backtrace cmdline: /usr/libexec/gnome-settings-daemon component: gnome-settings-daemon executable: /usr/libexec/gnome-settings-daemon kernel: 2.6.31.9-174.fc12.x86_64 package: gnome-settings-daemon-2.28.1-10.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 381629 [details] File: backtrace
Crash in gnome-desktop
I think we probably need to ensure that rect is entirely contained in the pixbuf extents, in pixbuf_draw_gradient
*** Bug 552232 has been marked as a duplicate of this bug. ***
*** Bug 552083 has been marked as a duplicate of this bug. ***
I've noticed that since the crash gnome-settings-daemon does not start (crashes each time) when I log in (e.g. fonts in gnome-panel & nautils are weirdly huge). Relatively quick workaround is to open the "Change desktop background" dialog (settings daemon is launched) and restart nautilus. Before the first crash it was all OK. Any idea which settings cause these crashes? Can I do some quick cleanup which could help me to get rid of this?
run it under gdb and see where it crashes ?
I've already submitted the backtrace to my original bug: https://bugzilla.redhat.com/attachment.cgi?id=381534&action=edit It fails in the pixbuf_draw_gradient you mention in comment #3. Sorry, I don't know any details about what this function does, so I'm not able to figure our what setting could cause these crashes.
*** Bug 552686 has been marked as a duplicate of this bug. ***
*** Bug 553202 has been marked as a duplicate of this bug. ***
gnome-desktop-2.28.2-3.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gnome-desktop'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0469
gnome-desktop-2.28.2-3.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.