GNOME Bugzilla – Bug 510828
crash in Open Folder: gconftool-2 -t str --set...
Last modified: 2008-01-21 14:21:11 UTC
Version: 2.18.3 What were you doing when the application crashed? gconftool-2 -t str --set /desktop/gnome/background/picture_filename /tmp/wp.jpg gconftool-2 -t str --set /desktop/gnome/background/picture_options centered Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 87613440 vsize: 87613440 resident: 15896576 share: 13262848 rss: 15896576 rss_rlim: 4294967295 CPU usage: start_time: 1199781948 rtime: 959 utime: 749 stime: 210 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208998176 (LWP 12554)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 186086
Thread 1 (Thread -1208998176 (LWP 12554))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib/libpoppler.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgstbase-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgstinterfaces-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgstaudio-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 439977 ***