Same issue in trusty. This is in fact a kernel bug: see https://lkml.org/lkml/2014/2/9/316.
Tried mainline (e.g. 3.15.6) and works fine. There is also another bug in modemmanager/networkmanager. This keeps rfcomm0 open when the connection is dropped and causes modemmanager to keep asking the bluetooth phone about the signal quality. When you try to connect again, the connection fails. However, this is easily worked around by "service modemmanager restart". So the main issue is with the kernel. The relevant patches should be backported to the saucy and trusty kernels. ** Summary changed: - Network manager fails to find bluetooth 'modem' for dun connection in saucy + Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty ** Package changed: network-manager (Ubuntu) => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1300386 Title: Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty Status in “linux-meta” package in Ubuntu: New Bug description: Working on kubuntu saucy 64bit. Trying to connect to the internet via an UMTS phone that is DUN capable over bluetooth (Samsung galaxy) Setting up things manually, i.e. bring up rfcomm via rfcomm command use kppp to connect the phone can provide internet access just fine. Trying to do the same with network-manager does not work. I have the profile set up in a file in /etc/NetworkManager/system- connections/ when I try to connect, things start just fine. Connection confirmation is asked on the phone and the rfcomm interface is brought up. However, network manager says that it fails to find the modem. In syslog I get: Mar 31 20:44:00 zagar NetworkManager[1149]: <info> Activation (6C:83:36:31:D9:FE) starting connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:00 zagar NetworkManager[1149]: <info> (6C:83:36:31:D9:FE): device state change: disconnected -> prepare (reason 'none') [30 40 0] Mar 31 20:44:00 zagar NetworkManager[1149]: <info> Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: <info> Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) started... Mar 31 20:44:00 zagar NetworkManager[1149]: <info> Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) scheduled... Mar 31 20:44:00 zagar NetworkManager[1149]: <info> Activation (6C:83:36:31:D9:FE) Stage 1 of 5 (Device Prepare) complete. Mar 31 20:44:00 zagar NetworkManager[1149]: <info> Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) starting... Mar 31 20:44:00 zagar NetworkManager[1149]: <info> (6C:83:36:31:D9:FE): device state change: prepare -> config (reason 'none') [40 50 0] Mar 31 20:44:00 zagar NetworkManager[1149]: <info> Activation (6C:83:36:31:D9:FE) Stage 2 of 5 (Device Configure) complete. Mar 31 20:44:05 zagar NetworkManager[1149]: <info> Activation (6C:83:36:31:D9:FE 6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) successful. Will connect via DUN. Mar 31 20:44:05 zagar NetworkManager[1149]: <info> Activation (6C:83:36:31:D9:FE/bluetooth) Stage 2 of 5 (Device Configure) waiting for modem to appear. Mar 31 20:44:36 zagar NetworkManager[1149]: <info> (6C:83:36:31:D9:FE): device state change: config -> failed (reason 'modem-not-found') [50 120 43] Mar 31 20:44:36 zagar NetworkManager[1149]: <warn> Activation (6C:83:36:31:D9:FE) failed for connection 'TIM Maxxi Alice/Internet' Mar 31 20:44:36 zagar NetworkManager[1149]: <info> (6C:83:36:31:D9:FE): device state change: failed -> disconnected (reason 'none') [120 30 0] Mar 31 20:44:36 zagar NetworkManager[1149]: <info> (6C:83:36:31:D9:FE): deactivating device (reason 'none') [0] Note that after the 'device configure' phase, giving the rfcomm command on the console shows the rfcomm interface up and alive. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 31 20:48:29 2014 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-12 (108 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 10.143.1.254 dev eth1 proto static 10.143.0.0/19 dev eth1 proto kernel scope link src 10.143.20.139 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH 6C:83:36:31:D9:FE bluetooth disconnected /org/freedesktop/NetworkManager/Devices/9 eth1 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/7 wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/2 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 nmcli-nm: RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0 connected enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1300386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
