[Bug 2066995] Re: /var/crash has perm 1777 (was: apport-gtk keeps prompting to report crashes in a loop)

[Chris Peterson]

I booted a noble release ISO:

$ stat -c "%a %n" /var/crash
1777

$ sudo apt -y install apport/noble-proposed
...

$ stat -c "%a %n" /var/crash
3777

$ python3 -c "import ctypes; ctypes.string_at(0)"
Segmentation fault (core dumped)


Whoopsie then picks up the crash file and I'm presented with the report prompt. After hitting send I can confirm the crash is uploaded correctly.

Uploaded here: https://errors.ubuntu.com/oops/4efcf3fe-5512-11ef-
bcb9-fa163e171f02


** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble

-- 
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:
  /var/crash has perm 1777 (was: apport-gtk keeps prompting to report
  crashes in a loop)

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  On affected systems, Python crashes will be owned by the crashing
  group instead of whoopsie. This causes whoopsie to fail reading and
  uploading the crash report. So a lot of Python crashes were not
  reporting and keeping us blind.

  [ Test Plan ]

  1. Reconstruct the problem by setting the permission of /var/crash to 1777.
  2. Upgrade Apport to the fixed version
  3. Verify that /var/crash has the permission 3777 after the update.
  4. Run and crash a random Python script (needs to be from a Ubuntu package)
  5. Verify that the Python crash was correctly uploaded.

  [ Where problems could occur ]

  The fix touched the /var/crash permission and the apport.service
  startup code. This might lead to failures on custom setup (despite
  using similar postinst code than whoopsie).

  This fix might still not address the initial bug report of reporting
  crashes in a loop. In this case a follow-up bug report should be
  started.

  [ Original report ]

  /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/apport/+bug/2066995/+subscriptions