GNOME Bugzilla – Bug 452775
crash in File Browser: right after login
Last modified: 2007-10-21 17:17:58 UTC
Version: 2.18.1 What were you doing when the application crashed? right after login Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 85872640 vsize: 85872640 resident: 21213184 share: 11771904 rss: 21213184 rss_rlim: 4294967295 CPU usage: start_time: 1183281908 rtime: 131 utime: 117 stime: 14 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 -1208211744 (LWP 2651)] (no debugging symbols found) 0x00477402 in __kernel_vsyscall ()
+ Trace 145022
Thread 1 (Thread -1208211744 (LWP 2651))
----------- .xsession-errors (9 sec old) --------------------- Checking for XComposite extension : passed (v0.3) Checking for XDamage extension : passed Checking for RandR extension : passed Checking for XSync extension : passed Checking Screen 0 ... 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) (nautilus:2651): 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
*** Bug 459867 has been marked as a duplicate of this bug. ***
*** Bug 463132 has been marked as a duplicate of this bug. ***
*** Bug 463130 has been marked as a duplicate of this bug. ***
*** Bug 463065 has been marked as a duplicate of this bug. ***
*** Bug 463064 has been marked as a duplicate of this bug. ***
*** Bug 463892 has been marked as a duplicate of this bug. ***
*** Bug 463890 has been marked as a duplicate of this bug. ***
*** Bug 484583 has been marked as a duplicate of this bug. ***
this is exactly the same issue as bug 439977. *** This bug has been marked as a duplicate of 439977 ***