Trying bluetooth tethering from Opensuse 12.3 netbook to Nokia N8. Bluetooth browse device is ok. But if I select "DUN" in the window that shows at the end when adding device, a notification showing "Kde workspace: setting up" opens and stays there, without anything after that. In network manager the tab "mobile broadband" is grayed out; nothing else happens. Opensuse 12.3 kde , installed from dvd (almost-clean install) Qt: 4.8.4 KDE Development Platform: 4.10.5 "release 1" bluedevil-1.3-2.1.2.x86_64 plasmoid-networkmanagement-0.**9.0.7-1.1.1.x86_64 Reproducible: Always Steps to Reproduce: 1. Configure bluetooth for a phone 2. Select DUN at the last screen Actual Results: Notification opens, but nothing else happens Expected Results: Software should setup a mobile broadband connection (or another type of connection maybe) in networkmanager, user should be able to just use connection "out of the box"
I have the same issue with kubuntu 13.10, with kde 4.11.2 and bluedevil 1.3.0. If I try to manually invoke bluedevil-network-dun, I get the same result. Namely, the dialog where I should enter my network plan, that used to work in the past, never appears. If I try to strace bluedevil-network-dun, in one of the logs, I see that bluedevil tries to register a dun device (with networkmanager?). In fact, I see an execve with parameters create --type bluetooth --specific-args dun but it is unclear to me what command this execve is trying to call, since there is no command name in the execve call in the trace! Is bluedevil missing something from modemmanager or networkmanager?
Can someone test this with BlueDevil 2.0 and plasma-nm? Thanks!
If you can provide the information requested in comment #2, please add it.
No response, changing status. If you have more information, please add a comment.
My bluedevil (on kubuntu 14.04) is marked as a 2.0 RC1. Working with the plasma nm, it is impossible to connect to the internet with bluetooth dun on a mobile phone. But it is perfectly possible to do so by manually setting up rfcomm and using kppp. So no big issue. In any case, bluetooth dun has been broken for ages (at least on kubuntu), first in the kernel (that was panicing on disconnect, now fixed) then somewhere on the bluedevil and nm and mm side. My feeling is that it would be better to disable it, rather than to ship it broken.
Reopening based on recent comment.
Looks like it is a kernel bug. Things work (sort of) when installing a mainline 3.15.6 kernel in place of the 3.14.something that is provided by ubuntu trusty. I think that the issue is http://lists.openwall.net/linux-kernel/2014/02/10/54. In any case, the problem is that modemmanager fails to see rfcomm0 as a modem, once bluedevil has set it up.
This is already fixed in recent versions of plasma-nm (with Bluez 5). When you pair with device, a Bluetooth network connection is added into available connections in network manager plasmoid where you can connect to it.