GNOME Bugzilla – Bug 446554
crash in Computer:
Last modified: 2007-07-18 15:53:45 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.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: 148516864 vsize: 148516864 resident: 43274240 share: 15040512 rss: 43274240 rss_rlim: 4294967295 CPU usage: start_time: 1181545059 rtime: 472 utime: 438 stime: 34 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 -1208690976 (LWP 3180)] (no debugging symbols found) 0x00c85402 in __kernel_vsyscall ()
+ Trace 140200
Thread 1 (Thread -1208690976 (LWP 3180))
----------- .xsession-errors (12 sec old) --------------------- ** Message: Hit unexpected error "目錄內仍有檔案存在" while doing a file operation. ** Message: Hit unexpected error "目錄內仍有檔案存在" while doing a file operation. ** Message: Hit unexpected error "目錄內仍有檔案存在" while doing a file operation. (gnome-terminal:3307): Vte-WARNING **: No handler for control sequence `device-control-string' defined. kbuildsycoca running... DCOP Cleaning up dead connections. ScimInputContextPlugin() ~ScimInputContextPlugin() ScimInputContextPlugin() WARNING: please edit ~/.scim/global and change /DefaultConfigModule to kconfig (nautilus:3180): GLib-CRITICAL **: g_markup_parse_context_end_parse: assertion `context->state != STATE_ERROR' failed (bug-buddy:4233): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: 第 1 行第 40 個字發生錯誤:元素‘b’已關閉,但開啟中的元素是‘span’ --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 451982 has been marked as a duplicate of this bug. ***
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 ***