GNOME Bugzilla – Bug 494933
crash in Open Folder: Using file manager
Last modified: 2007-11-08 18:07:45 UTC
Version: 2.18.3 What were you doing when the application crashed? Using file manager 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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 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: 95838208 vsize: 95838208 resident: 35864576 share: 22437888 rss: 35864576 rss_rlim: 4294967295 CPU usage: start_time: 1194469366 rtime: 839 utime: 579 stime: 260 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 -1208416544 (LWP 2641)] [New Thread -1242354800 (LWP 5883)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176290
Thread 2 (Thread -1242354800 (LWP 5883))
----------- .xsession-errors (23 sec old) --------------------- Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e02791 (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e03034 (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e03034 (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --- Hash table keys for warning below: --> file:///home/daniel (nautilus:5870): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2641): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x1ee0)! --------------------------------------------------
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 454799 ***