** Changed in: canonical-devices-system-image
Milestone: u8c-1 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1646648
Title:
Unity8 crashes with SIGSEGV in
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:
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
On Wed, Mar 22, 2017 at 02:20:15AM -, 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
--
You received
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 =>
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...?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
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.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1646648
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
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: (unassigned) => Michał Sawicz (saviq)
** Changed in: canonical-devices-system-image
Milestone: None => u8c-1
--
You
The stack seems to mention QLightDM and Greeter too.
** Summary changed:
-
/usr/bin/unity8:11:qtmir::MirSurface::onCloseTimedOut:QtPrivate::QSlotObjectBase::call:QMetaObject::activate:QtPrivate::QSlotObjectBase::call:QMetaObject::activate
+ Unity8 crashes with SIGSEGV in
10 matches
Mail list logo
