Ubuntu
whoopsie package

crash reports are not being uploaded automatically

Bug #1332925 reported by Alan Pope 🍺🐧🐱 πŸ¦„
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
whoopsie (Ubuntu)
Fix Released
High
Evan

Bug Description

I have multiple devices (flo, mako, manta) running various versions of Ubuntu Touch..
They are all set in the privacy settings to allow crash reports to be sent to Canonical.
As far as I can tell none of them have ever sent them automatically.
I can force them to upload with whoopsie-upload-all, but this is not ideal, I have to remember to do that, and if I wipe my device (which I do now and then) they are lost before uploading.

I have confirmed with others that I am not alone in this. Here's my /var/crashes:-

alan@deep-thought:~$ adb shell "ls -l /var/crash && system-image-cli --info"
total 7124
-rw-r--r-- 1 phablet whoopsie 7843 Jun 17 14:00 _sbin_init.32011.crash
-rw-r----- 1 root whoopsie 18821 Jun 18 10:45 _usr_bin_click.0.crash
-rw-r----- 1 phablet whoopsie 794312 Jun 17 14:12 _usr_bin_maliit-server.32011.crash
-rw-r----- 1 phablet whoopsie 107617 Jun 21 19:27 _usr_bin_mtp-server.32011.crash
-rw-r----- 1 phablet whoopsie 5239540 Jun 18 09:04 _usr_bin_online-accounts-ui.32011.crash
-rw-r----- 1 phablet whoopsie 1085578 Jun 20 15:39 _usr_bin_system-settings-wizard.32011.crash
-rw-rw-r-- 1 phablet whoopsie 12451 Jun 20 15:19 _usr_lib_arm-linux-gnueabihf_ubuntu-app-launch_desktop-hook.32011.crash
-rw-r--r-- 1 phablet whoopsie 10443 Jun 19 10:50 _usr_lib_arm-linux-gnueabihf_url-dispatcher_update-directory.32011.crash
current build number: 91
device name: flo
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/utopic-proposed
last update: 2014-06-20 08:57:30
version version: 91
version ubuntu: 20140620.1
version device: 20140530

alan@deep-thought:~$ adb shell "ls -l /var/crash && system-image-cli --info"
total 22176
-rw-r----- 1 phablet whoopsie 1097915 Jun 16 16:08 _usr_bin_maliit-server.32011.crash
---------- 1 phablet whoopsie 753594 Jun 17 16:12 _usr_bin_online-accounts-ui.32011.crash
---------- 1 phablet whoopsie 15880192 Jun 20 12:58 _usr_bin_webbrowser-app.32011.crash
-rw-r----- 1 phablet whoopsie 269491 Jun 15 23:06 _usr_lib_arm-linux-gnueabihf_indicator-network_indicator-network-service.32011.crash
-rw-r----- 1 phablet whoopsie 4421047 Jun 16 13:48 _usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash
-rw-rw-r-- 1 phablet autopilot 12378 Jun 20 20:51 _usr_lib_arm-linux-gnueabihf_ubuntu-app-launch_desktop-hook.32011.crash
-rw-r----- 1 root whoopsie 261254 Jun 17 17:19 _usr_lib_arm-linux-gnueabihf_urfkill_urfkilld.0.crash
current build number: 91
device name: mako
channel: ubuntu-touch/utopic-proposed
last update: 2014-06-20 12:59:32
version version: 91
version ubuntu: 20140620.1
version device: 20140530

The following device has uploaded because I forced it to:-

alan@deep-thought:~$ adb shell "ls -l /var/crash && system-image-cli --info"
total 1184
---------- 1 root whoopsie 8236 Jun 20 09:00 _lib_systemd_systemd-logind.0.crash
-rw-r----- 1 phablet whoopsie 1109662 Jun 19 09:37 _usr_bin_maliit-server.32011.crash
-rw-r--r-- 1 phablet rtkit 0 Jun 19 09:37 _usr_bin_maliit-server.32011.upload
-rw------- 1 whoopsie rtkit 0 Jun 19 13:52 _usr_bin_maliit-server.32011.uploaded
-rw-r----- 1 phablet whoopsie 73355 Jun 22 09:19 _usr_bin_system-settings.32011.crash
-rw-r----- 1 phablet rtkit 12598 Jun 20 10:00 _usr_lib_arm-linux-gnueabihf_ubuntu-app-launch_desktop-hook.32011.crash
-rw-r--r-- 1 phablet rtkit 0 Jun 19 09:37 _usr_lib_arm-linux-gnueabihf_ubuntu-app-launch_desktop-hook.32011.upload
-rw------- 1 whoopsie rtkit 0 Jun 19 13:50 _usr_lib_arm-linux-gnueabihf_ubuntu-app-launch_desktop-hook.32011.uploaded
current build number: 92
device name: mako
channel: ubuntu-touch/utopic-proposed
last update: 2014-06-21 16:03:54
version version: 92
version ubuntu: 20140621
version device: 20140530

