Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

*** Bug 404719 has been marked as a duplicate of this bug. ***

Created attachment 81973 [details]
Stack Trace Requested

I've also verified that D-bus is running.

Comment on attachment 81973 [details]
Stack Trace Requested

>(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)
>Registering 'moz.pyloader.1' (libpyloader.so)
>(no debugging symbols found)
>(no debugging symbols found)
>[New Thread -1248650352 (LWP 2700)]
>
>** (epiphany:2693): WARNING **: Unable to connect to system bus: 
>process 2693: arguments to dbus_connection_send_with_reply() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3048.
>This is normally a bug in some application using the D-Bus library.
>  /usr/lib/libdbus-1.so.3 [0xb7f51cde]
>  /usr/lib/libdbus-1.so.3 [0xb7f510c7]
>  /usr/lib/libdbus-1.so.3 [0xb7f455d6]
>  /usr/lib/libdbus-1.so.3(dbus_connection_send_with_reply+0x37f) [0xb7f239ff]
>  /opt/gnome/bin/epiphany [0x809fdea]
>  /usr/lib/libgobject-2.0.so.0(g_type_create_instance+0x4e6) [0xb75a34a6]
>  /usr/lib/libgobject-2.0.so.0 [0xb758a272]
>  /usr/lib/libgobject-2.0.so.0(g_object_newv+0x2d8) [0xb7588518]
>  /usr/lib/libgobject-2.0.so.0(g_object_new_valist+0x217) [0xb7589087]
>  /usr/lib/libgobject-2.0.so.0(g_object_new+0x40) [0xb7589240]
>  /opt/gnome/bin/epiphany(ephy_net_monitor_new+0x25) [0x809fc65]
>  /opt/gnome/bin/epiphany(ephy_shell_get_net_monitor+0x4d) [0x8086ccd]
>  /opt/gnome/bin/epiphany [0x8087c12]
>  /opt/gnome/bin/epiphany(ephy_embed_shell_get_embed_single+0x11) [0x80feca1]
>  /opt/gnome/bin/epiphany [0x80953f7]
>  /usr/lib/libgobject-2.0.so.0(g_object_newv+0x2d8) [0xb7588518]
>  /usr/lib/libgobject-2.0.so.0(g_object_new_valist+0x2bf) [0xb758912f]
>  /usr/lib/libgobject-2.0.so.0(g_object_new+0x40) [0xb7589240]
>  /opt/gnome/bin/epiphany(ephy_window_new_with_chrome+0x4f) [0x808f53f]
>  /opt/gnome/bin/epiphany(ephy_shell_new_tab_full+0xa6) [0x8087116]
>  /opt/gnome/bin/epiphany [0x8085770]
>  /usr/lib/libglib-2.0.so.0 [0xb7511c51]
>  /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x181) [0xb75139d1]
>  /usr/lib/libglib-2.0.so.0 [0xb7516a2f]
>  /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1b7) [0xb7516de7]
>  /usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xc1) [0xb79d7bf1]
>  /opt/gnome/bin/epiphany(main+0x852) [0x8082872]
>  /lib/libc.so.6(__libc_start_main+0xd8) [0xb73c77c8]
>  /opt/gnome/bin/epiphany [0x8081d01]
>
>Program received signal SIGABRT, Aborted.
>[Switching to Thread -1240306960 (LWP 2693)]
>0xb7fe1410 in ?? ()

+ Trace 108354

Could you try running epiphany under gdb (see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for how to do this) as that trace is still not brilliant. Thanks!

*** Bug 405113 has been marked as a duplicate of this bug. ***

*** Bug 405067 has been marked as a duplicate of this bug. ***

*** Bug 403056 has been marked as a duplicate of this bug. ***

This bug and all duplicates happened on Arch Linux. Reporters, could you provide a better backtrace please?

This bug must be something dbus-related. I guess it's related to our recent dbus 0.93 -> 1.0.2 upgrade that aborts when invalid calls into dbus are made. During the upgrade, the system and session bus crash because the running dbus 0.93 tries to reload the 1.0.2 configuration file, which contains settings not supported in the older version. To make things worse, our first package of dbus 1.0.2 didn't have the system-uuid file generated, causing random failures like these.

For the reporters: please supply details about the package version of dbus on your system, if you did restart your system and/or session bus, and if you're still experiencing the problem after upgrading to dbus 1.0.2-3.

*** Bug 405516 has been marked as a duplicate of this bug. ***

*** Bug 405816 has been marked as a duplicate of this bug. ***

*** Bug 406822 has been marked as a duplicate of this bug. ***

*** Bug 406360 has been marked as a duplicate of this bug. ***

*** Bug 406195 has been marked as a duplicate of this bug. ***

*** Bug 407034 has been marked as a duplicate of this bug. ***

*** Bug 407035 has been marked as a duplicate of this bug. ***

ok, I have an assertion backtrace from libdbus. This crash is reproducable with epiphany 2.17.91 also. Looking at the function backtraces, it appears to come from the networkmanager code that we enable in our distribution. To reproduce the crash:

chmod 0 /var/run/dbus/system_bus_socket (or whereever your system bus is)
epiphany

Looking at the code, I think it's located inside ephy_net_monitor_startup in ephy-net-monitor.c.
     dbus = ephy_dbus_get_default ();

After that, there's not a single check for the state of the dbus variable. Is it a connection? is it a NULL, etc etc. dbus 1.0.2 kills epiphany when you do this.

