Ubuntu
network-manager package

Suspend to RAM with active bluetooth network connection causes problems

Bug #1666125 reported by PeterPall on 2017-02-20

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	network-manager (Ubuntu)	New	Undecided	Unassigned

Bug Description

If I close my coputer while it is connected to my phone's network via bluetooth after resuming all of the following might happen
- Everything works right and i can re-connect to my bluetooth network using the network-manager-gnome icon
- Bluetooth network can still be used but network-manager seems to forget about my WiFi
- Bluetooth network can still be used and network-manager offers to connect to the WiFi stations that were there before suspending. But it doesn't scan for new ones
- Network works. But /etc/resolv.conf points to 127.0.0.0 and hosts cannot be resolved until I replace this number by a working nameserver
- Network works. But dnsmasq no more reacts
- Network no more works including my loopback network => even a poweroff command cannot shut down my computer.

If any problems exist a sudo service network-manager restart normally breaks my loopback network. No idea why.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager 1.4.4-1ubuntu2
Uname: Linux 4.10.0-041000-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon Feb 20 08:23:59 2017
EcryptfsInUse: Yes
IpRoute:
default via 192.168.44.1 dev bnep0 proto static metric 750
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown
192.168.44.0/24 dev bnep0 proto kernel scope link src 192.168.44.140 metric 750
NetworkManager.conf:
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
running 1.4.4 connected started full enabled enabled enabled enabled enabled

Tags:

Revision history for this message

PeterPall (peterpall) wrote on 2017-02-20:

CRDA.txt Edit (426 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (8.3 KiB, text/plain; charset="utf-8")
IfupdownConfig.txt Edit (151 bytes, text/plain; charset="utf-8")
IpAddr.txt Edit (1.1 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (283 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (16.7 KiB, text/plain; charset="utf-8")
NetDevice.bnep0.txt Edit (1.1 KiB, text/plain; charset="utf-8")
NetDevice.lo.txt Edit (248 bytes, text/plain; charset="utf-8")
NetDevice.lxcbr0.txt Edit (372 bytes, text/plain; charset="utf-8")
NetDevice.wlan0.txt Edit (885 bytes, text/plain; charset="utf-8")
PciNetwork.txt Edit (668 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (322 bytes, text/plain; charset="utf-8")
RfKill.txt Edit (179 bytes, text/plain; charset="utf-8")
WifiSyslog.txt Edit (90.7 KiB, text/plain; charset="utf-8")
nmcli-con.txt Edit (12.5 KiB, text/plain; charset="utf-8")
nmcli-dev.txt Edit (1.5 KiB, text/plain; charset="utf-8")

Revision history for this message

PeterPall (peterpall) wrote on 2017-03-01:

Weird:
a

sudo dhclient

resolves the network problem in most of the cases.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntunetwork-manager package