GNOME Bugzilla – Bug 314598
Evolution doesn't start anymore because of a dbus problem
Last modified: 2012-04-20 12:02:35 UTC
Steps to reproduce: 1.Check the option "send a dbus message when new mail arrives" 2. Close evolution 3. Restart evolution Stack trace: (gdb) run Starting program: /usr/bin/evolution (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) ---Type <return> to continue, or q <return> to quit--- (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) ---Type <return> to continue, or q <return> to quit--- (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) [Thread debugging using libthread_db enabled] [New Thread 46912610671568 (LWP 5841)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (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) ---Type <return> to continue, or q <return> to quit--- (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) es menu class init (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) ---Type <return> to continue, or q <return> to quit--- (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) adding hook target 'source' (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (evolution:5841): camel-WARNING **: Invalid root: '/home/rick/.evolution/mail/local/Drafts.ibex.index' (evolution:5841): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution:5841): camel-WARNING **: block size: 1024 (1024) OK (evolution:5841): camel-WARNING **: free: 0 (0 add size < 1024) OK (evolution:5841): camel-WARNING **: last: 6144 (6144 and size: 1024) BAD (evolution:5841): camel-WARNING **: flags: unSYNC (no debugging symbols found) (evolution:5841): evolution-mail-WARNING **: couldn't get service : No provider available for protocol `' [New Thread 1082132832 (LWP 5845)] (no debugging symbols found) [New Thread 1090525536 (LWP 5849)] [New Thread 1098918240 (LWP 5850)] [New Thread 1107310944 (LWP 5851)] (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) Failed to connect to the D-BUS daemon: Unable to determine the address of the message bus 5841: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 4029. This is normally a bug in some application using the D-BUS library. 5841: arguments to dbus_connection_set_watch_functions() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3320. This is normally a bug in some application using the D-BUS library. ** ERROR **: Not enough memory to set up DBusConnection for use with GLib aborting... Program received signal SIGABRT, Aborted. [Switching to Thread 46912610671568 (LWP 5841)] 0x00002aaab0d6add0 in raise () from /lib/libc.so.6 (gdb) thread apply all bt
+ Trace 62639
Thread 5 (Thread 1107310944 (LWP 5851))
Other information: Hello, I am running debian unstable pure64, and I am using evolution 2.2.3-2 I have had the really bad idea to check the option "send a d-bus message" (or something similar) in the Evolution receiving mail preferences and now it crashes immediately at every startup giving me this message: ------------ Failed to connect to the D-BUS daemon: Unable to determine the address of the message bus 4949: arguments to dbus_connection_get_data() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 4029. This is normally a bug in some application using the D-BUS library. 4949: arguments to dbus_connection_set_watch_functions() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3320. This is normally a bug in some application using the D-BUS library. ** ERROR **: Not enough memory to set up DBusConnection for use with GLib ------------------------ I cannot uncheck that option since the program crashes immediately; I have looked in my .evolution directory for some preferences file that I could modify to disable that option, but I haven't found nothing. The only way I have found to have evolution working again is to remove the package evolution-plugins, but in this way I am, of course, losing all other plugins. The dbus related packages I have installed are: |/ Name Version Description +++-==============-==============-============================================ ri dbus-1 0.23.4-6 simple interprocess messaging system pn dbus-1-dev <none> (no description available) pn dbus-1-doc <none> (no description available) ii dbus-1-utils 0.23.4-6 simple interprocess messaging system (utilit ri dbus-glib-1 0.23.4-6 simple interprocess messaging system (GLib-b pn dbus-glib-1-de <none> (no description available) ri dbus-qt-1 0.23.4-3 simple interprocess messaging system (Qt-bas pn dbus-qt-1-dev <none> (no description available)
you could do a couple of things. 1. do a make uninstall only in the new-mail-notify plugin directory (evolution/plugins/new-mail-notify) 2. or edit gconf entry in apps->evolution->eplugin->disabled and add/append the id 'org.gnome.evolution.new_mail_notify' and restart evolution. should work.
if you just run with -c contacts on the command line you will be able to run the plugin editor to turn it off. we've fixed any null dereferences and dbus version problems in 2.2.x ages ago, afaik.
this is happenning in evolution 2.2.3 and seems to be caused when the DBUS_SESSION_BUS_ADDRESS and DBUS_SESSION_BUS_PID environment variables are not set. The inteum solution is to make sure you have dbus-lanch installed (in Fedora Core it's in the dbus-x11 package). dbus-launch is usually launched from Xsession along with ssh-agent. (at least on fedora core it is..).
hey edward, are you still facing this issue. The stack trace provided does not suggest much. Also as mentioned in comment #2 most of the probles in the plugin have been fixed. Thanks
Hmm, sounds familiar. Looks like Evo fails hard when dbus simply is not available due to whatever reasons and the dbus plugin is enabled. Evo should fail gracefully, noticing to the user the plugin is not available, and go on. In the case there really is no dbus available. REOPENing.
This is really a setup issue. If dbus is not available, and the user has installed an rpm with this plugin built in and enabled, there is no way we can check if dbus exists before making a call. heck! complications.
Partha, this ain't exactly true. Installing dbus does *not* mean, it definitely will be running. The daemon can be disabled for a lot of reasons. And we can not depend on on packages anyway. Even worse: Any built plugin will be enabled by *default* AFAIK, since the stored settings holds the disabled plugins. There is no way to disable a plugin that is build/installed before starting Evo. (Short of manually messing around with GConf settings...)
i'd like to confirm this.
If anybody has time, could you please check again whether this issue still happens in Evolution 3.2.2 or 3.0.3 and update this report by adding a comment and changing the "Version" field and provide information about your distribution? Thanks a lot.
If D-Bus isn't behaving properly then Evolution won't start. That's just a fact, no way around that. Given that D-Bus is mandatory these days for single-instance detection and communicating with Evolution-Data-Server, I think this should be closed as OBSOLETE.
Closing as per last comment.