touch-packages team mailing list archive

[Hadmut Danisch <hadmut@xxxxxxxxxx>]

# dpkg -S $(grep -l -r chromium /etc/apparmor.d/)
dpkg-query: no path found matching pattern /etc/apparmor.d/abstractions/ubuntu-browsers.d/chromium-browser
evince-common: /etc/apparmor.d/abstractions/evince
lightdm: /etc/apparmor.d/abstractions/lightdm
apparmor: /etc/apparmor.d/abstractions/private-files-strict
apparmor: /etc/apparmor.d/abstractions/ubuntu-browsers
apparmor: /etc/apparmor.d/abstractions/ubuntu-helpers
lightdm: /etc/apparmor.d/abstractions/lightdm_chromium-browser
dpkg-query: no path found matching pattern /etc/apparmor.d/cache/usr.bin.chromium-browser
dpkg-query: no path found matching pattern /etc/apparmor.d/cache/lightdm-guest-session
dpkg-query: no path found matching pattern /etc/apparmor.d/local/usr.bin.chromium-browser
lightdm: /etc/apparmor.d/lightdm-guest-session
apparmor-profiles: /etc/apparmor.d/usr.bin.chromium-browser

-- 
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