alan@deep-thought:~$ adb shell "ls -l /var/crash && system-image-cli --info"
total 4276
-rw-r----- 1 phablet whoopsie 2460469 Jun 16 14:03 _usr_bin_mediascanner-service-2.0.32011.crash
-rw-r----- 1 phablet whoopsie 1896801 Jun 19 09:36 _usr_bin_mediascanner-service.32011.crash
-rw-rw-r-- 1 phablet rtkit 12391 Jun 19 16:15 _usr_lib_arm-linux-gnueabihf_ubuntu-app-launch_desktop-hook.32011.crash
current build number: 89
device name: manta
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/utopic-proposed
last update: 2014-06-19 16:14:40
version version: 89
version ubuntu: 20140619.1
version device: 20140530

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: whoopsie 0.2.31
Uname: Linux 3.4.0-3-flo armv7l
ApportVersion: 2.14.3-0ubuntu2
Architecture: armhf
Date: Sun Jun 22 08:09:17 2014
InstallationDate: Installed on 2014-06-20 (2 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140620.1)
SourcePackage: whoopsie
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Alan Pope 🍺🐧🐱 πŸ¦„ (popey) wrote :
Revision history for this message
dino99 (9d9) wrote :

Here is what i've got on my i386 pc running Utopic and booting with 'systemd':

Apport have been recently set to 'enable'
but got some 'whoopsie.service' failures inside boot.log

then glancing at /etc/default/whoopsie, i've seen that 2 lines there was still set to 'false' (the Apport upgrade should also have set it to 'true')

so purging everything related to 'whoopsie' from synaptic, then reinstalling whoopsie, have confirmed that /etc/default/whoopsie was set now to 'true'

