whoopsie can start before network-manager during boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
whoopsie (Ubuntu) |
Fix Released
|
High
|
Brian Murray | ||
Xenial |
Fix Released
|
High
|
Brian Murray | ||
Zesty |
Fix Released
|
High
|
Brian Murray |
Bug Description
[Impact]
whoopsie can start before network-manager and then will only work when a networking device state changes, however since it started before n-m it should notice the connection come on-line. This is upload is just in case there are some corner cases out there where whoopsie isn't working and uploading the crashes to the Error Tracker.
[Test Case]
1) Boot a system with the old version of whoopsie
2) Run 'systemctl status whoopsie'
3) Observe:
Jul 25 11:07:01 clean-zesty-amd64 systemd[1]: Started crash report submission daemon.
Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Using lock path: /var/lock/
Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Could not get the Network Manager state:
Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] GDBus.Error:
Jul 25 11:07:02 clean-zesty-amd64 whoopsie[446]: [11:07:02] offline
With the version of whoopsie in -proposed you'll see the following:
Jul 25 11:10:33 clean-zesty-amd64 systemd[1]: Started crash report submission daemon.
Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Using lock path: /var/lock/
Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] The default IPv4 route is: /org/freedeskto
Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Not a paid data plan: /org/freedeskto
Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Found usable connection: /org/freedeskto
[Regression Potential]
If whoopsie is working properly when it wasn't, this shouldn't be the case because whoopsie would start working when the network connection changed, then people might be surprised by additional network activity (uploading of crashes) and the Error Tracker may receive more crash reports.
Original 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=
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:
tags: | added: artful |
Changed in whoopsie (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → High |
description: | updated |
Changed in whoopsie (Ubuntu Xenial): | |
assignee: | nobody → Brian Murray (brian-murray) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in whoopsie (Ubuntu Zesty): | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: xenial |
tags: | added: zesty |
Changed in whoopsie (Ubuntu): | |
assignee: | nobody → Brian Murray (brian-murray) |
Changed in whoopsie (Ubuntu Zesty): | |
assignee: | nobody → Brian Murray (brian-murray) |
Changed in whoopsie (Ubuntu): | |
status: | Triaged → In Progress |
Changed in whoopsie (Ubuntu Xenial): | |
status: | Triaged → In Progress |
Changed in whoopsie (Ubuntu Zesty): | |
status: | Triaged → In Progress |
description: | updated |
tags: | added: id-59761bfbcfbdd79f928c8806 |
And I forgot to reference the bug number in the changelog uploaded to Artful.
whoopsie (0.2.58) artful; urgency=medium
* Modify the whoopsie service file to wants=networkin g-online. target too.