It's due to the system bluetooth.service unit using ProtectSystem=full, commenting that line from the service and doing $ sudo systemctl stop blueetooth.service $ sudo systemctl daemon-reload $ sudo systemctl start blueetooth.service
and sending the sig11 makes apport trigger Note that systemd-coredump doesn't have this problem and register a backtrace in the journal even with ProtectSystem in use, which suggests it's an apport limitation ** Summary changed: - bluetoothd never leaves dumps/crash files when it crashes + systemd ProtectSystem makes apport fail ** Summary changed: - systemd ProtectSystem makes apport fail + systemd ProtectSystem makes apport fail (impacts bluez) -- 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 makes apport fail (impacts bluez) Status in bluez package in Ubuntu: New Status in whoopsie package in Ubuntu: New 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/bluez/+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
