GNOME Bugzilla – Bug 543698
crash in Epiphany Web Browser: switching to larger text...
Last modified: 2008-07-19 10:23:42 UTC
Version: 2.22.2 What were you doing when the application crashed? switching to larger text - with toolbar command Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-amd64 #1 SMP Fri Jun 27 00:16:12 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 407224320 vsize: 407224320 resident: 49213440 share: 26345472 rss: 49213440 rss_rlim: 18446744073709551615 CPU usage: start_time: 1216454370 rtime: 151 utime: 132 stime: 19 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7ffb69b30780 (LWP 24757)] [New Thread 0x42d7b950 (LWP 24780)] [New Thread 0x43d7d950 (LWP 24766)] [New Thread 0x4357c950 (LWP 24765)] [New Thread 0x4257a950 (LWP 24763)] [New Thread 0x41578950 (LWP 24762)] [New Thread 0x41d79950 (LWP 24761)] [New Thread 0x40d77950 (LWP 24758)] (no debugging symbols found) 0x00007ffb624e8edf in waitpid () from /lib/libpthread.so.0
+ Trace 203246
Thread 1 (Thread 0x7ffb69b30780 (LWP 24757))
----------- .xsession-errors (237 sec old) --------------------- Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout e Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout e Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout e Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout e Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout e Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout e Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout e Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout e Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout e Couldn't get main dbus connection: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout e closing closing closing ** (nautilus:3601): WARNING **: Hit unhandled case 2 (Generic error) in fm_report_error_loading_directory --------------------------------------------------
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 525357 ***