GNOME Bugzilla – Bug 443927
crash in Open Folder: nothing...zip ...
Last modified: 2007-06-05 00:11:16 UTC
Version: 2.18.1 What were you doing when the application crashed? nothing...zip ... 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 83300352 vsize: 83300352 resident: 25522176 share: 16982016 rss: 25522176 rss_rlim: 4294967295 CPU usage: start_time: 1180962463 rtime: 53 utime: 49 stime: 4 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 -1208998176 (LWP 13833)] (no debugging symbols found) 0x00d46402 in __kernel_vsyscall ()
+ Trace 138109
Thread 1 (Thread -1208998176 (LWP 13833))
----------- .xsession-errors --------------------- seahorse nautilus module initialized Initializing nautilus-flac-converter extension Initializing nautilus-open-terminal extension Initializing nautilus-image-converter extension ** (evolution:13839): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:13839): DEBUG: mailto URL program: evolution (evolution:13839): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (nautilus:13833): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (evolution:13839): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 File /home/giray/nautilus-debug-log.txt has finished changing (evolution:13839): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:13839): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 flushing all words Finished indexing. Waiting for new events... --------------------------------------------------
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 ***