GNOME Bugzilla – Bug 506351
crash in Home Folder: I've downloaded a lot of...
Last modified: 2007-12-30 01:19:40 UTC
What were you doing when the application crashed? I've downloaded a lot of wallpapers with wget from art.gnome.org. Actually I have a directory with 1750 wallpapers. When I activate the "Icon view" from nautilus, the application stops and closes. I've activated the 5MB limit for image thumbs. I do this without problems at Window machines first than come to Linux (and the thumbs drawing its slow at nautilus, there are how to activate an invisible cache file to thumbs?) Use delete key to delete folders and files at tree panel can be useful too (It's not possible do this at tree) and a network item at tree too (there are the nerwork link, but not directily at tree, at tree only home, file system and mounted items. Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gartoon Memory status: size: 227651584 vsize: 227651584 resident: 170835968 share: 17248256 rss: 170835968 rss_rlim: 4294967295 CPU usage: start_time: 1198974009 rtime: 3977 utime: 3557 stime: 420 cutime:4 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6b606c0 (LWP 22283)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 183499
Thread 1 (Thread 0xb6b606c0 (LWP 22283))
Created attachment 101824 [details] Nautilus debug log file generated after bug I've added here the Nautilus debug log file generated after bug. Translating some informations at file: "Falha ao abrir arquivo" = Failed to open file "Muitos arquivos abertos" = Many opened files
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 483884 ***