Bug #16321
evince.feature failure in buster: apparmor/journalctl
Start date:
2019-01-08
Due date:
% Done:
0%
Description
After updating the reference images (as part of Bug #16281), I’m still seeing two errors with evince.feature
, regarding apparmor
. It seems one cannot find the expected DENIED
lines in the journal; might be related to the XFIXES flood (Bug #16305), or different logging in buster? Would be best to try again with the fix for Bug #16305 just to exclude that, and/or check what happens with apparmor
through manual testing.
Final report:
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 the logs:
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"'
Subtasks
History
#1 Updated by intrigeri 2019-01-08 10:38:41
- Assignee changed from intrigeri to CyrilBrulebois
- QA Check set to Info Needed
> Would be best to try again with the fix for Bug #16305
Yes, please :)
#2 Updated by mercedes508 2019-01-27 15:07:32
- Status changed from New to Confirmed
#3 Updated by hefee 2019-04-05 09:28:32
- Status changed from Confirmed to Resolved
- Assignee deleted (
CyrilBrulebois) - QA Check changed from Info Needed to Pass
evince.feature tests passes now on sib.