D-Bus User Bus

Havoc Pennington hp at pobox.com
Wed May 19 19:44:02 PDT 2010


On Wed, May 19, 2010 at 10:37 PM, Lennart Poettering <mzqohf at 0pointer.de> wrote:
> Let's not forget that gdm currently makes it impossible to login twice
> as the same user.

gah! doesn't that mean that the _only_ way to get two sessions per
homedir is network homedir?
So what is the point of this whole user bus thing if you've already
declared one session per user per machine to be the policy, the
session bus is effectively already what you want...

Is this just a fix for ssh sessions? What thing in an ssh session
wants to use the bus anyhow?

If the issue is running graphical stuff from ssh and you have said one
graphical session per user, then have the one graphical session
register DBUS_SESSION_BUS_ADDRESS somewhere systemwide (maybe on a
system bus service that just does that), and have a cheesy command
line app to fetch DBUS_SESSION_BUS_ADDRESS. Run in your login script
for ssh. All ssh sessions now have access to your graphical session's
bus. Done.

Or something, I don't know. But surely there's a simpler fix for
whatever we want to do in an ssh session, than breaking the crap out
of the whole desktop. :-P


More information about the dbus mailing list