touch-packages team mailing list archive

Thread
Date
[Bug 1480116] [NEW] network-manager randomly doesn't start at system start

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Karl-Philipp Richter <krichter722@xxxxxx>
Date: Fri, 31 Jul 2015 06:56:00 -0000
Reply-to: Bug 1480116 <1480116@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Public bug reported:

`sudo systemctl status network-manager.service` shows

    ● NetworkManager.service - Network Manager
       Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
       Active: inactive (dead)

Occurs about 30% of system starts.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu15.1
Uname: Linux 4.1.3-040103-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jul 31 08:49:13 2015
InstallationDate: Installed on 2015-06-08 (52 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
IpRoute:
 default via 192.168.179.1 dev eth2  proto static  metric 1024 
 10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
 169.254.0.0/16 dev eth2  scope link  metric 1000 
 192.168.179.0/24 dev eth2  proto kernel  scope link  src 192.168.179.2
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to vivid on 2015-06-09 (51 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-06-08T14:26:05.824491
nmcli-dev:
 GERÄT  TYP       STATUS           DBUS-PFAD                                  VERBINDUNG                     CON-UUID                              CON-PFAD                                           
 eth2   ethernet  verbunden        /org/freedesktop/NetworkManager/Devices/3  eth2 (second ax88179 adapter)  af2483f2-6748-4e9c-a427-dab37ba09034  /org/freedesktop/NetworkManager/ActiveConnection/0 
 wlan0  wifi      nicht verbunden  /org/freedesktop/NetworkManager/Devices/2  --                             --                                    --                                                 
 eth0   ethernet  nicht verfügbar  /org/freedesktop/NetworkManager/Devices/1  --                             --                                    --                                                 
 lo     loopback  nicht verwaltet  /org/freedesktop/NetworkManager/Devices/0  --                             --                                    --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Fehler: Objekt »nm« ist unbekannt, versuchen Sie »nmcli help«.

** Affects: network-manager (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug vivid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480116

Title:
  network-manager randomly doesn't start at system start

Status in network-manager package in Ubuntu:
  New

Bug description:
  `sudo systemctl status network-manager.service` shows

      ● NetworkManager.service - Network Manager
         Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
         Active: inactive (dead)

  Occurs about 30% of system starts.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  Uname: Linux 4.1.3-040103-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 31 08:49:13 2015
  InstallationDate: Installed on 2015-06-08 (52 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.179.1 dev eth2  proto static  metric 1024 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev eth2  scope link  metric 1000 
   192.168.179.0/24 dev eth2  proto kernel  scope link  src 192.168.179.2
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-06-09 (51 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-06-08T14:26:05.824491
  nmcli-dev:
   GERÄT  TYP       STATUS           DBUS-PFAD                                  VERBINDUNG                     CON-UUID                              CON-PFAD                                           
   eth2   ethernet  verbunden        /org/freedesktop/NetworkManager/Devices/3  eth2 (second ax88179 adapter)  af2483f2-6748-4e9c-a427-dab37ba09034  /org/freedesktop/NetworkManager/ActiveConnection/0 
   wlan0  wifi      nicht verbunden  /org/freedesktop/NetworkManager/Devices/2  --                             --                                    --                                                 
   eth0   ethernet  nicht verfügbar  /org/freedesktop/NetworkManager/Devices/1  --                             --                                    --                                                 
   lo     loopback  nicht verwaltet  /org/freedesktop/NetworkManager/Devices/0  --                             --                                    --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Fehler: Objekt »nm« ist unbekannt, versuchen Sie »nmcli help«.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1480116/+subscriptions