← Back to team overview

desktop-packages team mailing list archive

[Bug 1424664] Re: no ifupdown configuration found


*** This bug is a duplicate of bug 1447146 ***

** Tags added: wily

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.

  no ifupdown configuration found

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  booted with systemd-sysv

  found into syslog:

  NetworkManager[770]: <info> management mode: unmanaged
  NetworkManager[770]: <info> devices added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0/net/eth0, iface: eth0)
  NetworkManager[770]: <info> device added (path: /sys/devices/pci0000:00/0000:00:1c.3/0000:04:00.0/net/eth0, iface: eth0): no ifupdown configuration found.
  NetworkManager[770]: <info> devices added (path: /sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/net/eth1, iface: eth1)
  NetworkManager[770]: <info> device added (path: /sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/net/eth1, iface: eth1): no ifupdown configuration found.
  NetworkManager[770]: <info> devices added (path: /sys/devices/virtual/net/lo, iface: lo)
  NetworkManager[770]: <info> device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
  NetworkManager[770]: <info> end _init.

  NetworkManager[770]: (NetworkManager:770): GLib-CRITICAL **: g_dir_read_name: assertion 'dir != NULL' failed

  NetworkManager[770]: <info> (eth1): link connected
  NetworkManager[770]: <info> (eth1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
  NetworkManager[770]: <info> Auto-activating connection 'Wired connection 1'.
  Feb 23 15:06:39 u32 NetworkManager[770]: <info> Activation (eth1) starting connection 'Wired connection 1'
  NetworkManager[770]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled...
  NetworkManager[770]: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started...
  NetworkManager[770]: <info> (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
  NetworkManager[770]: <info> NetworkManager state is now CONNECTING

  note: only eth1 is used to get stream; so it looks like a race as
  networkmanager seems working as expected; but what a confusing
  process: do really need a better design, because that one is a real

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager
  ProcVersionSignature: Ubuntu 3.19.0-6.6-generic 3.19.0
  Uname: Linux 3.19.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Feb 23 15:45:26 2015
   default via dev eth1  proto static  metric 1024 dev eth1  scope link  metric 1000 dev eth1  proto kernel  scope link  src
   lo        no wireless extensions.

   eth0      no wireless extensions.

   eth1      no wireless extensions.

  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
   NAME                UUID                                  TYPE            TIMESTAMP   TIMESTAMP-REAL                   AUTOCONNECT  READONLY  DBUS-PATH                                   ACTIVE  DEVICE  STATE      ACTIVE-PATH
   Wired connection 1  7086b2ff-1446-45fe-b8f3-cd333cd4cee1  802-3-ethernet  1424702496  lun. 23 févr. 2015 15:41:36 CET  yes          no        /org/freedesktop/NetworkManager/Settings/0  yes     eth1    activated  /org/freedesktop/NetworkManager/ActiveConnection/0
   DEVICE  TYPE      STATE        DBUS-PATH                                  CONNECTION          CON-UUID                              CON-PATH
   eth1    ethernet  connected    /org/freedesktop/NetworkManager/Devices/2  Wired connection 1  7086b2ff-1446-45fe-b8f3-cd333cd4cee1  /org/freedesktop/NetworkManager/ActiveConnection/0
   eth0    ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --                  --                                    --
   lo      loopback  unmanaged    /org/freedesktop/NetworkManager/Devices/0  --                  --                                    --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to: