*** This bug is a duplicate of bug 1118903 ***
https://bugs.launchpad.net/bugs/1118903
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1118903, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** Summary changed:
- unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
+ unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
["Failed to schedule page flip"]
** Also affects: mir (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mir
Importance: Undecided
Status: New
** Information type changed from Private to Public
** Changed in: mir
Importance: Undecided => High
** Changed in: mir (Ubuntu)
Importance: Undecided => High
** Changed in: unity-system-compositor (Ubuntu)
Importance: Medium => High
** Summary changed:
- unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
["Failed to schedule page flip"]
+ unity-system-compositor crashes on start-up with "Mir fatal error: Failed to
schedule page flip" on VirtualBox Graphics Adapter
** This bug has been marked a duplicate of bug 1118903
[enhancement] Mir lacks a software rendering backend
--
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 crashes on start-up with "Mir fatal error:
Failed to schedule page flip" on VirtualBox Graphics Adapter
Status in Mir:
New
Status in mir package in Ubuntu:
New
Status in unity-system-compositor package in Ubuntu:
New
Bug description:
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/mir/+bug/1584894/+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
