Foundations is taking this for focal but it's at risk for the GA release. If there are system services that are crashing, and this issue is getting in the way of the Desktop Team debugging those crashes, a workaround would be to disable the ProtectSystem rule in the systemd units (or instruct users how to do so locally). This is defense in depth, but is not a core part of our security model in Ubuntu that we should be unwilling to disable it for debugging.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez 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: New Status in bluez package in Ubuntu: Invalid Status in apport source package in Focal: New Status in bluez source package in Focal: Invalid Bug 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 -- 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
