/var/crash has perm 1777 (was: apport-gtk keeps prompting to report crashes in a loop)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apport |
Fix Released
|
High
|
Unassigned | ||
apport (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Noble |
Fix Committed
|
High
|
Unassigned |
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_
-rw-rw-r-- 1 vorlon vorlon 0 May 23 16:06 _usr_bin_
-rw------- 1 whoopsie whoopsie 5 May 23 16:07 _usr_bin_
-rw-r----- 1 vorlon vorlon 23647 May 23 13:57 _usr_bin_
-rw-rw-r-- 1 vorlon vorlon 0 May 23 13:59 _usr_bin_
-rw------- 1 whoopsie whoopsie 5 May 23 13:59 _usr_bin_
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/
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
ProcVersionSign
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelMo
ApportLog:
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckR
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)
PackageArchitec
SourcePackage: apport
UpgradeStatus: Upgraded to noble on 2024-05-22 (1 days ago)
tags: | added: rls-nn-incoming |
tags: |
added: foundations-todo removed: rls-nn-incoming |
tags: |
added: rls-nn-incoming removed: foundations-todo |
tags: |
added: foundations-todo removed: rls-nn-incoming |
description: | updated |
summary: |
- apport-gtk keeps prompting to report crashes in a loop + /var/crash has perm 1777 (was: apport-gtk keeps prompting to report + crashes in a loop) |
Changed in apport: | |
milestone: | none → 2.30.0 |
milestone: | 2.30.0 → 2.29.0 |
importance: | Undecided → High |
status: | New → Fix Released |
Changed in apport (Ubuntu): | |
status: | Confirmed → Fix Committed |
Changed in apport (Ubuntu Noble): | |
importance: | Undecided → High |
Can you provide the journal log from during that time frame? Did that application crash multiple times?