Mir

Activity log for bug #1661295

Date Who What changed Old value New value Message
2017-02-02 15:58:20 Gerry Boland bug added bug
2017-02-03 01:33:45 Daniel van Vugt tags regression
2017-02-03 01:34:06 Daniel van Vugt summary [vmware] mir 0.26 failing with nested server in protobuf when bringing up NestedDisplay [vmware] mir 0.26 failing with nested server in protobuf when bringing up NestedDisplay [CHECK failed: (index) >= (0)]
2017-02-03 01:34:15 Daniel van Vugt mir: milestone 1.0.0
2017-02-03 01:34:27 Daniel van Vugt mir: importance Undecided High
2017-02-03 13:31:12 Cemil Azizoglu mir: milestone 1.0.0 0.26.1
2017-02-03 20:07:20 Cemil Azizoglu mir: milestone 0.26.1 1.0.0
2017-02-07 04:20:33 Daniel van Vugt description 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/ 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/ Thread 4 "MirServerThread" hit Breakpoint 1, mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*) const (this=0x7fffd804f7a0, output=0x7fffe0848280) at /build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417 8417 in /build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc #0 mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*) const (this=0x7fffd804f7a0, output=0x7fffe0848280) at /build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417 #1 0x00007fffeba5c3e8 in mir::protobuf::DisplayConfiguration::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*) const (this=0x7fffd804b830, output=0x7fffe0848280) at /build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:11436 #2 0x00007fffeb38a615 in google::protobuf::MessageLite::SerializeWithCachedSizesToArray(unsigned char*) const () from /usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.9 #3 0x00007fffed696798 in mir_blob_from_display_config () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9 #4 0x00007fffed1d7ec6 in copy_config (conf=<optimized out>) at /build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:44 #5 __base_ctor (other=warning: RTTI symbol not found for class 'mir::graphics::nested::NestedDisplayConfiguration' ..., this=0x7fffd8047300) at /build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:61
2017-04-03 03:07:45 Daniel van Vugt mir: milestone 0.27.0 0.28.0
2017-11-03 15:24:05 Michał Sawicz mir (Ubuntu): importance Undecided High
2018-03-24 09:32:46 Launchpad Janitor mir (Ubuntu): status New Fix Released