GNOME Bugzilla – Bug 452595
crash in Open Folder:
Last modified: 2007-07-18 15:51:39 UTC
Version: 2.18.1 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy P Icon Theme: Tango Memory status: size: 129441792 vsize: 129441792 resident: 61083648 share: 20844544 rss: 61083648 rss_rlim: 4294967295 CPU usage: start_time: 1183221033 rtime: 230 utime: 191 stime: 39 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 -1208736032 (LWP 3510)] (no debugging symbols found) 0x008ed402 in __kernel_vsyscall ()
+ Trace 144886
Thread 1 (Thread -1208736032 (LWP 3510))
----------- .xsession-errors --------------------- yet, something that must happen before any other GLib function is called. The application needs to be fixed so that it calls if (!g_thread_supported ()) g_thread_init(NULL); as very first thing in its main() function. Please file a bug against this application. ** (gnomebaker:3569): WARNING **: devices_is_disk_inserted - ioctl failed ** (gnomebaker:3569): WARNING **: devices_eject_disk - Error opening device \xe8\u0019? /sr0 ** (gnomebaker:3569): WARNING **: devices_eject_disk - Error opening device P\u001bH /sr0 (nautilus:3510): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed --------------------------------------------------
*** Bug 452596 has been marked as a duplicate of this bug. ***
*** Bug 452597 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us a stack trace with debugging symbols? Please install some debugging packages [1] and reproduce the crash, if possible. Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or simply report a new one. Thanks! [1] debugging packages for nautilus, eel and gnome-desktop, plus debugging packages for glib, gtk+ and gnome-vfs, GNOME's main libraries
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 440327 ***