Comment 3 for bug 1697375
Revision history for this message
| Brian Murray (brian-murray) wrote Re: crash reports are not uploaded automatically | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
On boot in artful whoopsie works for me, I think because whoopsie is started before networking and then network-manager's state changes and then whoopsie is able to connect. Here I started whoopsie, took an interface offline and then brought it online.
ul 14 14:25:25 speedy whoopsie[13673]: [14:25:25] Could not get the Network Manager state:
Jul 14 14:25:25 speedy whoopsie[13673]: [14:25:25] GDBus.Error:
Jul 14 14:25:35 speedy whoopsie[13673]: [14:25:35] offline
Jul 14 14:25:35 speedy whoopsie[13673]: [14:25:35] Cannot reach: https:/
Jul 14 14:25:35 speedy whoopsie[13673]: [14:25:35] Cannot reach: https:/
Jul 14 14:25:43 speedy whoopsie[13673]: [14:25:43] Cannot reach: https:/
Jul 14 14:25:43 speedy whoopsie[13673]: [14:25:43] The default IPv4 route is: /org/freedeskto
Jul 14 14:25:43 speedy whoopsie[13673]: [14:25:43] Not a paid data plan: /org/freedeskto
Jul 14 14:25:43 speedy whoopsie[13673]: [14:25:43] Found usable connection: /org/freedeskto
Jul 14 14:25:44 speedy whoopsie[13673]: [14:25:44] online
Additionally, if I try to start whoopsie manually when I am already online it fails.
Jul 14 14:48:09 speedy systemd[1]: Started crash report submission daemon.
Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Using lock path: /var/lock/
Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Could not get the Network Manager state:
Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] GDBus.Error:
I also noticed the same behavior on Ubuntu 17.04.