[Bug 2066995] Re: apport-gtk keeps prompting to report crashes in a loop

[Steve Langasek]

> Can you provide the journal log from during that time frame?

For what service? For whoopsie, I see:

May 23 13:58:13 homer systemd[1]: Started whoopsie.service - crash report submission.
May 23 13:58:13 homer whoopsie[147832]: [13:58:13] Using lock path: /var/lock/whoopsie/lock
May 23 13:58:13 homer systemd[1]: whoopsie.service: Deactivated successfully.
May 23 13:58:13 homer systemd[1]: Started whoopsie.service - crash report submission.
May 23 13:58:13 homer whoopsie[147855]: [13:58:13] Using lock path: /var/lock/whoopsie/lock
May 23 13:58:13 homer systemd[1]: whoopsie.service: Deactivated successfully.
May 23 13:58:20 homer systemd[1]: Started whoopsie.service - crash report submission.
May 23 13:58:20 homer whoopsie[148149]: [13:58:20] Using lock path: /var/lock/whoopsie/lock
May 23 13:58:20 homer systemd[1]: whoopsie.service: Deactivated successfully.
May 23 13:58:44 homer systemd[1]: Started whoopsie.service - crash report submission.
May 23 13:58:44 homer whoopsie[148216]: [13:58:44] Using lock path: /var/lock/whoopsie/lock
May 23 13:58:44 homer systemd[1]: whoopsie.service: Deactivated successfully.
May 23 13:58:48 homer systemd[1]: Started whoopsie.service - crash report submission.
May 23 13:58:48 homer whoopsie[148496]: [13:58:48] Using lock path: /var/lock/whoopsie/lock
May 23 13:58:48 homer systemd[1]: whoopsie.service: Deactivated successfully.
May 23 13:59:11 homer systemd[1]: Started whoopsie.service - crash report submission.
May 23 13:59:11 homer whoopsie[148522]: [13:59:11] Using lock path: /var/lock/whoopsie/lock
May 23 13:59:11 homer whoopsie[148522]: [13:59:11] Parsing /var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash.
May 23 13:59:11 homer whoopsie[148522]: [13:59:11] Unable to parse report (/var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash): /var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash could not be opened.
May 23 13:59:11 homer systemd[1]: whoopsie.service: Deactivated successfully.
May 23 13:59:25 homer systemd[1]: Started whoopsie.service - crash report submission.
May 23 13:59:25 homer whoopsie[148594]: [13:59:25] Using lock path: /var/lock/whoopsie/lock
May 23 13:59:25 homer whoopsie[148594]: [13:59:25] Parsing /var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash.
May 23 13:59:25 homer whoopsie[148594]: [13:59:25] Unable to parse report (/var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash): /var/crash/_usr_bin_python-argcomplete-check-easy-install-script.1000.crash could not be opened.
May 23 13:59:25 homer systemd[1]: whoopsie.service: Deactivated successfully.
May 23 13:59:25 homer systemd[1]: Started whoopsie.service - crash report submission.
May 23 13:59:25 homer whoopsie[148608]: [13:59:25] Using lock path: /var/lock/whoopsie/lock
May 23 13:59:25 homer systemd[1]: whoopsie.service: Deactivated successfully.
May 23 13:59:29 homer systemd[1]: Started whoopsie.service - crash report submission.
May 23 13:59:29 homer whoopsie[148618]: [13:59:29] Using lock path: /var/lock/whoopsie/lock
May 23 13:59:29 homer systemd[1]: whoopsie.service: Deactivated successfully.
May 23 14:01:44 homer systemd[1]: Started whoopsie.service - crash report submission.
May 23 14:01:44 homer whoopsie[148787]: [14:01:44] Using lock path: /var/lock/whoopsie/lock
May 23 14:01:44 homer systemd[1]: whoopsie.service: Deactivated successfully.
May 23 14:01:44 homer systemd[1]: Started whoopsie.service - crash report submission.
May 23 14:01:44 homer whoopsie[148813]: [14:01:44] Using lock path: /var/lock/whoopsie/lock
May 23 14:01:44 homer systemd[1]: whoopsie.service: Deactivated successfully.
May 23 14:04:44 homer systemd[1]: Started whoopsie.service - crash report submission.
[...]

> Did that application crash multiple times?

No. It was a SINGLE crash.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2066995

Title:
  apport-gtk keeps prompting to report crashes in a loop

Status in apport package in Ubuntu:
  New

Bug description:
  /var/crash has the following contents:

  -rw-r----- 1 vorlon   vorlon   107490 May 23 16:05 _usr_bin_gourmand.1000.crash
  -rw-rw-r-- 1 vorlon   vorlon        0 May 23 16:06 _usr_bin_gourmand.1000.upload
  -rw------- 1 whoopsie whoopsie      5 May 23 16:07 _usr_bin_gourmand.1000.uploaded
  -rw-r----- 1 vorlon   vorlon    23647 May 23 13:57 _usr_bin_python-argcomplete-check-easy-install-script.1000.crash
  -rw-rw-r-- 1 vorlon   vorlon        0 May 23 13:59 _usr_bin_python-argcomplete-check-easy-install-script.1000.upload
  -rw------- 1 whoopsie whoopsie      5 May 23 13:59 _usr_bin_python-argcomplete-check-easy-install-script.1000.uploaded

  As seen, the .upload / .uploaded files were created within 2 minutes
  of each of the crashes.

  But after submitting the crash report for /usr/bin/python-argcomplete-
  check-easy-install-script, I left my desktop for a while.  I came back
  to find at least TWENTY dialogs prompting me to submit the same crash
  report.

  The only way to stop the system from creating more prompts is to
  remove these files from disk.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.1-0ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: zfs
  ApportLog:
   
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 23 16:06:43 2024
  InstallationDate: Installed on 2019-12-23 (1613 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to noble on 2024-05-22 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2066995/+subscriptions