DBUS_SESSION_BUS_ADDRESS about krun HOT 8 OPEN

dbus-launch sets it.

from krun.

The VM can't access the system's dbus. We could implement a unixsock proxy using vsock, but we'd need a strong justification for doing that. How's Steam using it? Is there a fallback behavior if it's not present?

from krun.

Not sure what Steam is using it for. There's a fallback but before that it's noisy in the log. Simply installing dbus-x11 silences it.

If that works around the issue, it'd be a good idea to make the package (once we get to it) to depend on it.

from krun.

Oh, I see... But apps inside the VM would not be able to talk to services on the host's session bus, right?

from krun.

dbus-launch isn't installed per default on fedora, dbus-x11 needs to be installed to get dbus-launch.

from krun.

If I run dbus-launch it sets DBUS_SESSION_BUS_ADDRESS to something different than it was before. (originally it was unix:path=/run/user/1000/bus dbus-launch sets it to something like unix:path=/tmp/dbus-CB34ABmjaq,guid=2b0f4a14646900e5ac3fd40366470d34 but it does not export DBUS_SESSION_BUS_ADDRESS)

from krun.

Not sure what Steam is using it for. There's a fallback but before that it's noisy in the log. Simply installing dbus-x11 silences it.

from krun.

Yeah, will try to raise this with RPM Fusion. I think it should be considered a packaging bug.

from krun.