NetworkManager does not always start at boot/first login

Bug #1614393 reported by Andrew
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Syslog says:
Aug 18 17:03:41 <host> whoopsie[1010]: [17:03:41] Could not get the Network Manager state:
Aug 18 17:03:41 <host> whoopsie[1010]: [17:03:41] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files

Sometimes rebooting fixes it. Otherwise, need to run sudo systemctl start network-manager manually.

This is a blocker for Internet access (using wlan0)

Tags: xenial
Revision history for this message
Andrew (am-public-o) wrote :

Further information:

<user>@<host>:~$ sudo apt policy network-manager
network-manager:
  Installed: 1.1.93-0ubuntu4
  Candidate: 1.1.93-0ubuntu4
  Version table:
 *** 1.1.93-0ubuntu4 500
        500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status
<user>@<host>:~$ sudo uname -r
4.4.0-34-generic
<user>@<host>:~$ sudo cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Changed in network-manager (Ubuntu):
importance: Undecided → Critical
importance: Critical → High
Revision history for this message
Andrew (am-public-o) wrote :

Still affected by this bug. No whoopsie but I have attached relevant snippet of kern.log

More info:
$ uname -ra
Linux TOSgeek 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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