GNOME Bugzilla – Bug 528912
Screws up DBUS for launched web browsers
Last modified: 2008-04-19 17:04:31 UTC
When clicking on a web link contained in a note, I get the message: Epiphany could not connect to the session message bus. Your default settings will not be available. Epiphany then opens up and behaves as if it was launched with 'epiphany - -p'--that is, no settings/cookies/bookmarks/history are loaded or saved.
What happens when you click on a link in an Evolution email, or in any other programs? What do you have listed as your preferred browser command in the Preferred Applications under the Internet tab? What distro are you on? I cannot reproduce this on openSUSE 10.3. I'm going to close this because we use the standard gnome_url_show to open our links, so I don't really see any way that your problem could be caused by Tomboy.
The preferred web browser is 'gnome-www-browser %"' which is a symlink to epiphany. I replaced the symlink by a shell script that runs 'env' and then execs epiphany-browser and observed the same behaviour. Looking at the output I could see that the browser was being launched with a different DBUS_SESSION_ADDRESS in its environment. I also set the preferred application to epiphany directly, and observed the same behaviour.
I created a minimal program to test whther the problem is in gnome-sharp: class Gus{ public static int Main () { Gnome.Url.Show ("http://foo.com/"); return 0; } } and it works fine. I did some more investigation and saw with the aid of 'ps eww' that tomboy is runnign with a DBUS_SESSION_BUS_ADDRESS different to that of the rest of my session; unix:abstract=/tmp/dbus-rOBwJ8l5gn,guid=aac6721f321d694eb03665a74808cb77 as opposed to unix:abstract=/tmp/dbus-qZXxv4ad80,guid=50a99f53c58c1fb7755308e34808cc72. And netstat says there is nothing listening on the address that tomboy is using.
Well that's odd. Thanks for reopening. What distro are you using?
Sorry, I should have said I'm using Debian testing/unstable. I'm now no longer convinced this is a Tomboy problem. I can't see what in tomboy would change the value of DBUS_SESSION_BUS_ADDRESS, and after I logged out and in again I could no longer reproduce the problem. I will re-open this if I can reproduce it again and track the source of the bug down to tomboy. :)