OK, I've got a branch up that adds permission to talk to the USC
mir_socket to lightdm's apparmor profile for guests.
Bug 1593407 is indeed separate (though it also will involve editing the
guest apparmor profile). Not only can snaps not be run in a guest
session, but they aren't listed in the app drawer either, because we
can't talk to snapd.
When testing this, I also noticed a bug in unity8. The screen gets
locked due to a timeout. But the guest user can't unlock the screen.
Looking at that.
** No longer affects: unity8-desktop-session (Ubuntu)
** Changed in: lightdm (Ubuntu)
Status: Confirmed => In Progress
** Changed in: lightdm (Ubuntu)
Assignee: (unassigned) => Michael Terry (mterry)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1644237
Title:
unity8 fails to start as guest user
Status in Canonical System Image:
Triaged
Status in lightdm package in Ubuntu:
In Progress
Status in unity8 package in Ubuntu:
Incomplete
Bug description:
This is shown in unity8.log:
[2016-11-23 15:59:25.820868] mirserver: Starting
ERROR:
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/default_configuration.cpp(132):
Throw in function
mir::DefaultServerConfiguration::the_graphics_platform()::<lambda()>
Dynamic exception type:
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error>
>
std::exception::what: Exception while creating graphics platform
ERROR:
/build/mir-JY573_/mir-0.24.1+16.10.20160928/src/server/graphics/nested/mir_client_host_connection.cpp(245):
Throw in function
mir::graphics::nested::MirClientHostConnection::MirClientHostConnection(const
string&, const string&, const
std::shared_ptr<mir::shell::HostLifecycleEventListener>&)
Dynamic exception type:
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error>
>
std::exception::what: Nested Mir Platform Connection Error: Failed to connect
to server socket: Permission denied
[2016-11-23:15:59:35.820] ERROR: QMirServer - Mir failed to start
initctl: No such variable: UNITY_MIR_SOCKET
running current zesty, but I had the same problem on yakkety too.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1644237/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
