blueman-sendto crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.obex.service not found.

[amos koh]

ubuntu 17.10

problem 1 :
difficult to connect to bluetooth device (a speaker with no pin number required,
pin number should be 0000 )
connection to this bluetooth speaker seemed to depend on luck.

problem 2 :
even when connected , the device is not shown in the "Device" box.

problem 3:
if i do managed to connect to my smartphone
i am unable to send file from laptop to the smart phone.

what i had doen :
uninstall bluetooth , blueman
re-install bluetooth and blueman.
installed apache2 , libapache2-mod-dnssd

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: blueman 2.0.4-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity:Unity7
Date: Fri Jun 2 12:51:14 2017
ExecutablePath: /usr/bin/blueman-sendto
InstallationDate: Installed on 2017-05-23 (10 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InterpreterPath: /usr/bin/python3.5
ProcCmdline: /usr/bin/python3 /usr/bin/blueman-sendto --source=DC:85:DE:92:22:82 --device=68:3E:34:E4:F6:B2
PythonArgs: ['/usr/bin/blueman-sendto', '--source=DC:85:DE:92:22:82', '--device=68:3E:34:E4:F6:B2']
SourcePackage: blueman
Title: blueman-sendto crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.obex.service not found.
UpgradeStatus: Upgraded to artful on 2017-05-25 (8 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1672794, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.