Network manager fails to find bluetooth 'modem' for dun connection in saucy and trusty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
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/NetworkMan
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[
Mar 31 20:44:00 zagar NetworkManager[
Mar 31 20:44:00 zagar NetworkManager[
Mar 31 20:44:00 zagar NetworkManager[
Mar 31 20:44:00 zagar NetworkManager[
Mar 31 20:44:00 zagar NetworkManager[
Mar 31 20:44:00 zagar NetworkManager[
Mar 31 20:44:00 zagar NetworkManager[
Mar 31 20:44:00 zagar NetworkManager[
Mar 31 20:44:05 zagar NetworkManager[
Mar 31 20:44:05 zagar NetworkManager[
Mar 31 20:44:36 zagar NetworkManager[
Mar 31 20:44:36 zagar NetworkManager[
Mar 31 20:44:36 zagar NetworkManager[
Mar 31 20:44:36 zagar NetworkManager[
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
ProcVersionSign
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.
[main]
NetworkingEnab
WirelessEnable
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/freedeskto
eth1 802-3-ethernet connected /org/freedeskto
wlan0 802-11-wireless disconnected /org/freedeskto
eth0 802-3-ethernet unavailable /org/freedeskto
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/
/dev/snd/
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=
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=
ProcVersionSign
RelatedPackageV
linux-
linux-
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.
dmi.board.name: W740SU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: W740SU
dmi.product.
dmi.sys.vendor: Notebook
affects: | linux-meta (Ubuntu) → linux (Ubuntu) |
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.