Simon McVittie

@flibitijibibo: feel free to take over #3325 if it would be useful to you, I'm unlikely to have much time to work on it any time soon.

I tried packaging DXVK for Debian and the Steam Runtime, and didn't notice any remaining showstopper issues with the libraries. #4025 should be resolved at some point, but isn't a...

Hi, I'm a Steam Runtime developer (but I am not able to do what you request in https://github.com/ValveSoftware/steam-runtime/issues/654, someone from Valve will have to handle that for you). I'm glad...

Am I right in thinking that for services with `SystemdService=foo.service`, dbus-broker will start the systemd service named `foo.service` (the same as dbus-daemon does), with transient units only used for services...

> I would mostly see this as an effort to make the naming scheme of dbus-broker API Wouldn't that mean that adding a `SystemdService=fooapp.service` to an existing session service would...

> now add SystemdService=fooapp.service Or is the intention that this is deprecated, and if anything with an app-ID is installing a user-service, it should be named like `/usr/lib/systemd/user/app-com.example.FooApp.service` and therefore...

> This doesn't solve the issue with systemd services, does it? Even if the dbus service file contains the appid, if the systemd service name will always be whatever the...

> Why do you prefer to add another key to the systemd service file instead of renaming the file according to the systemd naming convention? I don't prefer it, exactly,...

> I would expect an application to check the dbus-activation-file and decide based on the presence of SystemdService= how to react This seems odd to me: usually D-Bus service files...

> I can write patch if you want If you think you know how to solve this, please do: reviewing a pull request and checking for things that can go...