GNOME Bugzilla – Bug 531710
crash in Computer: rien
Last modified: 2008-05-06 11:53:43 UTC
Version: 2.20.0 What were you doing when the application crashed? rien Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.20.1 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: Clearlooks Icon Theme: gnome Memory status: size: 87605248 vsize: 87605248 resident: 28332032 share: 15908864 rss: 28332032 rss_rlim: 4294967295 CPU usage: start_time: 1210061636 rtime: 1917 utime: 1713 stime: 204 cutime:0 cstime: 2 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 0xb6c3b720 (LWP 3218)] (no debugging symbols found) 0xb7669321 in waitpid () from /lib/libpthread.so.0
+ Trace 197016
Thread 1 (Thread 0xb6c3b720 (LWP 3218))
----------- .xsession-errors --------------------- (epiphany-browser:3610): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany-browser:3610): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany-browser:3610): libgnomevfs-WARNING **: Failed to create service browser: Bad state Avertissement du gestionnaire de fenêtres : Received a _NET_WM_MOVERESIZE message for 0x280001e (Exercice 1); these messages lack timestamps and therefore suck. Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00216 (Sans nom1 ) Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Avertissement du gestionnaire de fenêtres : Received a _NET_WM_MOVERESIZE message for 0x14037dc (test odt); these messages lack timestamps and therefore suck. (nautilus:3218): 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 ***