unity8 crashed with SIGSEGV: assign → set_error → MirConnection → MirConnection → make_unique → connect

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.10+15.10.20150804-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/073572aa56ec6f7f15553fe0287e99fb791097df contains more details.

[Daniel van Vugt (vanvugt)]

Seems to be a simple matter of this==NULL

#0 0xb38f6582 in assign (__s=0xb3926aa0 "connect not called", this=0x0) at /usr/include/c++/5/bits/basic_string.h:1166
No locals.
#1 set_error (value=0xb3926aa0 "connect not called", this=0xb140c970) at /build/mir-zugpY3/mir-0.15.0+15.10.20150818/obj-arm-linux-gnueabihf/src/protobuf/mir_protobuf.pb.h:8801
No locals.
#2 MirConnection::MirConnection (this=0xb140c258, conf=...) at /build/mir-zugpY3/mir-0.15.0+15.10.20150818/src/client/mir_connection.cpp:130
No locals.

[Cemil Azizoglu (cemil-azizoglu)]

Looks like an isolated protobuf lib error to me. Hasn't happened in almost 3 months.

[Albert Astals Cid (aacid)]

Agree with Cemil we could probably close it if it since it hasn't happened again

[Daniel van Vugt (vanvugt)]

For a bug to expire, all tasks must be set to Incomplete and Unassigned.

[Launchpad Janitor (janitor)]

[Expired for mir (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for Mir because there has been no activity for 60 days.]