Evince cannot open HTTP link in Google Chrome or chromium-browser
Impact: when chromium-browser or Google Chrome are set as the default browser, the user is unable to open links via PDF files
Development fix: the fix will be applied to Quantal via pocket copy of this SRU.
Stable fix: this was fixed in r2039 by adding the following to /etc/apparmor.
# While the chromium and chrome sandboxes are setuid root, they only link
# in limited libraries so glibc's secure execution should be enough to not
# require the santized_helper (ie, LD_PRELOAD will only use standard system
# paths (man ld.so)).
1. Install chromium-browser and/or Google Chrome
2. Launch chromium-browser (or Chrome) and set it as the default web browser
3. Open a PDF with a link in it (attached) in evince and click on the link.
At this point, chromium-browser (or Chrome) should open to the link specified. Without the patch, it does not open and there are AppArmor denials in /var/log/kern.log.
Regression potential: the regression potential is considered low. Launching chromium-browser and Chrome via evince is currently broken, so there is no regression potential there, however ubuntu-helpers is included by the (disable by default) firefox profile so a mistake in the added policy could prevent firefox policy from loading.
|Changed in apparmor (Ubuntu):|
|status:||New → Triaged|
|Changed in apparmor (Ubuntu Quantal):|
|status:||Triaged → In Progress|
|assignee:||Steve Beattie (sbeattie) → Jamie Strandboge (jdstrand)|