Reports are not sent when whoopsie can't talk to NetworkManager over DBus

[Aymeric]

Starting with bug #1022261, in comment #2 Martin Pitt said that whoopsie daemon must send data to https://errors.ubuntu.com/

So after installing it I ran again the apport command to send my crash data.

$ ls /home/user/apport/
pidgin.crash
$ apt-get --yes install whoopsie
$ ps aux | grep whoopsie
whoopsie 2168 0.0 0.6 24412 3368 ? Ssl 18:23 0:00 whoopsie
$ sudo service whoopsie status
whoopsie start/running, process 2168

#starting wireshark in capture mode#

$ apport-cli /home/user/apport/pidgin.crash
*** Envoyer un rapport d'anomalie aux développeurs ?

Une fois que le rapport d'anomalie aura été envoyé, veuillez compléter le
formulaire ouvert automatiquement dans votre navigateur Web.

Que voulez-vous faire ? Les choix possibles sont :
  E: Envoyer le rapport (11.5 MB)
  V: Voir le rapport
  C: Conserver le fichier du rapport pour l'envoyer ultérieurement ou le copier quelque part
  I: Annuler et ignorer les futurs plantages de cette version du programme
  A: Annuler
Faites un choix (E/V/C/I/A) : E
$
$ ls
pidgin.crash pidgin.upload
$
And as said in the other bug, there is only a .upload file created, and absolutely no traffic to the Internet..

This computer can access errors.ubuntu.com, a least pinging and doing dns lookup, but whoopsie don't try anything.

$ ping -c 2 errors.ubuntu.com
PING errors.ubuntu.com (91.189.95.54) 56(84) bytes of data.
64 bytes from gremlin.canonical.com (91.189.95.54): icmp_req=1 ttl=44 time=57.4 ms
64 bytes from gremlin.canonical.com (91.189.95.54): icmp_req=2 ttl=44 time=57.8 ms

--- errors.ubuntu.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 57.417/57.621/57.826/0.315 ms

I start thinking that you no longer want to have information about problems on Ubuntu (daemon not installed by default, daemon doesn't work)...

PS: I'm running Precise up-to-date.

[Evan (ev)]

Is the whoopsie daemon running (`status whoopsie`)?

By the way, it sends to daisy.ubuntu.com, not errors.ubuntu.com. The latter is a website to process the information contained within Daisy.

[Brian Murray (brian-murray)]

Manually running whoopsie would also provide some valuable information here. You can do this by stopping the service and then executing the following command:

sudo env CRASH_DB_URL=https://daisy.ubuntu.com whoopsie -f

[Aymeric (mulx)]

@Evan
Whoopsie was running, you can view it with the "ps aux | grep whoopsie" in my initial comment.
BTW this is the output of status
$ status whoopsie
whoopsie start/running, process 32442

@Brian
That's the only output line produced by your command:

$ sudo env CRASH_DB_URL=https://daisy.ubuntu.com whoopsie -f
Could not get the Network Manager state: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.369" (uid=118 pid=32530 comm="whoopsie -f ") interface="org.freedesktop.DBus.Properties" member="Get" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1285 comm="NetworkManager ")

And network-manager was running
$ status network-manager
network-manager start/running, process 1285

[Evan (ev)]

Hm, so whoopsie is assuming that it's offline if it cannot talk to NetworkManager over DBus (src/connectivity.c:327). We'll have to better handle this, or just make that case assume we're online.

[Evan (ev)]

Also, assuming we're online in this case will mean that we don't have a dependency on networkmanager, and will thus be able to send networkmanager crash reports in cases where it never comes back.

[Sorin Sbarnea (ssbarnea)]

3 years later and it seems that we have to remove whoopsie if we are not using the network manger (something quite likely for servers)