GNOME Bugzilla – Bug 484120
crash in Open Folder:
Last modified: 2007-10-07 18:56:51 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 265596928 vsize: 265596928 resident: 196435968 share: 33284096 rss: 196435968 rss_rlim: 4294967295 CPU usage: start_time: 1191646322 rtime: 6550 utime: 5365 stime: 1185 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 -1208846624 (LWP 3884)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 168315
Thread 1 (Thread -1208846624 (LWP 3884))
----------- .xsession-errors (24 sec old) --------------------- (gnome-system-log:4061): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gnome-system-log:4061): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gnome-system-log:4061): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gnome-system-log:4061): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gnome-system-log:4061): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gnome-system-log:4061): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() 07-10-06 02:50:46 (WARNING): [PARQ UL] Removing 222.127.58.196:60230 (BearShare 5.2.1.2) for too many disconnections "Taylor Dayne - Love Will Lead You Back.mp3" 9 secs early (nautilus:3884): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed --------------------------------------------------
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 439977 ***