This bug was fixed in the package mir - 0.31.0.1-0ubuntu1
---
mir (0.31.0.1-0ubuntu1) bionic; urgency=medium
* New upstream release 0.31.0 (LP: #1757952)
- ABI summary:
+ mirclient ABI unchanged at 9
+ miral ABI bumped to 3
+ mirserver ABI bumped to 46
+
Ok, VMWare is setting the current crtc mode at a generic 800x600, which isn't
in the list of modes for the connected display. Only approach I see is to
compare the mode name with "preferred", for which I see prior art:
https://github.com/wayland-project/weston/blob/master/compositor/main.c#L1068
Problem is that the "real" KMS platform is unable to determine the
current mode when running on VMware, leaving the current_mode_index at
an invalid value of UINTMAX, which is being passed through to the nested
platform.
--
You received this bug notification because you are a member of Ubuntu
Bug
Syncing task from Mir.
** Changed in: mir (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661295
Title:
[vmware] mir 0.26 failing with nested server in prot