This is an issue we are hitting in Gentoo for a long time: https://bugs.gentoo.org/show_bug.cgi?id=577842 Only when dbus is compiled with user-session support. It seems ArchLinux is also suffering this bug: https://bugs.archlinux.org/task/45816 In summary, if we don't manually do this link: ln -fs /usr/lib/systemd/user/obex.service /usr/lib/systemd/user/dbus- org.bluez.obex.service systemd cannot launch obexd when needed and, hence, sending files fails silently (as opposed to dbus without user-session, that was able to launch obexd when needed). Then, I am not sure if this link should be provided always or if we have something missing in bluez.service file that, even enabling it, is not enough for "fully" enabling bluetooth (as it seems obexd is not handled at all) Thanks a lot for your help -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
