Bug 371492

Summary:	Receiving files via bluetooth fails
Product:	[Unmaintained] Bluedevil	Reporter:	Christian (Fuchs) <kde>
Component:	daemon	Assignee:	David Rosca <nowrep>
Status:	RESOLVED UPSTREAM
Severity:	major
Priority:	NOR
Version First Reported In:	5.8.2
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Christian (Fuchs) 2016-10-22 19:01:12 UTC

Receiving files via bluetooth no longer works, both trying to send from my mobile phone (Galaxy S4 with android) and a different Laptop  (KDE Plasma 5.6) sending the file fails

Reproducible: Always

Steps to Reproduce:
1. Try to send a file to plasma desktop with bluedevil


Actual Results:  
Sending the file fails 

Expected Results:  
Sending the file succeeds

It doesn't matter whether the other device is authorized / trusted or not. There is no dialogue to accept / deny the file, and if auto-accept is set to trusted or even all devices, the file is still not accepted. 

The icon in the systray briefly changes and that's it. There are no log entries to be found in the usual places. 

Sending a file from that PC works, also does media control with the very same other device. It is just receiving files that fails.

Bluez:    5.42
Bluez-Qt: 5.27.0
Qt: 5.7.0

Comment 1 David Rosca 2016-10-22 19:05:56 UTC

Is there anything bluetooth related in the syslog? (dmesg / journalctl)

Comment 2 Christian (Fuchs) 2016-10-22 19:11:23 UTC

(In reply to David Rosca from comment #1)
> Is there anything bluetooth related in the syslog? (dmesg / journalctl)

Nothing dmesg, 
journalctl has a couple of 

Okt 22 20:57:00 foxpad bluetoothd[462]: connect error: Host is down (112)

however, this is not triggered by a failed receive (I just tried sending two files and re-opened journalctl, nothing has been added, neither does when I watch it live) 

As said: the icon quickly changes (with the dots left and right of the icon), so something happens, but then silently fails.

Comment 3 David Rosca 2016-10-22 19:13:07 UTC

Is "obexd" running? If not, please try to manually start it and send the file to PC again.

Comment 4 Christian (Fuchs) 2016-10-22 19:20:12 UTC

(In reply to David Rosca from comment #3)
> Is "obexd" running? If not, please try to manually start it and send the
> file to PC again.

fuchs      887  0.0  0.0  80452  6612 ?        S    20:24   0:00 /usr/libexec/bluetooth/obexd

Appears to be running.

When I kill it, it is automatically restarted. When I disable bluetooth integration and restart it, I also don't get any decent debugging information.

Comment 5 David Rosca 2016-10-22 19:32:07 UTC

Alright, so please restart kded5 with debug output enabled for Bluedevil:

kquitapp5 kded5
QT_LOGGING_RULES="bluedevil.debug=true" kded5

After that, make sure bluedevil module is loaded - open Bluetooth settings in KCM and make sure there is no error. You should see in output lines "bluedevil" category. Then try to send a file to PC and upload the whole kded5 output here as attachement.

Comment 6 Christian (Fuchs) 2016-10-22 19:33:39 UTC

Actually, might be a nevermind, 

I just downgraded bluez to 5.39, so a change introduced in bluez seem to be causing the issue. I'll go check if it is a bug there instead of in bluedevil first, in case of it being a bluez one I'll come back. Thanks for the help so far!