Ubuntu
dbus package

  1. Bug #592434
  2. Comment #20

Comment 20 for bug 592434

Revision history for this message
In , Colin Walters (walters) wrote :

(In reply to comment #5)
> DISPLAY=:0 some-dbus-command
>
> is very much used. You cannot remove this functionality.

Well, eventually my goal is just

"some-dbus-command" works (this gets back to OS single session).

I agree maintaining DISPLAY= setting for legacy gettys is desirable (I use it myself sometimes), though I don't see such a hard and fast "you cannot remove" rule for random Linux voodoo commands.

The question is - can we come up with a variation that "fixes" the ssh case without changing anything else?

It looks like recent versions of OpenSSH put "SSH_CONNECTION" in the environment; in that case, we could simply not connect to X. We could also check inside dbus-launch for whether the X is remote, and if so ignore it.

However - if it comes down to "do we 'break' getty or do we 'unbreak' ssh", I think the latter really has to win.