GNOME Bugzilla – Bug 473104
crash in Open Folder: while i was reading my s...
Last modified: 2007-09-05 15:34:33 UTC
Version: 2.18.3 What were you doing when the application crashed? while i was reading my salary slip 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 140615680 vsize: 140615680 resident: 72413184 share: 22372352 rss: 72413184 rss_rlim: 4294967295 CPU usage: start_time: 1188806830 rtime: 4321 utime: 2795 stime: 1526 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 -1208645920 (LWP 2564)] [New Thread -1254098032 (LWP 5362)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 160037
Thread 2 (Thread -1254098032 (LWP 5362))
----------- .xsession-errors (7 sec old) --------------------- [org.jboss.ide.eclipse.as.core.module.factory.ArchiveModuleFactory] Caching factory --- Hash table keys for warning below: --> file:///home/tywickra (nautilus:3889): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1a5 specified for 0x1200120 (). --- Hash table keys for warning below: --> file:///home/tywickra (nautilus:5346): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2564): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x24766)! --------------------------------------------------
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 ***