desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #83531
[Bug 1371481] Re: Network Manager's Upstart configuration is wrong - Network Manager doesn't start in case of faulty ifupdown configuration
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New => Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
** Changed in: hundredpapercuts
Importance: Undecided => Low
** Changed in: hundredpapercuts
Importance: Low => High
** Changed in: network-manager (Ubuntu)
Importance: Low => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1371481
Title:
Network Manager's Upstart configuration is wrong - Network Manager
doesn't start in case of faulty ifupdown configuration
Status in One Hundred Papercuts:
Confirmed
Status in “network-manager” package in Ubuntu:
Confirmed
Bug description:
Hi everyone,
If you add a faulty entry to ifupdown's configuration
(/etc/network/interfaces or sourced in files) then Network Manager
doesn't get started by Upstart.
As an example add this block for a non-existent network interface to /etc/network/interfaces:
auto bogus0
iface bogus0 inet dhcp
If you reboot your machine then Network Manager won't be started by
Upstart.
The issue with Network Manager's Upstart configuration is that it starts on the following condition:
start on (local-filesystems
and started dbus
and static-network-up)
This is wrong as the static-network-up event is never emitted in case the ifupdown configuration is (partially) invalid.
In order to fix this issue please use the following start on condition:
start on (local-filesystems
and started dbus
and started networking)
This is an issue in all currently supported Ubuntu releases.
Please let me know if you have any further questions.
Best,
Michael Schaller
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1371481/+subscriptions
References