[Bug 495972] Re: Network interfaces are not loaded by init if NetworkManager is not installed before dist-upgrade

[Tim]

Cleaning out old reports.  Please file a new one if this is still a problem in a current release.  Thanks.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

** Changed in: update-manager (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/495972

Title:
  Network interfaces are not loaded by init if NetworkManager is not
  installed before dist-upgrade

Status in “update-manager” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: update-manager

  I performed a dist-upgrade from 8.10 to 9.04, then immediately to
  9.10.  Logs are attached.

  In my configuration with 8.10, I did not use Network Manager.  I had a
  manually configured static IP address in /etc/network/interfaces, and
  this was loaded normally on boot.

  After the upgrade to 9.10, the init symlinks to /etc/init.d/networking
  were missing from the folders /etc/rc1.d, /etc/rc2.d, /etc/rc2.d,
  /etc/rc3.d, /etc/rc4.d, and /etc/rc5.d.  Since there were no symlinks
  to /etc/init.d/networking in any of the startup init profiles, the
  network interfaces were never activated upon booting.  I believe this
  error occurred on the transition from 9.04 to 9.10, because I did not
  have to do anything special to activate the network adapters when
  performing the dist-upgrade from 9.04.

  The /etc/networking/interfaces file remained intact, and the
  /etc/init.d/networking script behaved properly when I executed the
  command "/etc/init.d/networking start".  Also, manually starting the
  interface using "ifup eth0" also worked.

  I did not want to install NetworkManager, and it should not be
  required.  Others have suggested removing NetworkManager to use a
  static IP, as in this forum post:
  http://ubuntuforums.org/showthread.php?t=1309835

  Strangely, there was a symlink to /etc/init.d/networking located in
  "/etc/rc6.d/S35networking" and "/etc/rc0.d/S35networking".  However,
  these would only be run during "init 0" or "init 6", which are halt
  and reboot, respectively.  I made a new symlink to
  /etc/init.d/networking in the folders /etc/rc1.d, /etc/rc2.d,
  /etc/rc2.d, /etc/rc3.d, /etc/rc4.d, and /etc/rc5.d, and named it
  "S28networking".  Hopefully the system will now start networking
  properly at boot time.

  Here is my current directory listing for these files:

  $ sudo find /etc/|grep networking
  /etc/rc0.d/S35networking
  /etc/rc1.d/S28networking
  /etc/rc2.d/S28networking
  /etc/rc3.d/S28networking
  /etc/rc4.d/S28networking
  /etc/rc5.d/S28networking
  /etc/rc6.d/S35networking
  /etc/init.d/networking
  /etc/init/networking.conf

  ProblemType: Bug
  Architecture: i386
  Date: Sat Dec 12 11:07:17 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: update-manager 1:0.126.9
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
  SourcePackage: update-manager
  Uname: Linux 2.6.31-16-generic i686
  XsessionErrors:
   (gnome-settings-daemon:2714): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
   (gnome-settings-daemon:2714): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
   (polkit-gnome-authentication-agent-1:2827): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:2820): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

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