Public bug reported:
mediatomb fails to start at boot because the network is not yet up.
It's unit file lists After: network-online.target, but this target comes
up before NetworkManager has brought the network up. I'm guessing it
only counts networks configured in /etc/interfaces.
** Affects: mediatomb (Ubuntu)
Importance: Undecided
Status: New
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1453602
Title:
mediatomb fails to start at boot
Status in mediatomb package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
mediatomb fails to start at boot because the network is not yet up.
It's unit file lists After: network-online.target, but this target
comes up before NetworkManager has brought the network up. I'm
guessing it only counts networks configured in /etc/interfaces.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediatomb/+bug/1453602/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
