I was just playing in the control center, clicking different background images, at random. After switching back and forth between random images, the entire dialog froze up and stop responding. ps showed gnome-background-properties eating CPU. strace showed that this is what it was doing: write(2, "\n(gnome-background-properties:16682): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL\' failed\n", 117) = 117 write(2, "\n(gnome-background-properties:16682): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL\' failed\n", 118) = 118 write(2, "\n(gnome-background-properties:16682): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL\' failed\n", 114) = 114 write(2, "\n(gnome-background-properties:16682): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL\' failed\n", 117) = 117 write(2, "\n(gnome-background-properties:16682): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL\' failed\n", 118) = 118 write(2, "\n(gnome-background-properties:16682): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL\' failed\n", 114) = 114 write(2, "\n(gnome-background-properties:16682): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL\' failed\n", 117) = 117 write(2, "\n(gnome-background-properties:16682): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL\' failed\n", 118) = 118 ... and so on, and so on, and so on...
Could you please run gnome-background-properties with "--g-fatal-warnings" and get the debug backtrace of the crash? http://fedoraproject.org/wiki/StackTraces has details. Make sure you install the appropriate debuginfo packages so that the backtrace has symbols.
I believe that I explained that this was not a crash. Gnome-background-properties was spinning in an infinite loop, printing an endless stream of these two error messages. I'll keep trying to repeat this bug, and will update this bug when I do.
If you run it with --g-fatal-warnings, it will crash when printing the warning, instead of looping. Then you can gather a backtrace.
The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there have not been any updates to the report since thirty (30) days or more since we requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. Thank you in advance. Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.