Bug#754675: [Pkg-bluetooth-maintainers] Bug#754675: obexd is not started automatically

Hi, 2014-07-18 6:46 GMT+09:00 David Rosca : > 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 m

Bug#754675: obexd is not started automatically

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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#754675: [Pkg-bluetooth-maintainers] Bug#754675: obexd is not started automatically

tags 754675 pending thanks Hi, Thanks for your report. This will fix with next upload. Thanks, Nobuhiro 2014-07-13 21:29 GMT+09:00 David Rosca : > Package: bluez-obexd > Version: 5.21-1~exp0 > Severity: normal > > Dear Maintainer, > > obexd from Bluez5 is not started automatically because it

Bug#754675: obexd is not started automatically

Package: bluez-obexd Version: 5.21-1~exp0 Severity: normal Dear Maintainer, obexd from Bluez5 is not started automatically because it is configued to be started by sestemd in user session. Please use this patch [1] that is used in Gentoo, Fedora and other distros. Thanks [1] http://sources.gent