Unity8 crashes with SIGSEGV in qtmir::MirSurface::onCloseTimedOut () at ./src/modules/Unity/Application/mirsurface.cpp:917

Bug #1646648 reported by errors.ubuntu.com bug bridge
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Won't Fix
High
Michał Sawicz
qtmir (Ubuntu)
Won't Fix
High
Unassigned
unity8 (Ubuntu)
Won't Fix
High
Unassigned

Bug Description

The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with package version 8.15+17.04.20161116.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/ded3a210b92755ec7de56b1bb4097103984eb123 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The stack seems to mention QLightDM and Greeter too.

summary: - /usr/bin/unity8:11:qtmir::MirSurface::onCloseTimedOut:QtPrivate::QSlotObjectBase::call:QMetaObject::activate:QtPrivate::QSlotObjectBase::call:QMetaObject::activate
+ Unity8 crashes with SIGSEGV in qtmir::MirSurface::onCloseTimedOut () at
+ ./src/modules/Unity/Application/mirsurface.cpp:917
Changed in qtmir (Ubuntu):
importance: Undecided → High
Changed in unity8 (Ubuntu):
importance: Undecided → High
Changed in canonical-devices-system-image:
importance: Undecided → High
tags: added: unity8-desktop
Revision history for this message
kevin gunn (kgunn72) wrote :

we may want to reduce this to medium, if this isn't going to directly effect u8 on classic desktop for a while

Changed in canonical-devices-system-image:
assignee: nobody → Michał Sawicz (saviq)
milestone: none → u8c-1
Revision history for this message
Albert Astals Cid (aacid) wrote :

Is this "fixed" ?

If you look at https://errors.ubuntu.com/problem/ded3a210b92755ec7de56b1bb4097103984eb123 all the "new" reports are either from 15.04+armhf (i.e phone) running an "old" version (20161114) or amd64 also running an "old" version (20160922).

The first one i can find that is "new-ish" is
December 27, 2016 using 8.15+17.04.20161207.1-0ubuntu1

So maybe we have fixed it since and that's why no other 17.04 version crash has happened?

Revision history for this message
Brian Murray (brian-murray) wrote :

It certainly looks like but if it is fixed it'd be good to get that fix in 16.10 which still seems affected by the bug.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Are we maintaining Unity8 on 16.10 at all?

Unity8 for yakkety is 5 months out of date. I thought we were developing for 17.04 only...?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Incomplete. This crash hasn't been seen on zesty since unity8 8.15+17.04.20161207.1-0ubuntu1

Changed in canonical-devices-system-image:
status: New → Incomplete
Changed in qtmir (Ubuntu):
status: New → Incomplete
Changed in unity8 (Ubuntu):
status: New → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote : Re: [Bug 1646648] Re: Unity8 crashes with SIGSEGV in qtmir::MirSurface::onCloseTimedOut () at ./src/modules/Unity/Application/mirsurface.cpp:917

On Wed, Mar 22, 2017 at 02:20:15AM -0000, Daniel van Vugt wrote:
> Are we maintaining Unity8 on 16.10 at all?

It's in the official archive of Ubuntu so that implies that it should be
maintained. If it wasn't something being maintained then it should be in
a PPA.

--
Brian Murray

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I agree in general. However from a practical point of view we don't have the resources to keep yakkety up to date with the latest development, and it's also an inappropriate thing to do for a stable release anyway.

Unity8 was still too feature-incomplete in yakkety so it's unrealistic to expect all future development to get backported to it. Even bug fixes. It's so incomplete in yakkety that just fixing a crash or two doesn't really help people.

Revision history for this message
Michał Sawicz (saviq) wrote :

Yeah I agree, especially since this would require us dig through what actually caused this fix.

Changed in canonical-devices-system-image:
status: Incomplete → Won't Fix
Changed in qtmir (Ubuntu):
status: Incomplete → Won't Fix
Changed in unity8 (Ubuntu):
status: Incomplete → Won't Fix
Changed in canonical-devices-system-image:
milestone: u8c-1 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.