Evince → Firefox → native messaging fail
Both Chromium and Firefox support native messaging so that browser extensions can communicate with a program on the host system. A native messaging program can be stored anywhere on the system: the path to it is set in a configuration file.
On Ubuntu, the AppArmor profile for /usr/bin/evince and/or /usr/bin/evince//sanitized_helper breaks native messaging if a browser is spawned as the result of clicking a hyperlink in a pdf. IOW:
What I observe:
- close all browsers
- evince hyperlink.pdf
- click the link
- behold, extensions in the browser that require native messaging don't function
What I expect: the browser to function normally, even if it happens to be started from a link in evince.
Here's a test case: nm.zip
Edited by intrigeri