touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

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.

** Also affects: mir
   Importance: Undecided
       Status: New

** Summary changed:

- /usr/bin/unity8:11:assign:set_error:MirConnection::MirConnection:make_unique:connect
+ unity8 crashed with SIGSEGV: assign → set_error → MirConnection → MirConnection → make_unique → connect

** Changed in: mir
   Importance: Undecided => High

** Changed in: mir (Ubuntu)
   Importance: Undecided => High

** Changed in: mir
    Milestone: None => 0.16.0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1487649

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

Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1487649/+subscriptions