whoopsie cannot report crash reports from live environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
whoopsie (Ubuntu) |
New
|
High
|
Unassigned | ||
Mantic |
New
|
High
|
Unassigned |
Bug Description
The .uploaded file corresponding to a crash report had NULL for its contents so I used journalctl to find information about whoopsie and saw the following:
Sep 18 15:28:42 ubuntu systemd[1]: Started whoopsie.service - crash report submission.
Sep 18 15:28:42 ubuntu whoopsie[14510]: [15:28:42] Using lock path: /var/lock/
Sep 18 15:28:42 ubuntu whoopsie[14510]: [15:28:42] Parsing /var/crash/
Sep 18 15:28:42 ubuntu whoopsie[14510]: [15:28:42] Unable to parse report (/var/crash/
Sep 18 15:28:42 ubuntu systemd[1]: whoopsie.service: Deactivated successfully.
This was on an Ubuntu daily-legacy image dated 20230918.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: whoopsie 0.2.77
ProcVersionSign
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelMo
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckR
CasperVersion: 1.482
CrashReports:
600:109:
644:1000:
640:1000:
640:1000:
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 18 15:31:48 2023
LiveMediaBuild: Ubuntu Legacy 23.10 "Mantic Minotaur" - Daily amd64 (20230918)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-
XDG_RUNTIME_
RelatedPackageV
SourcePackage: whoopsie
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in whoopsie (Ubuntu): | |
importance: | Undecided → High |
tags: |
added: foundations-todo removed: rls-mm-incoming |
If I read CrashReports correctly /var/crash/ _usr_lib_ ubiquity_ bin_ubiquity. 0.crash is owned by 1000:1000 and has permission 640. So only user 1000 can read it. Isn't whoopsie running as root?