This bug is back in Document Viewer/Evince(*) 3.36.7, at least under Linux Mint 20 Ulyana.
Apparently, evince does not try to use exo-open anymore, but launches firefox directly (or via a sh shell?!?!) :{
I get error: "sh: 1: exec: firefox: Operation not permitted"
I've tried the trick found here to modify /etc/apparmor.d/usr.bin.evince but with not success.
I used (NOTE: I have absolutely no idea what "ixr" could mean, thus what I'm doing...):
/usr/bin/firefox ixr, -> error about "option" x being in conflict
/usr/bin/firefox r, -> does not work
/usr/bin/sh r, -> seems very dangerous & does not work
(*) Life would be a LOT easier for bug reporters if only one name would be used for app, instead of one name in CLI (/usr/bin/evince) and another in GUI (Document Viewer)...
Hi,
This bug is back in Document Viewer/Evince(*) 3.36.7, at least under Linux Mint 20 Ulyana.
Apparently, evince does not try to use exo-open anymore, but launches firefox directly (or via a sh shell?!?!) :{
I get error: "sh: 1: exec: firefox: Operation not permitted"
I've tried the trick found here to modify /etc/apparmor. d/usr.bin. evince but with not success.
I used (NOTE: I have absolutely no idea what "ixr" could mean, thus what I'm doing...):
/usr/bin/firefox ixr, -> error about "option" x being in conflict
/usr/bin/firefox r, -> does not work
/usr/bin/sh r, -> seems very dangerous & does not work
(*) Life would be a LOT easier for bug reporters if only one name would be used for app, instead of one name in CLI (/usr/bin/evince) and another in GUI (Document Viewer)...