This bug was fixed in the package apport - 2.29.0-0ubuntu1
---------------
apport (2.29.0-0ubuntu1) oracular; urgency=medium
[ Benjamin Drung ]
* New upstream release:
- Ignore container crash reports from systemd-coredump (LP: #2063349)
- apport: do not modify permission of existing /var/crash or
create /var/crash with setgid permission (mode 3777) (LP: #2066995)
- Fix retracing crashes on Ubuntu 24.04 (noble) (LP: #2067120)
* ubuntu: fix possibly using dpkg_log_without_error before assignment
* Drop python3-requests dependency
* autopkgtest: add chaos-marmosets for system-tests
* apport.postinst: Create /var/crash with mode 3777 (LP: #2066995)
* Build-depend on mypy and python3-typeshed for type checking
* Build-depend on systemd-dev to determine systemd/udev paths
[ Chris Peterson ]
* d/package-hooks/subiquity.py: update information collection (LP: #2067775)
- Add information about snap update/refresh state
- Attach logs and change key names to align with the information attached
by subiquity's self-collection
- Attach hardware information
- Ensure bug reports are always private since there may be private
information in the logs
- Don't require sudo for logs collection
- Add journal logs
- Ensure snap revision is included in both deb and snap collection style
-- Benjamin Drung <bdr...@ubuntu.com> Fri, 14 Jun 2024 10:18:31 +0200
** Changed in: apport (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2063349
Title:
systemd-coredump handler does not forward the crash to the container
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Bug description:
Steps to reproduce:
1. install systemd-coredump on the host
2. open a shell on a noble container
2.1 machinectl pull-raw
"http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img";
noble
2.2 machinectl start noble
2.3 machinectl shell noble
3. install chaos-marmosets inside the container (# apt install
chaos-marmosets)
4. generate a crash inside the container (# divide-by-zero)
Observed behaviour: The .crash file is present on the host /var/crash
Expected behaviour: The .crash file should be present inside the container
/var/crash
Note: Here is how you can enable Host Network on the container
https://wiki.archlinux.org/title/systemd-nspawn#Use_host_networking
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apport 2.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportLog:
INFO: apport (pid 126611) 2024-04-24 16:34:39,226: executable:
/usr/bin/divide-by-zero (command line "divide-by-zero")
INFO: apport (pid 126611) 2024-04-24 16:34:39,664: wrote report
/var/crash/_usr_bin_divide-by-zero.1000.crash
INFO: apport (pid 127435) 2024-04-24 16:41:16,322: executable:
/usr/bin/divide-by-zero (command line "divide-by-zero")
INFO: apport (pid 127435) 2024-04-24 16:41:16,758: wrote report
/var/crash/_usr_bin_divide-by-zero.297664512.crash
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 24 17:03:02 2024
InstallationDate: Installed on 2024-04-18 (6 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2063349/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
