GNOME Bugzilla – Bug 397969
crash in Epiphany Web Bookmarks:
Last modified: 2007-01-18 12:40:53 UTC
Version: 2.16.1 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.16.2 2006-11-20 (FreeBSD GNOME Project) BugBuddy Version: 2.16.1 System: FreeBSD 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Mon Dec 11 15:36:42 CET 2006 tilt@kamster:/usr/obj/usr/src/sys/MYKERNEL i386 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: No Accessibility: Disabled Memory status: size: 1605632 vsize: 0 resident: 1605632 share: 0 rss: 12189696 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 626075 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/local/bin/epiphany' (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100183] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100183] 0x29179711 in wait4 () from /lib/libc.so.6
+ Trace 103221
Thread 1 (LWP 100183)
----------- .xsession-errors --------------------- LibGTop-Server: pid 28843 received eof. Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x360001f (Actuele wa); these messages lack timestamps and therefore suck. process 56005: Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application. D-Bus not compiled with backtrace support so unable to print a backtrace ** (bug-buddy:56032): WARNING **: Couldn't load icon for Bonobo Component Browser ** (bug-buddy:56032): WARNING **: Couldn't load icon for Menu Editor ** (bug-buddy:56032): WARNING **: Couldn't load icon for Open Folder This libgtop was compiled on FreeBSD 6.1-STABLE i386 If you see strange problems caused by it, you should recompile libgtop and dependent applications warning: Unable to get location for thread creation breakpoint: generic error --------------------------------------------------
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 358007 ***