GNOME Bugzilla – Bug 514251
crash in Home Folder: 搜索文件 是不是和gooogle桌面搜索有冲...
Last modified: 2008-02-04 13:21:32 UTC
What were you doing when the application crashed? 搜索文件 是不是和gooogle桌面搜索有冲突 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.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 225492992 vsize: 225492992 resident: 50880512 share: 22310912 rss: 50880512 rss_rlim: 4294967295 CPU usage: start_time: 1202149626 rtime: 340 utime: 291 stime: 49 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 -1209018656 (LWP 4887)] (no debugging symbols found) 0x00a9d402 in __kernel_vsyscall ()
+ Trace 188025
Thread 1 (Thread -1209018656 (LWP 4887))
----------- .xsession-errors --------------------- 窗口管理器警告:为 0x3e00004 (WPS Office) 指定了无效的 WM_TRANSIENT_FOR 窗口 0x3e00003。 closing closing Loading "installonlyn" plugin warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 7fac5991 窗口管理器警告:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c00003 (Google 桌) 窗口管理器警告:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. 无法在“/home/kangning/.ntrc_2/config”打开配置文件 使用默认配置 :))... (nautilus:2809): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:2809): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:4887): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 436071 ***