GNOME Bugzilla – Bug 464273
crash in Open Folder: nothing particular
Last modified: 2007-08-07 09:04:01 UTC
Version: 2.18.3 What were you doing when the application crashed? nothing particular Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-33.fc7 #1 SMP Mon Jul 23 16:59:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 506310656 vsize: 506310656 resident: 67252224 share: 23060480 rss: 67252224 rss_rlim: 18446744073709551615 CPU usage: start_time: 1186470547 rtime: 249 utime: 208 stime: 41 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496475184 (LWP 23857)] (no debugging symbols found) 0x00000039a100d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 153413
Thread 1 (Thread 46912496475184 (LWP 23857))
----------- .xsession-errors (1677 sec old) --------------------- localuser:gremaud being added to access control list SESSION_MANAGER=local/stealth.spectro.jussieu.fr:/tmp/.ICE-unix/23731 winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running (gnome-terminal:23870): Vte-WARNING **: No handler for control sequence `device-control-string' defined. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e0005a (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e0005a (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
*** Bug 464274 has been marked as a duplicate of this bug. ***
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 436873 ***