[Touch-packages] [Bug 964510] Re: Evince cannot open HTTP link in Google Chrome or chromium-browser
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: apparmor (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/964510
Title:
Evince cannot open HTTP link in Google Chrome or chromium-browser
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Precise:
Won't Fix
Status in apparmor source package in Quantal:
Fix Released
Bug description:
SRU Justification:
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.d/abstractions/ubuntu-helpers:
# 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)).
/usr/lib/chromium-browser/chromium-browser-sandbox PUxr,
/opt/google/chrome/chrome-sandbox PUxr,
/opt/google/chrome/google-chrome Pixr,
/opt/google/chrome/chrome Pixr,
/opt/google/chrome/lib*.so{,.*} m,
TEST CASE:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/964510/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 964510] Re: Evince cannot open HTTP link in Google Chrome or chromium-browser
Adnan, Cerin, Raffi - please note the message above from Seth, and
gather the evidence as he describes, and file a new bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/964510
Title:
Evince cannot open HTTP link in Google Chrome or chromium-browser
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Precise:
Triaged
Status in apparmor source package in Quantal:
Fix Released
Bug description:
SRU Justification:
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.d/abstractions/ubuntu-helpers:
# 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)).
/usr/lib/chromium-browser/chromium-browser-sandbox PUxr,
/opt/google/chrome/chrome-sandbox PUxr,
/opt/google/chrome/google-chrome Pixr,
/opt/google/chrome/chrome Pixr,
/opt/google/chrome/lib*.so{,.*} m,
TEST CASE:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/964510/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 964510] Re: Evince cannot open HTTP link in Google Chrome or chromium-browser
And in 17.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/964510
Title:
Evince cannot open HTTP link in Google Chrome or chromium-browser
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Precise:
Triaged
Status in apparmor source package in Quantal:
Fix Released
Bug description:
SRU Justification:
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.d/abstractions/ubuntu-helpers:
# 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)).
/usr/lib/chromium-browser/chromium-browser-sandbox PUxr,
/opt/google/chrome/chrome-sandbox PUxr,
/opt/google/chrome/google-chrome Pixr,
/opt/google/chrome/chrome Pixr,
/opt/google/chrome/lib*.so{,.*} m,
TEST CASE:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/964510/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 964510] Re: Evince cannot open HTTP link in Google Chrome or chromium-browser
This is still broken in 16.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/964510
Title:
Evince cannot open HTTP link in Google Chrome or chromium-browser
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Precise:
Triaged
Status in apparmor source package in Quantal:
Fix Released
Bug description:
SRU Justification:
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.d/abstractions/ubuntu-helpers:
# 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)).
/usr/lib/chromium-browser/chromium-browser-sandbox PUxr,
/opt/google/chrome/chrome-sandbox PUxr,
/opt/google/chrome/google-chrome Pixr,
/opt/google/chrome/chrome Pixr,
/opt/google/chrome/lib*.so{,.*} m,
TEST CASE:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/964510/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 964510] Re: Evince cannot open HTTP link in Google Chrome or chromium-browser
Adnan, this old bug describes an issue that was fixed several years ago.
Please file a new bug with ubuntu-bug evince if you're experiencing
similar symptoms. Be sure to include the output of grep DEN
/var/log/syslog or grep DEN /var/log/audit/audit.log (if you're using
auditd).
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/964510
Title:
Evince cannot open HTTP link in Google Chrome or chromium-browser
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Precise:
Triaged
Status in apparmor source package in Quantal:
Fix Released
Bug description:
SRU Justification:
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.d/abstractions/ubuntu-helpers:
# 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)).
/usr/lib/chromium-browser/chromium-browser-sandbox PUxr,
/opt/google/chrome/chrome-sandbox PUxr,
/opt/google/chrome/google-chrome Pixr,
/opt/google/chrome/chrome Pixr,
/opt/google/chrome/lib*.so{,.*} m,
TEST CASE:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/964510/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 964510] Re: Evince cannot open HTTP link in Google Chrome or chromium-browser
This problem is still present 4 years later in 16.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/964510
Title:
Evince cannot open HTTP link in Google Chrome or chromium-browser
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Precise:
Triaged
Status in apparmor source package in Quantal:
Fix Released
Bug description:
SRU Justification:
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.d/abstractions/ubuntu-helpers:
# 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)).
/usr/lib/chromium-browser/chromium-browser-sandbox PUxr,
/opt/google/chrome/chrome-sandbox PUxr,
/opt/google/chrome/google-chrome Pixr,
/opt/google/chrome/chrome Pixr,
/opt/google/chrome/lib*.so{,.*} m,
TEST CASE:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/964510/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