checking 'systemctl status whoopsie.service' also confirm the 'active' status.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in whoopsie (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

Since post #2 i've got a crash, and it has been reported as expected. So i suppose that 'apport' have to be blamed as it has not updated the default whoopsie settings when it has switched to report=true recently.

Alexander Sack (asac)
Changed in whoopsie (Ubuntu):
assignee: nobody → Evan Dandrea (ev)
importance: Undecided → High
Revision history for this message
Brian Murray (brian-murray) wrote :

@Alan - Could you please include the output of 'grep whoopsie /var/log/syslog' from each of the individual devices on which you have noticed this issue? Thanks in advance.

Revision history for this message
Alan Pope 🍺🐧🐱 πŸ¦„ (popey) wrote :

Here you go...

alan@deep-thought:~$ adb shell "grep whoopsie /var/log/syslog"
alan@deep-thought:~$ adb shell "grep whoopsie /var/log/syslog"
Jun 23 08:12:27 ubuntu-phablet whoopsie[2404]: whoopsie 0.2.31 starting up.
Jun 23 08:12:27 ubuntu-phablet whoopsie[2404]: Unable to find a hardware address
Jun 23 08:12:27 ubuntu-phablet whoopsie[2404]: Using lock path: /var/lock/whoopsie/lock
Jun 23 08:12:28 ubuntu-phablet whoopsie[2506]: offline
Jun 23 08:12:29 ubuntu-phablet whoopsie[2506]: offline
Jun 23 08:12:30 ubuntu-phablet whoopsie[2506]: online
alan@deep-thought:~$ adb shell "grep whoopsie /var/log/syslog"
Jun 23 07:05:09 ubuntu-phablet whoopsie[2267]: online
Jun 23 07:05:18 ubuntu-phablet whoopsie[2267]: message repeated 9 times: [ online]
Jun 23 07:39:08 ubuntu-phablet whoopsie[2267]: Parsing /var/crash/_usr_bin_system-settings.32011.crash.
Jun 23 07:39:08 ubuntu-phablet whoopsie[2267]: Uploading /var/crash/_usr_bin_system-settings.32011.crash.
Jun 23 07:39:08 ubuntu-phablet whoopsie[2267]: Sent; server replied with: No error
Jun 23 07:39:08 ubuntu-phablet whoopsie[2267]: Response code: 502
Jun 23 07:39:08 ubuntu-phablet whoopsie[2267]: Server replied with:
Jun 23 07:39:08 ubuntu-phablet whoopsie[2267]: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">#012<html><head>#012<title>502 Bad Gateway</title>#012</head><body>#012<h1>Bad Gateway</h1>#012<p>The proxy server received an invalid#015#012response from an upstream server.<br />#015#012</p>#012<hr>#012<address>Apache/2.2.22 (Ubuntu) Server at daisy.ubuntu.com Port 443</address>#012</body></html>#012
Jun 23 09:09:43 ubuntu-phablet whoopsie[2267]: online
Jun 23 09:11:12 ubuntu-phablet whoopsie[2103]: whoopsie 0.2.31 starting up.
Jun 23 09:11:12 ubuntu-phablet whoopsie[2103]: Unable to find a hardware address
Jun 23 09:11:12 ubuntu-phablet whoopsie[2103]: Using lock path: /var/lock/whoopsie/lock
Jun 23 09:11:12 ubuntu-phablet whoopsie[2141]: offline
Jun 23 09:11:21 ubuntu-phablet whoopsie[2141]: message repeated 5 times: [ offline]
Jun 23 09:11:22 ubuntu-phablet whoopsie[2141]: Network connection found that may be a paid data plan.
Jun 23 09:11:22 ubuntu-phablet whoopsie[2141]: offline
alan@deep-thought:~$ adb shell "grep whoopsie /var/log/syslog"
alan@deep-thought:~$

Revision history for this message
Brian Murray (brian-murray) wrote :

Actually, it is interesting that there are no .upload files for the .crash files on the systems.

Revision history for this message
Brian Murray (brian-murray) wrote :

Also does the file /var/lib/apport/autoreport exist on your devices?

Revision history for this message
Alan Pope 🍺🐧🐱 πŸ¦„ (popey) wrote :

/var/lib/apport/autoreport doesn't exist on any of them

Revision history for this message
Brian Murray (brian-murray) wrote :

It is also interesting that the system reporting this bug only seems to have .crash files in /var/crash and no .upload files.

Revision history for this message
Brian Murray (brian-murray) wrote :

/var/lib/apport/autoreport is created when one goes to system settings, security and privacy, diagnostics and checks "app crashes and errors". Do you choose to enable crash reporting every time you flash the device?

Revision history for this message
Alan Pope 🍺🐧🐱 πŸ¦„ (popey) wrote :

No. It's already ticked.

I just visited that part of system settings on one of my phones and see the tick box is ticked. Now the file has arrived.

-rw-r--r-- 1 root root 0 Jun 24 09:04 /var/lib/apport/autoreport

Note the time stamp is just now, confirming it's created by visiting that page in system settings.

This seems flawed. I am happy to upload my crash dumps, and given it is ticked when I visit that dialog, I assumed it's switched on by default, which from Barry's comment, it seems it's not.

I (and other devs) flash our phones a *lot*, sometimes multiple times a day. I (and others) will almost certainly forget to visit this pane to switch crash reporting on. It will also be problematic for devices which are auto-testing in the lab.

Can we have that setting on my default during development, and perhaps switch off post-release if people are twitchy about this being on by default.

Revision history for this message
Brian Murray (brian-murray) wrote : Re: [Bug 1332925] Re: crash reports are not being uploaded automatically

On Tue, Jun 24, 2014 at 08:10:31AM -0000, Alan Pope γ‹› wrote:
> No. It's already ticked.
>
> I just visited that part of system settings on one of my phones and see
> the tick box is ticked. Now the file has arrived.
>
> -rw-r--r-- 1 root root 0 Jun 24 09:04 /var/lib/apport/autoreport
>
> Note the time stamp is just now, confirming it's created by visiting
> that page in system settings.
>
> This seems flawed. I am happy to upload my crash dumps, and given it is
> ticked when I visit that dialog, I assumed it's switched on by default,
> which from Barry's comment, it seems it's not.

That is correct reporting of crashes is not on by default.

> I (and other devs) flash our phones a *lot*, sometimes multiple times a
> day. I (and others) will almost certainly forget to visit this pane to
> switch crash reporting on. It will also be problematic for devices which
> are auto-testing in the lab.

Do you go through the setup wizard each time? There is a merge
proposal[1] for ubuntu system settings that will ask about reporting
crashes during the initial setup of the phone.

[1]
https://code.launchpad.net/~cimi/ubuntu-system-settings/wizard.privacy/+merge/213124

--
Brian Murray

Revision history for this message
Brian Murray (brian-murray) wrote :

Actually the setup wizard will actually says the following ""Your phone is setup to automatically report errors to Canonical. This can be disabled in system settings.", so crash reporting will be enabled by default once that branch has landed.

Revision history for this message
Brian Murray (brian-murray) wrote :

@Alan - are you still currently affected by this bug? Many a change has landed to whoopsie and apport-noui now which should have resolved this problem. Thanks!

Brian Murray (brian-murray)
Changed in whoopsie (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Alan Pope 🍺🐧🐱 πŸ¦„ (popey) wrote :

Sorry for not replying earlier. Yes. I see this as fixed on my device.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.