and here's the output:

NOTE: Enabling gecko pango renderer; this may cause performance degradation.
You can set /apps/epiphany/web/enable_pango to "false" to disable it.

(epiphany:32694): libgnomevfs-WARNING **: Error initializing Avahi: Access denied

(epiphany:32694): libgnomevfs-WARNING **: Error initializing Avahi: Access denied

(epiphany:32694): libgnomevfs-WARNING **: Error initializing Avahi: Access denied
Registering 'moz.pyloader.1' (libpyloader.so)

** (epiphany:32694): WARNING **: Unable to connect to system bus: 
process 32694: arguments to dbus_connection_send_with_reply() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3048.
This is normally a bug in some application using the D-Bus library.
  /usr/lib/libdbus-1.so.3 [0xb7e9bcde]
  /usr/lib/libdbus-1.so.3 [0xb7e9b0c7]
  /usr/lib/libdbus-1.so.3 [0xb7e8f5d6]
  /usr/lib/libdbus-1.so.3(dbus_connection_send_with_reply+0x37f) [0xb7e6d9ff]
  epiphany [0x80a3a8a]
  /usr/lib/libgobject-2.0.so.0(g_type_create_instance+0x4e6) [0xb74b94a6]
  /usr/lib/libgobject-2.0.so.0 [0xb74a0272]
  /usr/lib/libgobject-2.0.so.0(g_object_newv+0x2d8) [0xb749e518]
  /usr/lib/libgobject-2.0.so.0(g_object_new_valist+0x217) [0xb749f087]
  /usr/lib/libgobject-2.0.so.0(g_object_new+0x40) [0xb749f240]
  epiphany(ephy_net_monitor_new+0x25) [0x80a3905]
  epiphany(ephy_shell_get_net_monitor+0x4d) [0x808a32d]
  epiphany [0x808b272]
  epiphany(ephy_embed_shell_get_embed_single+0x11) [0x81034e1]
  epiphany [0x8098ae7]
  /usr/lib/libgobject-2.0.so.0(g_object_newv+0x2d8) [0xb749e518]
  /usr/lib/libgobject-2.0.so.0(g_object_new_valist+0x2bf) [0xb749f12f]
  /usr/lib/libgobject-2.0.so.0(g_object_new+0x40) [0xb749f240]
  epiphany(ephy_window_new_with_chrome+0x4f) [0x8092c2f]
  epiphany(ephy_shell_new_tab_full+0xa6) [0x808a776]
  epiphany [0x8088dd0]
  /usr/lib/libglib-2.0.so.0 [0xb7426c51]
  /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x181) [0xb74289d1]
  /usr/lib/libglib-2.0.so.0 [0xb742ba2f]
  /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1b7) [0xb742bde7]
  /usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xc1) [0xb78c7bf1]
  epiphany(main+0x852) [0x8085ed2]
  /lib/libc.so.6(__libc_start_main+0xd8) [0xb72dd7c8]
  epiphany [0x8085361]

For completeness, the same applies to ephy_net_monitor_shutdown, I've seen crashes of epiphany at shutdown here when dbus was killed while epiphany was running. It looks like we traced that one also now.

*** Bug 407547 has been marked as a duplicate of this bug. ***

*** Bug 407573 has been marked as a duplicate of this bug. ***

also had this problem on arch linux, resolved it by manually flushing the stale /var/run/dbus.pid file (i.e., remove the file) and restarting dbus. 

The stack that I posted has no differences when ran through gdb.

I also tried starcycle@gmail.com's resolution and it worked. Rather annoying that it has to be done everytime though.

*** Bug 408156 has been marked as a duplicate of this bug. ***

*** Bug 408383 has been marked as a duplicate of this bug. ***

I run archlinux and reported the same bug.

Version of dbus is now dbus-1.0.2-4 and it seems to be no problem if one starts epiphany (or any other dbus-dependent app) if the dbus daemon is started first :D

/etc/rc.d/dbus start

Also I added dbus to DAEMONS in rc.conf

After upgrading, the problem has went away for me. I don't event have to remove the pid file.

*** Bug 409105 has been marked as a duplicate of this bug. ***

*** Bug 408655 has been marked as a duplicate of this bug. ***

*** Bug 409158 has been marked as a duplicate of this bug. ***

*** Bug 409735 has been marked as a duplicate of this bug. ***

*** Bug 409732 has been marked as a duplicate of this bug. ***

*** Bug 409719 has been marked as a duplicate of this bug. ***

*** Bug 411428 has been marked as a duplicate of this bug. ***

*** Bug 411888 has been marked as a duplicate of this bug. ***

*** Bug 413095 has been marked as a duplicate of this bug. ***

Created attachment 83884 [details] [review]
Check dbus connection before using it

Adds checks for a valid dbus connection before taking action.
In the startup function: check for monitor->priv->bus before placing monitors or calling the network checking function
In the network checking function: return when priv->bus is NULL.

Applies clean to both 2.17.92 and 2.16.x and fixes crashes when the system bus is not available.

committed to trunk and gnome-2-16. Thanks for the patch!

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.

*** Bug 414591 has been marked as a duplicate of this bug. ***

*** Bug 416351 has been marked as a duplicate of this bug. ***

*** Bug 431978 has been marked as a duplicate of this bug. ***

removed from auto-reject list