apport-autoreport.service fails: whoopsie.path is not enabled

[satmandu]

This is what the service reports. Aside from crash reports no longer uploading automatically, I'm having trouble pointing ubuntu-bug to crash reports in /var/crash - a window opens, but then a browser never opens. ubuntu-bug program-name does open the browser though.

× apport-autoreport.service - Process error reports when automatic reporting is enabled
     Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static)
     Active: failed (Result: exit-code) since Tue 2022-09-06 14:27:48 EDT; 2min 33s ago
TriggeredBy: ● apport-autoreport.path
             ● apport-autoreport.timer
    Process: 24994 ExecStart=/usr/share/apport/whoopsie-upload-all --timeout 20 (code=exited, status=1/FAILURE)
   Main PID: 24994 (code=exited, status=1/FAILURE)
        CPU: 115ms

Sep 06 14:27:48 mbp113 systemd[1]: Starting Process error reports when automatic reporting is enabled...
Sep 06 14:27:48 mbp113 whoopsie-upload-all[24994]: ERROR: whoopsie.path is not enabled
Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE
Sep 06 14:27:48 mbp113 systemd[1]: apport-autoreport.service: Failed with result 'exit-code'.
Sep 06 14:27:48 mbp113 systemd[1]: Failed to start Process error reports when automatic reporting is enabled.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: apport 2.23.0-0ubuntu1
Uname: Linux 6.0.0-rc4 x86_64
NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
ApportLog:
 ERROR: apport (pid 20795) Tue Sep 6 14:26:35 2022: called for pid 3732, signal 6, core limit 0, dump mode 1
 ERROR: apport (pid 20795) Tue Sep 6 14:26:35 2022: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
 ERROR: apport (pid 20795) Tue Sep 6 14:26:36 2022: debug: session gdbus call: (true,)

 ERROR: apport (pid 20795) Tue Sep 6 14:26:46 2022: wrote report /var/crash/_usr_bin_gnome-shell.1000.crash
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CrashReports:
 640:1000:123:43075180:2022-09-06 14:26:45.388720512 -0400:2022-09-06 14:27:48.608538333 -0400:/var/crash/_usr_bin_gnome-shell.1000.crash
 640:1000:123:8681261:2022-08-29 22:32:29.231918756 -0400:2022-08-29 20:57:41.939131333 -0400:/var/crash/_usr_libexec_goa-daemon.1000.crash
 640:1000:123:44557691:2022-08-30 08:01:54.998418753 -0400:2022-08-30 08:01:50.202489325 -0400:/var/crash/_opt_google_chrome_chrome.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 6 14:29:03 2022
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

[Benjamin Drung (bdrung)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

What is the output of "systemctl status whoopsie.path"? Can you start this service? "sudo systemctl start whoopsie.path"?

[satmandu (satadru-umich)]

satadru@mbp113 ~$ systemctl status whoopsie.path
● whoopsie.path - Start whoopsie on modification of the /var/crash directory
     Loaded: loaded (/lib/systemd/system/whoopsie.path; disabled; preset: enabled)
     Active: active (waiting) since Mon 2022-09-12 09:22:59 EDT; 4min 35s ago
      Until: Mon 2022-09-12 09:22:59 EDT; 4min 35s ago
   Triggers: ● whoopsie.service

satadru@mbp113 ~$ sudo systemctl status whoopsie
○ whoopsie.service - crash report submission
     Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; preset: enabled)
     Active: inactive (dead) since Mon 2022-09-12 09:28:09 EDT; 4s ago
   Duration: 14ms
TriggeredBy: ● whoopsie.path
    Process: 33720 ExecStart=/usr/bin/whoopsie -f --no-polling (code=exited, status=0/SUCCESS)
   Main PID: 33720 (code=exited, status=0/SUCCESS)
        CPU: 8ms

Sep 12 09:28:09 mbp113 systemd[1]: Started crash report submission.
Sep 12 09:28:09 mbp113 whoopsie[33720]: [09:28:09] Using lock path: /var/lock/whoopsie/lock

satadru@mbp113 ~$ sudo systemctl start whoopsie.path
satadru@mbp113 ~$ sudo systemctl status whoopsie.path
● whoopsie.path - Start whoopsie on modification of the /var/crash directory
     Loaded: loaded (/lib/systemd/system/whoopsie.path; disabled; preset: enabled)
     Active: active (waiting) since Mon 2022-09-12 09:22:59 EDT; 6min ago
      Until: Mon 2022-09-12 09:22:59 EDT; 6min ago
   Triggers: ● whoopsie.service

[satmandu (satadru-umich)]

satadru@mbp113 ~$ sudo systemctl status apport-autoreport.service
× apport-autoreport.service - Process error reports when automatic reporting is enabled
     Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static)
     Active: failed (Result: exit-code) since Mon 2022-09-12 09:22:59 EDT; 7min ago
