GNOME Bugzilla – Bug 502441
crash in System Log: I am getting error code ...
Last modified: 2007-12-08 11:40:37 UTC
Version: 2.18.1 What were you doing when the application crashed? I am getting error code 110 when trying to use a 500gb storage usb device will not mount I really need help it mounts perfectly fine in a windows enviroment Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 53149696 vsize: 53149696 resident: 27934720 share: 17117184 rss: 27934720 rss_rlim: 4294967295 CPU usage: start_time: 1197082956 rtime: 464 utime: 424 stime: 40 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/sbin/gnome-system-log' (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 -1208502560 (LWP 5773)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 181193
Thread 1 (Thread -1208502560 (LWP 5773))
----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/5511 Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-5731-1972604239-1197082798 --active --geometry 80x24+575+132 --title root@localhost:/ --wo --------------------------------------------------
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 442846 ***