Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty

[Sergio Callegari]

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
---
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: callegar 2789 F.... pulseaudio
                      callegar 3227 F.... pulseaudio
 /dev/snd/controlC0: callegar 2789 F.... pulseaudio
                      callegar 3227 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=c7dd5aac-abad-4cd0-9cac-552d49960853
InstallationDate: Installed on 2013-12-12 (242 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Notebook W740SU
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-33-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_hd-vg/swap_1 acpi_backlight=vendor vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-33-generic N/A
 linux-backports-modules-3.13.0-33-generic N/A
 linux-firmware 1.127.5
Tags: trusty
Uname: Linux 3.13.0-33-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-05-06 (98 days ago)
UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo vboxusers video
_MarkForUpload: True
dmi.bios.date: 10/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W740SU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: W740SU
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

[Sergio Callegari (callegar)]

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.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1300386

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Sergio Callegari (callegar)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.6-trusty/

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[lkalev (lkalev)]

In response to comment#20, I can confirm that that connection is possible with a kernel downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17.4-vivid/linux-image-3.17.4-031704-generic_3.17.4-031704.201411211317_i386.deb.

This was tested on Ubuntu 14.04 (Xubuntu).

Note I used a manually created NetworkManager configuration file stored in /etc/NetworkManager/system-connections. Connecting from the Blueman control panel does not work (says "NetworkManager did not support the connection").