** Also affects: whoopsie (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: whoopsie (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: whoopsie (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: whoopsie (Ubuntu Xenial)
Status: New => Triaged
** Changed in: whoopsie (Ubuntu Xenial)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: whoopsie (Ubuntu Zesty)
Status: New => Triaged
** Changed in: whoopsie (Ubuntu Zesty)
Importance: Undecided => High
** Tags added: xenial
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1706195
Title:
whoopsie can start before network-manager during boot
Status in whoopsie package in Ubuntu:
Triaged
Status in whoopsie source package in Xenial:
Triaged
Status in whoopsie source package in Zesty:
Triaged
Bug description:
whoopsie's systemd service file does not start after networking which
is incorrect since it initially needs to query network-manager's
state. A fix was attempted by changing the service file to include
"After=network-online.target" but this was insufficient. The following
messages demonstrate the failure, if whoopsie were to start after
network-manager we would not see them:
Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network
Manager state:
Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47]
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.NetworkManager was not provided by any .service files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1706195/+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
