GNOME Bugzilla – Bug 511053
crash in File Browser: Propiedades de un icono,...
Last modified: 2008-01-23 10:10:21 UTC
Version: 2.18.3 What were you doing when the application crashed? Propiedades de un icono, en este caso de un Volumen extraible. Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 90570752 vsize: 90570752 resident: 40480768 share: 16588800 rss: 40480768 rss_rlim: 4294967295 CPU usage: start_time: 1200930260 rtime: 2661 utime: 2444 stime: 217 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 0xb6e1b6b0 (LWP 3065)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 186208
Thread 1 (Thread 0xb6e1b6b0 (LWP 3065))
----------- .xsession-errors (77 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 (gnome-terminal:3254): GnomeUI-WARNING **: While connecting to session manager: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed. Advertencia del gestor de ventanas: last_user_time (3076097072) is greater than comparison timestamp (2634714587). This most likely represents a buggy client sending inaccurate timestamps in messages Advertencia del gestor de ventanas: 0x220001f (Terminal) appears to be one of the offending windows with a timestamp of 3076097072. Working around... --------------------------------------------------
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 ***