GNOME Bugzilla – Bug 492283
crash in File Browser: I was searching for file...
Last modified: 2007-11-01 15:55:33 UTC
Version: 2.18.3 What were you doing when the application crashed? I was searching for file "client.conf" in the file system 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 14:35:28 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 438116352 vsize: 438116352 resident: 60096512 share: 29605888 rss: 60096512 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193902362 rtime: 138 utime: 124 stime: 14 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912697254640 (LWP 3231)] [New Thread 1094719824 (LWP 3242)] (no debugging symbols found) 0x00002aaab11812e6 in poll () from /lib64/libc.so.6
+ Trace 174304
Thread 2 (Thread 1094719824 (LWP 3242))
----------- .xsession-errors --------------------- Brakujący parametr dla --import-file Uruchom "nm-vpn-properties --help" aby zobaczyć listę wszystkich dostępnych opcji. --- Hash table keys for warning below: --> file:///home/marzenia (nautilus:3203): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2911): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff37da3000 (nautilus:3231): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff8fdfd000 --------------------------------------------------
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 ***