GNOME Bugzilla – Bug 469559
crash in Epiphany Web Browser: vieing web site with fla...
Last modified: 2007-08-23 13:27:10 UTC
Version: 2.14.3 What were you doing when the application crashed? vieing web site with flash Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.18-4-686 #1 SMP Mon Mar 26 17:17:36 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 216735744 vsize: 216735744 resident: 93093888 share: 21233664 rss: 93093888 rss_rlim: 4294967295 CPU usage: start_time: 1187645208 rtime: 450157 utime: 393999 stime: 56158 cutime:440 cstime: 934 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 -1241205056 (LWP 5604)] [New Thread -1309672560 (LWP 31261)] [New Thread -1335321712 (LWP 31257)] [New Thread -1289749616 (LWP 31254)] [New Thread -1252779120 (LWP 5722)] [New Thread -1244390512 (LWP 5721)] (no debugging symbols found) 0xb6e75eb9 in poll () from /lib/libc.so.6
+ Trace 157347
Thread 4 (Thread -1289749616 (LWP 31254))
----------- .xsession-errors (170292 sec old) --------------------- ** (epiphany:5604): WARNING **: IPP request failed with status 1280 ** (epiphany:5604): WARNING **: IPP request failed with status 1280 ** (epiphany:5604): WARNING **: IPP request failed with status 1280 ** (epiphany:5604): WARNING **: IPP request failed with status 1280 ** (epiphany:5604): WARNING **: IPP request failed with status 1280 libnm_glib_dbus_init: error, org.freedesktop.DBus.Error.FileNotFound raised: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory ...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 349051 ***