[Bug 1556321] Re: unity8 crashed with SIGSEGV in deref() from qtmir::serializeMimeData()

** Also affects: qtmir Importance: Undecided Status: New ** Changed in: qtmir Status: New => Confirmed ** Changed in: qtmir Importance: Undecided => High ** Changed in: qtmir (Ubuntu) Importance: Undecided => High ** Summary changed: - unity8 crashed with SIGSEGV in

[Bug 1556321] Re: unity8 crashed with SIGSEGV in deref() from qtmir::serializeMimeData()

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556321 Title:

[Bug 1556321] Re: unity8 crashed with SIGSEGV in deref() from qtmir::serializeMimeData()

Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtmir (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556321 Title:

[Bug 1556321] Re: unity8 crashed with SIGSEGV in deref()

That kind of stack trace confusion sometimes means some private/local/inline function has been called. And it shows the nearest public function instead. ** Also affects: mir Importance: Undecided Status: New ** Summary changed: - unity8 crashed with SIGSEGV in deref() + unity8 crashed

[Bug 1556321] Re: unity8 crashed with SIGSEGV in deref()

The ThreadStacktrace looks weird #2 qtmir::serializeMimeData (mimeData=0x7f8849398f30 ::operator()(MirDisplayOutput &) const+656>) at