GNOME Bugzilla – Bug 521759
crash in Home Folder: I was about to open a fi...
Last modified: 2008-03-11 18:24:37 UTC
What were you doing when the application crashed? I was about to open a file without a default action/application to open. So the window "Open with" popped up and when it was loading the list of available applications, it crashed. Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 80539648 vsize: 80539648 resident: 24981504 share: 14618624 rss: 24981504 rss_rlim: 4294967295 CPU usage: start_time: 1205236170 rtime: 1577 utime: 1443 stime: 134 cutime:3 cstime: 1 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6bd36c0 (LWP 3916)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 192069
Thread 1 (Thread 0xb6bd36c0 (LWP 3916))
----------- .xsession-errors (16 sec old) --------------------- CConn: Using ZRLE encoding Tue Mar 11 09:20:05 2008 CConn: Throughput 20416 kbit/s - changing to hextile encoding CConn: Throughput 20416 kbit/s - changing to full colour CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConn: Using hextile encoding Tue Mar 11 09:21:12 2008 main: read: Connection reset by peer (104) Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": libgnomebreakpad.so: cannot open shared object file: Arquivo ou diretório não encontrado Message: device: default (nautilus:3916): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
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 355018 ***