[Bug 1870060] Re: systemd ProtectSystem/mount namespace makes apport fail (impact most of our default system services)

[Brian Murray]

** Description changed:

+ [Impact]
+ apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS.
+ 
+ [Test Case]
+ On an Ubuntu desktop system perform the following step
+ 1) sudo pkill -11 upowerd
+ 
+ With the current version of apport there will not be a crash file for
+ upowerd in /var/crash/. With the version of apport in -proposed there
+ will be a crash file for upowerd in /var/crash/.
+ 
+ [Regression Potential]
+ In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes.
+ 
+ [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes
  
  And it seems this is true for everyone. Only supplementary binaries' crash reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year

-- 
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/1870060

Title:
  systemd ProtectSystem/mount namespace makes apport fail (impact most
  of our default system services)

Status in apport package in Ubuntu:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Confirmed
Status in bluez source package in Focal:
  Invalid

Bug description:
  [Impact]
  apport is not creating crash files for multiple system services that use ProtectSystem since Ubuntu 20.04 LTS.

  [Test Case]
  On an Ubuntu desktop system perform the following step
  1) sudo pkill -11 upowerd

  With the current version of apport there will not be a crash file for
  upowerd in /var/crash/. With the version of apport in -proposed there
  will be a crash file for upowerd in /var/crash/.

  [Regression Potential]
  In the event that the changes to /usr/share/apport/apport are bad then apport itself would crash thereby preventing us from getting any crash reports. So in addition to killing upowerd we should also test a regular application like xeyes.

  [Original Description]
  bluetoothd never leaves dumps/crash files when it crashes

  And it seems this is true for everyone. Only supplementary binaries' crash reports are shown:
  https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=bluez&period=year

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