Changing the upstart job to have it start/stop with dbus does not work for me. It still thinks it's not online and I get messages like this in syslog:
Jul 22 16:18:06 ubuntu-phablet whoopsie[850]: Not online; processing later (/var/crash/_usr_lib_arm-linux-gnueabihf_url-dispatcher_update-directory.32011.crash)
If I instead have it start/stop with network-manager, I don't get the messages about it being offline. However it does seem like it gets stuck, or it's waiting on some lock in whoopsie still. I see the .upload file come up, but whoopsie doesn't seem to be doing anything.
Changing the upstart job to have it start/stop with dbus does not work for me. It still thinks it's not online and I get messages like this in syslog: _usr_lib_ arm-linux- gnueabihf_ url-dispatcher_ update- directory. 32011.crash)
Jul 22 16:18:06 ubuntu-phablet whoopsie[850]: Not online; processing later (/var/crash/
If I instead have it start/stop with network-manager, I don't get the messages about it being offline. However it does seem like it gets stuck, or it's waiting on some lock in whoopsie still. I see the .upload file come up, but whoopsie doesn't seem to be doing anything.