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

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  [vmware] mir 0.26 failing with nested server in protobuf when bringing
  up NestedDisplay [CHECK failed: (index) >= (0)]

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to