somehow it got fixed with-> "dbus-launch systemctl --user"
for some reason that did something and I now just use "systemctl --user"
(even after a reboot)
I'm able to see user-specific unit files I created in
~/.config/systemd/user , so I know I am really looking at the user
context entries..
somehow it got fixed with-> "dbus-launch systemctl --user"
for some reason that did something and I now just use "systemctl --user"
(even after a reboot)
I'm able to see user-specific unit files I created in
~/.config/systemd/user , so I know I am really looking at the user
context entries..
Am 27.11.19 um 11:47 schrieb westlake:
> ^ "systemctl --user" is still used by many users and this user-context
> requires "org.freedesktop.systemd1.service"
No, systemctl requires the org.freedesktop.systemd1 D-Bus interface.
This D-Bus interface is provided by the systemd --user instance that is
Am 27.11.19 um 11:47 schrieb westlake:
> Bugreport relayed to the dbus package, immediately closes bug with the
> following response,
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945561
> ""
> Even if systemd --user was suitable for being started by a D-Bus service
> file org.freedesktop.sys
Bugreport relayed to the dbus package, immediately closes bug with the
following response,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945561
""
Even if systemd --user was suitable for being started by a D-Bus service
file org.freedesktop.systemd1.service, it would be systemd (not dbus)
tha
Package: systemd
Version: 242-8~bpo10
Severity: important
listing the contents of systemd_242-8~bpo10+1_amd64.deb shows that
org.freedesktop.systemd1.service is missing from this package
please add this service file as it is needed for systemctl --user commands
thanks
6 matches
Mail list logo