TriggeredBy: ● apport-autoreport.timer
             ● apport-autoreport.path
   Main PID: 2598 (code=exited, status=1/FAILURE)
        CPU: 150ms

Sep 12 09:22:59 mbp113 systemd[1]: Starting Process error reports when automatic reporting is enabled...
Sep 12 09:22:59 mbp113 whoopsie-upload-all[2598]: ERROR: whoopsie.path is not enabled
Sep 12 09:22:59 mbp113 systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE
Sep 12 09:22:59 mbp113 systemd[1]: apport-autoreport.service: Failed with result 'exit-code'.

[William Wilson (jawn-smith)]

Can you check in the control panel under "Privacy" -> "Diagnostics"? If "Send error reports to Canonical" is set to "Never" then the whoopsie.path service will be disabled.

[satmandu (satadru-umich)]

The Diagnostics option showed as "Automatic"... and then showed "Never"!

I flipped it to automatic, and now I see this:

systemctl status whoopsie.path
● whoopsie.path - Start whoopsie on modification of the /var/crash directory
     Loaded: loaded (/lib/systemd/system/whoopsie.path; enabled; preset: enabled)
     Active: active (waiting) since Wed 2022-09-14 22:18:25 EDT; 2min 5s ago
      Until: Wed 2022-09-14 22:18:25 EDT; 2min 5s ago
   Triggers: ● whoopsie.service

systemctl status apport-autoreport.service
× apport-autoreport.service - Process error reports when automatic reporting is enabled
     Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static)
     Active: failed (Result: exit-code) since Wed 2022-09-14 22:19:37 EDT; 2min 18s ago
TriggeredBy: ● apport-autoreport.timer
             ● apport-autoreport.path
    Process: 18585 ExecStart=/usr/share/apport/whoopsie-upload-all --timeout 20 (code=exited, status=2)
   Main PID: 18585 (code=exited, status=2)
        CPU: 17.854s

Sep 14 22:19:05 mbp113 whoopsie-upload-all[18585]: WARNING: hook failed for processing /var/crash/_opt_Signal_signal-desktop.1000.crash:
Sep 14 22:19:07 mbp113 whoopsie-upload-all[18585]: INFO:root:Marking /var/crash/_opt_Signal_signal-desktop.1000.crash for whoopsie upload
Sep 14 22:19:07 mbp113 whoopsie-upload-all[18585]: INFO:root:Waiting for whoopsie to upload reports (timeout: 20 s)
Sep 14 22:19:07 mbp113 whoopsie-upload-all[18585]: INFO:root: missing (remaining: 20 s): /var/crash/_usr_libexec_goa-daemon.1000.uploaded /var/crash/_opt_Signal_signal-desktop.1000.uploaded
Sep 14 22:19:17 mbp113 whoopsie-upload-all[18585]: INFO:root: missing (remaining: 10 s): /var/crash/_opt_Signal_signal-desktop.1000.uploaded
Sep 14 22:19:27 mbp113 whoopsie-upload-all[18585]: INFO:root: missing (remaining: 0 s): /var/crash/_opt_Signal_signal-desktop.1000.uploaded
Sep 14 22:19:37 mbp113 systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Sep 14 22:19:37 mbp113 systemd[1]: apport-autoreport.service: Failed with result 'exit-code'.
Sep 14 22:19:37 mbp113 systemd[1]: Failed to start Process error reports when automatic reporting is enabled.
Sep 14 22:19:37 mbp113 systemd[1]: apport-autoreport.service: Consumed 17.854s CPU time.

[satmandu (satadru-umich)]

ls /var/crash/
_opt_Signal_signal-desktop.1000.crash _usr_bin_gnome-shell.1000.crash _usr_bin_gnome-shell.1000.uploaded _usr_libexec_goa-daemon.1000.upload
_opt_Signal_signal-desktop.1000.upload _usr_bin_gnome-shell.1000.upload _usr_libexec_goa-daemon.1000.crash _usr_libexec_goa-daemon.1000.uploaded

I guess it is working now...

[Sebastian Unger (sebunger44)]

Why is this invalid? It is still a bug in Ubuntu. I have a bunch of machines in this state which all now report a systemd state of Degraded.

Is there a way to fix this from the command-line? I only have ssh access to these machines.

[Sebastian Unger (sebunger44)]

Is it just a matter of enabling whoopsie.path?

[Rolf Leggewie (r0lf)]

reopening as per comment #8. @Sebastian, I suggest you disable whoopsie-path instead "systemctl disable whoopsie-path" and then reboot to get a clean "systemctl --failed"

for those who are like me looking for the "Privacy" GUI control panel mentioned in comment #5, make sure you have the "activity-log-manager" package installed