GNOME Bugzilla – Bug 530305
crash in File Browser: Apri con altra applicazi...
Last modified: 2008-04-28 08:08:57 UTC
Version: 2.20.0 What were you doing when the application crashed? Apri con altra applicazione Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Nuvola Icon Theme: Nuvola Memory status: size: 79106048 vsize: 79106048 resident: 25346048 share: 16461824 rss: 25346048 rss_rlim: 4294967295 CPU usage: start_time: 1209360133 rtime: 423 utime: 383 stime: 40 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6a99720 (LWP 3365)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196310
Thread 1 (Thread 0xb6a99720 (LWP 3365))
----------- .xsession-errors (8 sec old) --------------------- *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. *** Gnome Registry Session: yes. OpenOffice path is '/usr/lib/openoffice' OpenOffice path is '/usr/lib/openoffice' OpenOffice path is '/usr/lib/openoffice' OpenOffice path is '/usr/lib/openoffice' Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800003 (Salva come) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (nautilus:3365): 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 ***