Comment 2 for bug 1712039

ts (tsdz) wrote :

The file itself may be not specific to evince, but the behaviour that evince tries to read it (and AppArmor denies that) is specific to the AppArmor profile file that gets delivered with evince-common (/etc/apparmor.d/usr.bin.evince).
That is why i think it affects the package evince or evince-common, to be precise.