Trying to revive 'ubtd' (Bluetooth file transfer)
-
@gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):
For now, I have only one positive thing to say: in the application that worked with 16.04, the template was set to 'unconfined'; while this is not generally a great idea, to advance your testing maybe it could be worth a try to add it to the apparmor profile ?
Yes, you're right -- it's certainly worth a try.
-
Well, good news! With the "unconfined" AA profile, the app works

The phone successfully received a
.jpegfile sent over BT from my laptop:
-
Great ! have happy file exchanges with your car

-
@PhAndersson said in Trying to revive 'ubtd' (Bluetooth file transfer):
Well, good news! With the "unconfined" AA profile, the app works

The phone successfully received a
.jpegfile sent over BT from my laptop:
Congrats, So some changes are needed on UT to make it work ?
-
@gpatel-fr said in Trying to revive 'ubtd' (Bluetooth file transfer):
Great ! have happy file exchanges with your car

That won't work yet, unfortunately. For this, I need the SharePlugin to work. That one still crashes as soon as I select it which causes the phone to restart.
More troubleshooting needed

-
@lduboeuf said in Trying to revive 'ubtd' (Bluetooth file transfer):
Congrats, So some changes are needed on UT to make it work ?
If your question is: did I need to hack my phone to make the app work in its current state, then the answer is no. As suggested by @gpatel-fr, I just gave it an "unconfined" AA profile (which I understand would prevent me from publishing it on the OpenStore).
So eventually an updated
bluetoothAppArmor Policy Group would be needed, I guess (or a extra one dedicated to OBEX). -
@PhAndersson I think any spawning of external processes that are not inside the app's
~/.local/sharedirectory require unconfined. And in this case, unconfined would be required since it's using some system executable.