Running APT evince 42.1-3 on stock Ubuntu 22.04/GNOME 42.0/Wayland.
My issue is Evince opening in a tiny window every time it's fired off; this deployment was upgraded from 21.10, which didn't suffer from such issue.
I attach below the output from `journalctl -f` while starting up Evince, which clearly shows AppArmor violations.
I thus attempted the approach from https://askubuntu.com/a/886011/145568 . When running with `aa-complain evince`, Evince behaves properly; I accepted `aa-logprof`'s suggestion to grant /usr/bin/evince [owner /run/user/1000/at-spi/bus rw,]. Unfortunately as soon as I reinstate `aa-enforce evince`, the tiny window issue re-appears.
(Note: at first I Ignored /usr/sbin/cups-browsed [capability sys_nice,] because I thought it was unrelated; I tried to grant it but this still doesn't solve the issue).
Running APT evince 42.1-3 on stock Ubuntu 22.04/GNOME 42.0/Wayland.
My issue is Evince opening in a tiny window every time it's fired off; this deployment was upgraded from 21.10, which didn't suffer from such issue.
I attach below the output from `journalctl -f` while starting up Evince, which clearly shows AppArmor violations.
I thus attempted the approach from https:/ /askubuntu. com/a/886011/ 145568 . When running with `aa-complain evince`, Evince behaves properly; I accepted `aa-logprof`'s suggestion to grant /usr/bin/evince [owner /run/user/ 1000/at- spi/bus rw,]. Unfortunately as soon as I reinstate `aa-enforce evince`, the tiny window issue re-appears.
(Note: at first I Ignored /usr/sbin/ cups-browsed [capability sys_nice,] because I thought it was unrelated; I tried to grant it but this still doesn't solve the issue).