Oxide-based containers don't work in the guest session
Bug #1306560 reported by
David Barth
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lightdm (Ubuntu) |
Fix Released
|
High
|
Jamie Strandboge |
Bug Description
There is a security mechanism preventing webapp-container from working in the guest-session. The webview never gets displayed and it is then impossible to stop the guest session, because the oxide processes seem to be locked.
Related branches
Changed in lightdm (Ubuntu): | |
assignee: | nobody → Jamie Strandboge (jdstrand) |
importance: | Undecided → High |
status: | New → Triaged |
no longer affects: | oxide |
Changed in lightdm (Ubuntu): | |
status: | Triaged → In Progress |
Changed in lightdm (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
This bug was fixed in the package lightdm - 1.10.0-0ubuntu3
---------------
lightdm (1.10.0-0ubuntu3) trusty; urgency=medium
* debian/ patches/ 06_apparmor_ chromium_ updates. patch: allow oxide based
browsers and Google Chrome to run in the guest session
- LP: #1298021
- LP: #1306560
-- Jamie Strandboge <email address hidden> Fri, 11 Apr 2014 09:24:09 -0500