GNOME Bugzilla – Bug 459021
crash in Home Folder: gconftool-2 --type strin...
Last modified: 2007-07-30 00:22:40 UTC
What were you doing when the application crashed? gconftool-2 --type string --set /desktop/gnome/background/picture_filename /home/zaki/Pictures/Wallpaper/wpchange.sh gconftool-2 --type string --set /desktop/gnome/background/picture_options centered Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 82640896 vsize: 82640896 resident: 32169984 share: 20631552 rss: 32169984 rss_rlim: 4294967295 CPU usage: start_time: 1185035488 rtime: 123 utime: 110 stime: 13 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 -1208326432 (LWP 4157)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 149609
Thread 1 (Thread -1208326432 (LWP 4157))
----------- .xsession-errors --------------------- Launching a SCIM process with x11... Loading socket Config module ... Creating backend ... Loading x11 FrontEnd module ... GTK Panel of SCIM 1.4.5 Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 SESSION_MANAGER=local/zaki-f7:/tmp/.ICE-unix/4052 (gnome-terminal:4229): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (nautilus:4157): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install the following debug packages provided by Fedora: nautilus-debuginfo, glib2-debuginfo, gtk2-debuginfo, pango-debuginfo, gnome-vfs2-debuginfo, libgnome-debuginfo, and libgnomeui-debuginfo. More details can be found here: http://live.gnome.org/GettingTraces
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 439593 ***