GNOME Bugzilla – Bug 469054
crash in Open Folder:
Last modified: 2007-08-22 13:35:17 UTC
Version: 2.18.3 What were you doing when the application crashed? 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-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gTangish-2.0a1 Memory status: size: 143618048 vsize: 143618048 resident: 45543424 share: 35602432 rss: 45543424 rss_rlim: 4294967295 CPU usage: start_time: 1187740681 rtime: 331 utime: 318 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 -1209121056 (LWP 3075)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 156997
Thread 1 (Thread -1209121056 (LWP 3075))
----------- .xsession-errors (10 sec old) --------------------- Checking for GLX_SGIX_fbconfig : passed Checking for GLX_EXT_texture_from_pixmap : passed Checking for non power of two texture support : passed Checking maximum texture size : passed (2048x2048) compiz: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. compiz: No manageable screens found on display :0.0 (gnome-session:2643): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch /usr/sbin/pirut:51: GtkWarning: gdk_xsettings_watch_cb(): Couldn't find window to unwatch gtk.main_iteration() Launched application : 3061 Initializing gnome-mount extension (nautilus:3075): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 468808 ***