Mir

Comment 0 for bug 1661295

Revision history for this message
Gerry Boland (gerboland) wrote : [vmware] mir 0.26 failing with nested server in protobuf when bringing up NestedDisplay

Setup:
1. VMWare 12, with the following line added to ~/.vmware/preferences:
      mks.gl.allowBlacklistedDrivers = "TRUE"
2. Created a VM with Xenial + Overlay PPA
3. Installed unity8-desktop-session-mir, rebooted
4. Tried to log in to a Unity8 session

Problem: Unity8 fails to start, but is exiting cleanly as opposed to crashing. The following is all that is printed of the log:

[2017-02-02:07:18:21.137] qtmir.screens: ScreensModel::ScreensModel
[2017-02-02 07:18:21.143261] mirplatform: Found graphics driver: mir:mesa-kms (version 0.26.0)
[2017-02-02 07:18:21.143413] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.26.0)
[2017-02-02 07:18:21.144063] mirserver: Starting
[libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK failed: (index) >= (0):
[2017-02-02:07:18:21.165] CHECK failed: (index) >= (0):
initctl: No such variable: UNITY_MIR_SOCKET

USC is coming up correctly however.

If I try to launch miral-shell manually, I get similar error:

MIR_SOCKET=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_PROMPT_FILE=1 MIR_SERVER_HOST_SOCKET=/run/mir_socket MIR_SERVER_FILE=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_NAME=session-0 miral-shell
[2017-02-02 07:55:56.686669] mirplatform: Found graphics driver: mir:mesa-kms (version 0.26.0)
[2017-02-02 07:55:56.687395] mirplatform: Found graphics driver: mir:mesa-x11 (version 0.26.0)
[2017-02-02 07:55:56.689036] mirserver: Starting
[libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK failed: (index) >= (0):
ERROR: Dynamic exception type: google::protobuf::FatalException
std::exception::what: CHECK failed: (index) >= (0):

I tried to grab a backtrace at the location of the last call to /usr/include/google/protobuf/repeated_field.h:885 which might print the error:

http://pastebin.ubuntu.com/23911595/