touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #110854
[Bug 1504049] Re: apparmor rules too tight for chromium
Could you please edit also the following directive in abstractions
/lightdm_chromium-browser? I cannot close Chromium remotely with
"killall chromium" from a guest session because it's currently
disallowed to receive SIGTERM.
signal (receive, send) set=("exists", "term") peer=/usr/lib/lightdm
/lightdm-guest-session
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1504049
Title:
apparmor rules too tight for chromium
Status in Light Display Manager:
Fix Committed
Status in Light Display Manager 1.10 series:
Fix Committed
Status in Light Display Manager 1.14 series:
Fix Committed
Status in Light Display Manager 1.16 series:
Fix Committed
Status in chromium-browser package in Ubuntu:
Confirmed
Status in lightdm package in Ubuntu:
Fix Released
Status in chromium-browser source package in Trusty:
New
Status in lightdm source package in Trusty:
Triaged
Status in chromium-browser source package in Vivid:
New
Status in lightdm source package in Vivid:
Triaged
Status in chromium-browser source package in Wily:
Confirmed
Status in lightdm source package in Wily:
Fix Released
Bug description:
[Impact]
Unable to run Chromium from guest session.
[Test Case]
1. Start Ubuntu
2. From greeter select guest session
3. Load Chromium
Expected result:
Chromium runs.
Observed result:
Chromium does not run.
[Regression Potential]
Low. The change is a few additional apparmor rules. There is a low risk that the new rules might allow a guest program to access a flaw.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1504049/+subscriptions