GNOME Bugzilla – Bug 467730
crash in File Browser: Stavo effettuando una ri...
Last modified: 2007-08-21 20:28:31 UTC
Version: 2.18.3 What were you doing when the application crashed? Stavo effettuando una ricerca 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:21:43 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 559484928 vsize: 559484928 resident: 40742912 share: 20815872 rss: 40742912 rss_rlim: 18446744073709551615 CPU usage: start_time: 1187364344 rtime: 513 utime: 466 stime: 47 cutime:0 cstime: 2 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 46912496348208 (LWP 3155)] [New Thread 1199618384 (LWP 5633)] (no debugging symbols found) 0x0000003fea8c82e6 in poll () from /lib64/libc.so.6
+ Trace 155961
Thread 2 (Thread 1199618384 (LWP 5633))
----------- .xsession-errors --------------------- open(/dev/video2): No such file or directory open(/dev/video3): No such file or directory Found Logitech QuickCam Pro 4000 at /dev/video0 --- Hash table keys for warning below: --> file:///home/davalv (nautilus:3828): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Some deprecated features have been used. Set the environment variable GUILE_WARN_DEPRECATED to "detailed" and rerun the program to get more information. Set it to "no" to suppress this message. (nautilus:3155): GLib-CRITICAL **: g_utf8_strdown: assertion `str != 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 454799 ***