This bug was fixed in the package apport - 2.20.11-0ubuntu13
---------------
apport (2.20.11-0ubuntu13) focal; urgency=medium
[ Brian Murray ]
* Create additional symlinks to the source_linux.py apport package hook for
many OEM kernels. Thanks to You-Sheng Yang for the patch. (LP: #1847967)
[ 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.
-- Michael Hudson-Doyle <michael.hud...@ubuntu.com> Fri, 06 Dec 2019
08:57:09 +1300
** Changed in: apport (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
New
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/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
