You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ cat ~/.local/share/dbus-1/services/com.github.amezin.false.service
[D-BUS Service]
Name=com.github.amezin.false
Exec=false
$ dbus-send --session --dest=org.freedesktop.DBus --print-reply --reply-timeout=120000 /org/freedesktop/DBus org.freedesktop.DBus.StartServiceByName string:'com.github.amezin.false' uint32:0
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
While, obviously, the service fails (almost) immediately.
In journal:
Created slice Slice /app/dbus-:1.2-com.github.amezin.false.
Started dbus-:[email protected].
dbus-:[email protected]: Main process exited, code=exited, status=1/FAILURE
dbus-:[email protected]: Failed with result 'exit-code'.
And it seems that activation won't be attempted again until dbus-broker is restarted. So, if there was some issue with, for example, service configuration, or missing dependencies, after fixing it I'll have to log out and login again - for session bus, or restart the system completely - for system bus.
The text was updated successfully, but these errors were encountered:
While, obviously, the service fails (almost) immediately.
In journal:
And it seems that activation won't be attempted again until dbus-broker is restarted. So, if there was some issue with, for example, service configuration, or missing dependencies, after fixing it I'll have to log out and login again - for session bus, or restart the system completely - for system bus.
The text was updated successfully, but these errors were encountered: