GNOME Bugzilla – Bug 600702
crash in Epiphany Web Bookmarks: Closing epiphany
Last modified: 2009-11-04 16:40:12 UTC
Version: 2.28.1 What were you doing when the application crashed? Closing epiphany Distribution: Gentoo Base System release 1.12.13 Gnome Release: 2.26.3 2009-10-08 (Gentoo) BugBuddy Version: 2.28.0 System: Linux 2.6.31-zen4 #4 ZEN PREEMPT Wed Oct 21 23:17:17 CEST 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10603901 Selinux: No Accessibility: Disabled GTK+ Theme: Shiki-Gentoo Icon Theme: gnome-gentoo GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 713629696 vsize: 713629696 resident: 151502848 share: 38625280 rss: 151502848 rss_rlim: 18446744073709551615 CPU usage: start_time: 1257352481 rtime: 3449 utime: 3316 stime: 133 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany' [Thread debugging using libthread_db enabled] [New Thread 0x7ffe93bc0790 (LWP 7903)] [New Thread 0x7ffe76b06950 (LWP 7934)] [New Thread 0x7ffe7fb70950 (LWP 7921)] 0x00007ffe86d2c55f in waitpid () from /lib/libpthread.so.0
+ Trace 218796
Thread 1 (Thread 0x7ffe93bc0790 (LWP 7903))
----------- .xsession-errors (9183 sec old) --------------------- ** (evolution:6779): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:6779): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:6779): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:6779): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:6779): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:6779): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ** (evolution:6779): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed ...Too much output, ignoring rest... --------------------------------------------------
Trace contains:
+ Trace 218797
Then, maybe it's caused by flash, sorry, I will check better the crash next time *** This bug has been marked as a duplicate of bug 600333 ***