GNOME Bugzilla – Bug 472290
crash in Epiphany Web Browser: closing down
Last modified: 2007-08-31 21:17:11 UTC
Version: 2.14.3 What were you doing when the application crashed? closing down Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18 #7 PREEMPT Sat Jul 21 20:59:30 BST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Lush Icon Theme: Lush Memory status: size: 110850048 vsize: 110850048 resident: 41705472 share: 22548480 rss: 41705472 rss_rlim: 4294967295 CPU usage: start_time: 1188582428 rtime: 9764 utime: 9593 stime: 171 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany' (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 -1242097456 (LWP 13746)] (no debugging symbols found) 0xb6f3dbf1 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 159433
Thread 1 (Thread -1242097456 (LWP 13746))
----------- .xsession-errors --------------------- ** Message: File monitoring not supported in the compiled version of gnome-vfs: bookmarks won't be monitored. (epiphany:13746): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany:13746): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany:13746): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany:13746): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (bug-buddy:14022): gnome-vfs-modules-WARNING **: Could not initialize inotify Failed to read a valid object file image from memory. --------------------------------------------------
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 349051 ***