GNOME Bugzilla – Bug 553574
crash in Computer: choisir une application ...
Last modified: 2008-09-24 12:29:48 UTC
Version: 2.20.0 What were you doing when the application crashed? choisir une application par défaut dans les propriétées Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (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: 80121856 vsize: 80121856 resident: 26742784 share: 15958016 rss: 26742784 rss_rlim: 4294967295 CPU usage: start_time: 1222258972 rtime: 299 utime: 283 stime: 16 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 0xb6bed720 (LWP 2553)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 207193
Thread 1 (Thread 0xb6bed720 (LWP 2553))
----------- .xsession-errors --------------------- xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 Initializing gnome-mount extension seahorse nautilus module initialized (nautilus:2349): Eel-WARNING **: No extension, not implemented yet (nautilus:2349): Eel-WARNING **: No extension, not implemented yet Initializing gnome-mount extension seahorse nautilus module initialized (nautilus:2553): Eel-WARNING **: No extension, not implemented yet (nautilus:2553): 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 ***