GNOME Bugzilla – Bug 510244
crash in Computer: monter une clef usb
Last modified: 2008-01-17 18:57:57 UTC
Version: 2.18.3 What were you doing when the application crashed? monter une clef usb Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 171565056 vsize: 171565056 resident: 25960448 share: 15003648 rss: 25960448 rss_rlim: 4294967295 CPU usage: start_time: 1200587499 rtime: 8847 utime: 8320 stime: 527 cutime:574 cstime: 73 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 0xb6d896b0 (LWP 4361)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 185736
Thread 1 (Thread 0xb6d896b0 (LWP 4361))
----------- .xsession-errors (150 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ====================== libparted : 1.7.1 ====================== Avertissement du gestionnaire de fenêtres : last_user_time (3076338736) is greater than comparison timestamp (2298889320). This most likely represents a buggy client sending inaccurate timestamps i Avertissement du gestionnaire de fenêtres : 0x3000003 (GParted) appears to be one of the offending windows with a timestamp of 3076338736. Working around... Unable to open /dev/hdc read-write (Système de fichiers accessible en lecture seulement). /dev/hdc has been opened read-only. ** Message: drive = 8aa1ec0 ** Message: volume = 0 Unable to open /dev/hdc - unrecognised disk label. --------------------------------------------------
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 ***