evince.feature failure in buster: apparmor/journalctl
After updating the reference images (as part of #16281 (closed)), I’m still
seeing two errors with
apparmor. It seems
one cannot find the expected
DENIED lines in the journal; might be
related to the XFIXES flood (#16305 (closed)), or different logging in buster?
Would be best to try again with the fix for #16305 (closed) just to exclude
that, and/or check what happens with
apparmor through manual testing.
Failing Scenarios: cucumber features/evince.feature:24 # Scenario: I cannot view a PDF file stored in non-persistent /home/amnesia/.gnupg cucumber features/evince.feature:57 # Scenario: I cannot view a PDF file stored in persistent /home/amnesia/.gnupg 5 scenarios (2 failed, 3 passed) 41 steps (2 failed, 10 skipped, 29 passed) 45m29.997s
with such commands getting run to try and locate
DENIED messages in
00:09:02.175179922: calling as root: journalctl --full --no-pager --since='2019-01-07 23:34:20' SYSLOG_IDENTIFIER=kernel | grep -w 'apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/home/amnesia/.gnupg/default-testpage.pdf"'