Hello, It wasn't previously, and I don't think it should be, necesary to read the user's Evolution contacts in order to receive a file from a local bluetooth peer (my understanding is that a file-receive operation requires an explicit approval in the GNOME bluetooth settings and blueman interfaces, unless the peer has already been marked as trusted).
I'm not certain when the runtime dependency (regardless of Debian package dependency markers) on Evolution became effectively required, but I think that the following commit that landed in bluez upstream in July Y2021, first included in release v5.61, may be when the behaviour changed: https://github.com/bluez/bluez/commit/bdeaad3fa02825e32f2fb52ba2fee0dece856f60 I'd like to suggest considering this bug for re-opening, and to mention it to the PkgPrivacyMaintainers[1] team. I have not found time yet, but I think it would be feasible to adjust the error handling and/or phonebook-ebook service code so that a failure to find or start the contactbook service does not prevent obexd from advertising the Object Push Profile. Regards, James [1] - https://wiki.debian.org/Teams/PkgPrivacyMaintainers
