GNOME Bugzilla – Bug 530491
crash in Open Folder:
Last modified: 2008-04-29 07:14:38 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Gentoo Base System release 2.0.0 Gnome Release: 2.20.3 2008-02-03 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.24-gentoo-r3 #11 SMP PREEMPT Thu Apr 24 03:57:09 PDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 78741504 vsize: 78741504 resident: 24317952 share: 14045184 rss: 24317952 rss_rlim: 4294967295 CPU usage: start_time: 1209447304 rtime: 97 utime: 90 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb76446c0 (LWP 12886)] 0xb7f47410 in __kernel_vsyscall ()
+ Trace 196406
Thread 1 (Thread 0xb76446c0 (LWP 12886))
----------- .xsession-errors (1878 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 gecko: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. gecko: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. firefox-bin exited with non-zero status (1) /opt/vmware/workstation/lib/bin/vmware: /opt/vmware/workstation/lib/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2) using /home/plrca2/.azureus/gentoo.config /usr/bin/azureus: line 72: /dev/stderr: Permission denied ...Too much output, ignoring rest... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 508751 ***