[Pkg-bluetooth-maintainers] Bug#754675: Bug#754675: obexd is not started automatically
Nobuhiro Iwamatsu
iwamatsu at nigauri.org
Tue Jul 22 05:27:49 UTC 2014
Hi,
2014-07-18 6:46 GMT+09:00 David Rosca <nowrep at gmail.com>:
> Hi,
> there is now new problem.
> We now have user session in systemd (208), but obexd still can't be started:
>
> $ systemctl --user start obex
> Failed to issue method call: Unit dbus.socket failed to load: No such
> file or directory.
>
Yes, user must prepare a configuration file for dbus.
-- /etc/systemd/user/dbus.socket
[Unit]
Description=D-Bus Message Bus Socket
Before=sockets.target
[Socket]
ListenStream=/run/user/%U/dbus/user_bus_socket
[Install]
WantedBy=default.target
-- /etc/systemd/user/dbus.service
[Unit]
Description=D-Bus Message Bus
Requires=dbus.socket
[Service]
ExecStart=/usr/bin/dbus-daemon --session --address=systemd: --nofork
--nopidfile --systemd-activation
ExecReload=/usr/bin/dbus-send --print-reply --session
--type=method_call --dest=org.freedesktop.DBus /
org.freedesktop.DBus.ReloadConfig
And execute "sudo systemctl --global enable dbus.socket"
I think not intended to be prepared in bluez, these files as something
to be prepared in systemd package.
I will ask to systemd maintainer.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
More information about the Pkg-bluetooth-maintainers
mailing list