Control: close 950520 Control: fixed 950520 2.1.3-1
I'm not sure if moving '/usr/lib/systemd/user/blueman-applet.service' to '/lib/systemd/user/blueman-applet.service' is the correct solution here.
No, it's not. It caused #961215 and is thus reverted in 2.1.3-2.
According to the systemd.unit(5) man [1], the user unit search path contains '/usr/lib/systemd/user/*' but it doesn't contain '/lib/systemd/user/*'.
The user unit dir gets prefixed with the configured prefix, so it's /usr/lib/systemd/user in Debian.
It is worth noting, that according to the manual, '/lib/systemd/system' seems to be correct location for 'shipped blueman-mechanism.service' (as '/lib/systemd/system/*' is in system unit search path, while '/usr/lib/systemd/system/' is not).
The system unit dir gets prefixed with the rootprefix which defaults to / in split /usr systems, so it's /lib/systemd/system in Debian.
However, systemd always looks into /usr/lib/systemd/system (and other paths, like /usr/local/lib/systemd/system) as well, so the installation path was not a problem.
