Linda Walsh <suse@tlinx.org> schreef:
You got it!
Even though I am logged in over a network, I have yet to be able to get the dbus running on my desktop to talk to the dbus that I'm 'ssh'ed into. I.e. the dbus running on the suse linux machine doesn't work for anything, since it doesn't talk to the 'dbus' running on my desktop machine.
Linda, can you or anyone please explain to me what the deal is about dbus anyway? I have this slight impression that the architecture of it is broken although I have never looked into it. It is flouted as a "simple interprocess communication framework" but at the same time I rather despise everything uses it. For instance, what I've found from experience is that some programs may take a long time to start up because in the background there is DBUS activity going on, trying to catch up to something or anything. For instance just firing up KWrite from a konsole would give me all sorts of dbus messages related to /NetworkManager/ of all things. That is just a severely broken architecture. Something like that should never ever happen in any system that just features an IPC channel for applications. I feel that if I *were* to look into it I would pretty quickly discover what I so disagree with, or what so disagrees with me. I'm pretty good at software architecture you know, but so are you (I think). Instead of being a "caller in the desert" I feel perhaps you might be someone who has a thought on this? Regards, xx, Bart. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org