Thanks Daniel for working on this!
I've tried the silo in zesty, and I still cannot get past a black
screen. In the unity8 log I have:
==================
[2016-11-15:09:37:52.997] qtmir.screens: ScreensModel::ScreensModel
[2016-11-15:09:37:53.026] qtmir.mir: MirServer created
[2016-11-15:09:37:53.026] qtmir.mir: Command line arguments passed to Qt:
("unity8", "--mode=full-shell")
[2016-11-15 09:37:53.390037] mirserver: Starting
ERROR:
/build/mir-FMihxs/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-FMihxs/mir-0.24.1+16.10.20160928/src/common/sharedlibrary/shared_library.cpp(65):
Throw in function void* mir::SharedLibrary::load_symbol(const char*, const
char*) const
Dynamic exception type:
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error>
>
std::exception::what:
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.11:
undefined symbol: create_guest_platform, version MIR_GRAPHICS_PLATFORM_0.24
[2016-11-15:09:38:03.390] ERROR: QMirServer - Mir failed to start
initctl: No such variable: UNITY_MIR_SOCKET
==================
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1584894
Title:
unity-system-compositor (or any Mir server) crashes on start-up with
"Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics
Adapter and QEMU
Status in Canonical System Image:
Confirmed
Status in Mir:
Fix Committed
Status in mir package in Ubuntu:
Confirmed
Bug description:
(separated from bug 1118903)
unity-system-compositor crashes on start-up with "Mir fatal error: Failed to
schedule page flip" on VirtualBox Graphics Adapter
---
can not login to Unity8
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: unity-system-compositor 0.4.3+16.04.20160323-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
Date: Mon May 23 19:20:43 2016
ExecutablePath: /usr/sbin/unity-system-compositor
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-05-19 (3 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160519)
ProcCmdline: /usr/sbin/unity-system-compositor
--disable-inactivity-policy=true --on-fatal-error-abort --file
/run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8
ProcEnviron:
Signal: 6
SourcePackage: unity-system-compositor
StacktraceTop:
mir::fatal_error_abort(char const*, ...) () from
/usr/lib/x86_64-linux-gnu/libmircommon.so.5
?? () from
/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.8
?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38
?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Title: unity-system-compositor crashed with SIGABRT in
mir::fatal_error_abort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
version.libdrm: libdrm2 2.4.68-1
version.lightdm: lightdm 1.19.0-0ubuntu1
version.mesa: libegl1-mesa-dev N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584894/+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
