Bluetooth transfers fail from Jolla to Jolla.
asked 2015-04-23 21:18:41 +0200
I tried to send a video to another Jolla via BT and first it seemed to go OK. It down-/uploaded about 5% of the file and then just stopped, I got a notification that the file transfer had failed. Tried with another video and got to ~75% and then a failure.
The logs show the following (for the second try):
[root@Jolla nemo]# journalctl -n 500 | grep bluetooth
Apr 23 21:04:40 Jolla kernel: bluetoothd(773) send signal 13 to bluetoothd(773)
Apr 23 21:04:40 Jolla bluetoothd[773]: Stopping discovery
Apr 23 21:05:22 Jolla dbus[476]: [system] Rejected send message, 5 matched rules; type="method_return", sender=":1.13" (uid=0 pid=773 comm="/usr/sbin/bluetoothd -n ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.131" (uid=100000 pid=4107 comm="/usr/libexec/obex-client ")
Apr 23 21:05:30 Jolla bluetoothd[773]: Discovery session 0x41b91ae8 with :1.79 activated
And to be honest, I have no idea what went wrong here, because when I don't have the transfer active the logs are as follows:
[root@Jolla nemo]# journalctl -n 500 | grep bluetooth
Apr 23 21:08:30 Jolla bluetoothd[773]: Discovery session 0x41b91ae8 with :1.79 activated
Apr 23 21:08:30 Jolla kernel: bluetoothd(773) send signal 13 to bluetoothd(773)
Apr 23 21:08:40 Jolla bluetoothd[773]: Stopping discovery
Apr 23 21:08:40 Jolla kernel: bluetoothd(773) send signal 13 to bluetoothd(773)
I tried to send a photo and first got the error message that the transfer failed, with the second try the transfer succeeded, here's the logs:
[root@Jolla nemo]# journalctl -n 500 | grep bluetooth
Apr 23 21:11:47 Jolla bluetoothd[773]: Stopping discovery
Apr 23 21:11:47 Jolla kernel: bluetoothd(773) send signal 13 to bluetoothd(773)
Apr 23 21:11:48 Jolla bluetoothd[773]: Mode session 0x41b91ae8 with :1.131 activated
Apr 23 21:11:48 Jolla kernel: bluetoothd(773) send signal 13 to bluetoothd(773)
Apr 23 21:12:27 Jolla dbus[476]: [system] Rejected send message, 5 matched rules; type="method_return", sender=":1.13" (uid=0 pid=773 comm="/usr/sbin/bluetoothd -n ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.131" (uid=100000 pid=4107 comm="/usr/libexec/obex-client ")
Apr 23 21:12:30 Jolla bluetoothd[773]: Discovery session 0x41b91ae8 with :1.79 activated
Apr 23 21:12:30 Jolla kernel: bluetoothd(773) send signal 13 to bluetoothd(773)
Apr 23 21:12:41 Jolla bluetoothd[773]: Stopping discovery
Apr 23 21:12:41 Jolla kernel: bluetoothd(773) send signal 13 to bluetoothd(773)
Apr 23 21:13:33 Jolla bluetoothd[773]: Discovery session 0x41b91ae8 with :1.79 activated
Apr 23 21:13:33 Jolla kernel: bluetoothd(773) send signal 13 to bluetoothd(773)
Hopefully this gets solved. I tagged this for the latest update, don't know if this has been an issue before (never tried BT transfer). But feel free to edit/update if this problem exists in previous releases as well.
Bluetooth on Sailfish is a mess and a bit of a joke. Every update brings back old problems and connections with various kit is a lottery from one day to another. I'm tired of reporting such problems, to the point where I don't bother to do so any more, as most requests are either attacked or ignored.
Spam Hunter ( 2017-12-13 11:18:09 +0200 )edit@Edz, ack, but sometimes some basic Bluetooth functions appear to be the easiest way (on first sight).
olf ( 2017-12-14 20:30:41 +0200 )editTrue though, that I have to divert to workarounds quite often, too.