GNOME Bugzilla – Bug 472957
crash in Open Folder:
Last modified: 2007-09-05 15:34:29 UTC
Version: 2.18.3 What were you doing when the application crashed? 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.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 508444672 vsize: 508444672 resident: 33529856 share: 20807680 rss: 33529856 rss_rlim: 18446744073709551615 CPU usage: start_time: 1188070855 rtime: 1523 utime: 1215 stime: 308 cutime:374 cstime: 129 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 46912500715536 (LWP 2580)] [New Thread 1115834704 (LWP 2516)] (no debugging symbols found) 0x000000337fac82e6 in poll () from /lib64/libc.so.6
+ Trace 159924
Thread 2 (Thread 1115834704 (LWP 2516))
----------- .xsession-errors (696518 sec old) --------------------- MPlayer SVN-r23784 rpm.livna.org (C) 2000-2007 MPlayer Team CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ (Family: 15, Model: 67, Stepping: 3) CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1 Compiled with runtime CPU detection. mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing http://192.168.1.150/img/video.asf. Resolving 192.168.1.150 for AF_INET6... Couldn't resolve name for AF_INET6: 192.168.1.150 Connecting to server 192.168.1.150[192.168.1.150]: 80... Cache size set to 320 KBytes Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache fill: 0.00% (0 bytes) Cache f ...Too much output, ignoring rest... --------------------------------------------------
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 ***