https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1518681
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442044
Title:
Ordering processes: networkmanager should wait for kernel'module
i still get this bug
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442044
Title:
Ordering processes: networkmanager should wait for kernel'module been
activated first before
This is fixed into Wily
** Changed in: network-manager (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: hundredpapercuts
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1451797 ***
https://bugs.launchpad.net/bugs/1451797
** This bug has been marked a duplicate of bug 1451797
rc.local should require network-online.target
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** This bug is no longer a duplicate of bug 1451797
rc.local should require network-online.target
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442044
Title:
Ordering processes: networkmanager
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New = Confirmed
** Changed in: network-manager (Ubuntu)
Importance: Undecided = Medium
** Changed in: hundredpapercuts
Importance: Undecided = Medium
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442044
@Martin
what i'm reporting is only about the boot logic: if a process needs
first a kernel'module activation, then it might be checked, even if it
'come go' like networkmanager.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: systemd (Ubuntu) = network-manager (Ubuntu)
** Changed in: network-manager (Ubuntu)
Status: Invalid = New
** Description changed:
Get that journalctl log showing networkmanager starting before the
related kernel'module been ready:
-
systemd[1]: Starting
** Summary changed:
- Ordering processes: networkmanager should wait for kernel'module activated
first before starting
+ Ordering processes: networkmanager should wait for kernel'module been
activated first before starting
--
You received this bug notification because you are a member of
Network devices come and go, some are hotpluggable, some have
killswitches, etc. There is no such concept as wait for all network
devices to be present. NetworkManager listens to uevents and can handle
appearing and disappearing network interfaces just fine.
If that doesn't work for a particular
11 matches
Mail list logo
