This bug was fixed in the package apport - 2.20.11-0ubuntu8.5 --------------- apport (2.20.11-0ubuntu8.5) eoan; urgency=medium
* data/whoopsie-upload-all: append to the crash report using fdopen and open from os to cope with protected_regular being set to 1. (LP: #1848064) [ Michael Hudson-Doyle ] * Fix autopkgtest failures since recent security update: (LP: #1854237) - Fix regression in creating report for crashing setuid process by getting kernel to tell us the executable path rather than reading /proc/[pid]/exe. - Fix deletion of partially written core files. - Fix test_get_logind_session to use new API. - Restore add_proc_info raising ValueError for a dead process. - Delete test_lock_symlink, no longer applicable now that the lock is created in a directory only root can write to. -- Brian Murray <br...@ubuntu.com> Mon, 24 Feb 2020 09:38:55 -0800 ** Changed in: apport (Ubuntu Eoan) Status: Fix Committed => 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/1854237 Title: autopkgtests fail after security fixes Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Bionic: New Status in apport source package in Disco: New Status in apport source package in Eoan: Fix Released Bug description: The following autopkgtests fail after the recent security fixes: log:FAIL: test_get_logind_session (__main__.T) log:FAIL: test_core_dump_packaged (__main__.T) log:FAIL: test_core_dump_unpackaged (__main__.T) log:FAIL: test_crash_setuid_drop (__main__.T) log:FAIL: test_crash_setuid_keep (__main__.T) log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T) log:FAIL: test_lock_symlink (__main__.T) test_get_logind_session is a test failing to keep up with an API change. test_core_dump_* is failures to remove partly written core files. Both of these are easy fixes, I'll have a MP for them soon. test_crash_setuid_* are caused by the dropping of privileges when accessing the crashing process's /proc. They seem to be testing behaviour now explicitly forbidden by the fix to be honest! test_lock_symlink fails because the lock file is now always in /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could update the test, but is it really worth it after the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1854237/+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