GNOME Bugzilla – Bug 464583
crash in Open Folder:
Last modified: 2007-08-10 13:39: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.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: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 82280448 vsize: 82280448 resident: 27906048 share: 20500480 rss: 27906048 rss_rlim: 4294967295 CPU usage: start_time: 1186551866 rtime: 213 utime: 178 stime: 35 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 -1208604960 (LWP 12634)] [New Thread -1210950768 (LWP 12642)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 153633
Thread 2 (Thread -1210950768 (LWP 12642))
----------- .xsession-errors (21890 sec old) --------------------- ^1A^7O^4D ^4Clubber ^4Lang^7 was blasted by Garbo^7's support fire ^2*^0Xx ^2HoLoCroN ^0xX^2*^7 was blasted by Garbo^7's support fire [skipnotify]: (^1Aluminor^7_from_^2B^3r^2a^3^ss^2i^7)^3(D,3)^7:^5Sorry! ^1A^7O^4D 88 Fingers Louie^7 rediscovered gravity ^w!!!! ^1Ultra Kill ^w> ^*Garbo ^w< ^1Ultra Kill ^w!!!! ^0|bc|^0P^8eanut^0B^8utter^0J^7 was killed by ^5*A^7L^5M*^7's MP40 [skipnotify]Bane^7 entered the game Bane^7 has joined the Axis team^7! ^2=^1H^7z^4K^2=^1fy^7rfy^4tr^7 was killed by HELL 22^7's Thompson ^!Interested in being a paying admin? Email me at beo.beo@gmail.com ^1he^7nk^4ie^7 was blasted by ^1A^7O^4D ^1Obl^7ivi^4on^7's Panzerfaust ^1A^q^wO^5^4D ^hWeed^0-^hRang^7 was blasted by ^1A^7O^4D ^1Obl^7ivi^4on^7's Panzerfaust ^1A^7O^4D ^3C O O K^7 was blasted by ^1A^7O^4D ^1Obl^7ivi^4on^7's Panzerfaust ...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 ***