GNOME Bugzilla – Bug 512597
crash in File Browser: I find all spreadshet fr...
Last modified: 2008-01-28 17:05:27 UTC
Version: 2.18.3 What were you doing when the application crashed? I find all spreadshet from my home folder ( *.ods ) Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 181874688 vsize: 181874688 resident: 87498752 share: 44335104 rss: 87498752 rss_rlim: 4294967295 CPU usage: start_time: 1201531519 rtime: 1861 utime: 1644 stime: 217 cutime:251 cstime: 37 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 -1208809760 (LWP 2527)] [New Thread -1302795376 (LWP 8353)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 187077
Thread 2 (Thread -1302795376 (LWP 8353))
----------- .xsession-errors (10 sec old) --------------------- Ostrzeżenie menedżera okien: Nieprawidłowa wartość WM_TRANSIENT_FOR dla okna 0x66 określona w 0x4a01123 (Wybierz ka). --- Hash table keys for warning below: --> file:///home/Jarek (nautilus:8247): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:8247): GLib-CRITICAL **: g_hash_table_insert: assertion `hash_table != NULL' failed (nautilus:8247): GLib-CRITICAL **: g_hash_table_insert: assertion `hash_table != NULL' failed (nautilus:2527): GnomeUI-CRITICAL **: size_prepared_cb: assertion `width > 0 && height > 0' failed (nautilus:2527): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x1c1e1)! --------------------------------------------------
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 ***