** Changed in: unity-system-compositor (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
** Changed in: unity-system-compositor
Status: In Progress => Fix Released
--
You received this bug
** Changed in: mir/0.20
Status: New => Fix Released
** Changed in: mir/0.20
Importance: Undecided => Critical
** Changed in: mir/0.20
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: mir
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
Title:
unity-system-compositor crashed with std::runtime_error in
This bug was fixed in the package mir - 0.20.0+16.04.20160219-0ubuntu1
---
mir (0.20.0+16.04.20160219-0ubuntu1) xenial; urgency=medium
[ Alan Griffiths ]
* New upstream release 0.20.0 (https://launchpad.net/mir/+milestone/0.20.0)
- ABI summary: Only servers need rebuilding;
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Committed
** Changed in: canonical-devices-system-image
Milestone: ww04-2016 => 9.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mir/0.19
Milestone: None => 0.19.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
Title:
unity-system-compositor crashed with std::runtime_error in
Fix landed in 0.19.2
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
Title:
unity-system-compositor crashed with
** Also affects: mir/0.19
Importance: Undecided
Status: New
** Also affects: mir/0.20
Importance: Undecided
Status: New
** Changed in: mir/0.19
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: unity-system-compositor
Milestone: None => 0.4.1
** Changed in: unity-system-compositor
Milestone: 0.4.1 => 0.4.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
Title:
OK, we've made a point release of mir 0.19.1 and unity-system-compositor 0.4.1
which are now in the stable overlay.
Which means will be built into the next image and available on the rc-proposed
channel.
Also, this should make it into the OTA9.5 release.
If you update and know you are on these
** Changed in: unity-system-compositor
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
Title:
unity-system-compositor crashed with
Fix committed into lp:unity-system-compositor at revision 274, scheduled
for release in unity-system-compositor, milestone Unknown
** Changed in: unity-system-compositor
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
We're needing more data on this bug, and we're going to eventually land
the MP's to improve some reporting.
But this bug is critical, and we'd like to get information as soon as possible.
_Only_ if you are willing to risk not getting autoupdates (and have to flash
your phone in future) - you can
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.20.0
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't think that was a fix that landed. Just some helpful progress.
** Changed in: mir
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
Title:
** Changed in: canonical-devices-system-image
Milestone: ww08-2016 => ww04-2016
** Changed in: canonical-devices-system-image
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Digging into the code (without being able to reproduce) the likeliest
cause seems to be incorrect error handling in
mir::compositor::CompositingFunctor::operator()().
In Mir 0.18 this function can plausibly terminate via an exception
before setting the promise (on line 116) - it has a catch
** Branch linked: lp:~alan-griffiths/mir/better-error-reporting-in-
MultiThreadedCompositor-start
** Changed in: mir
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
** Changed in: unity-system-compositor
Assignee: (unassigned) => Alan Griffiths (alan-griffiths)
** Changed
** Branch linked: lp:~alan-griffiths/unity-system-compositor/report-
warnings-instead-of-crashing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
Title:
unity-system-compositor crashed with
Note:
lp:~alan-griffiths/mir/better-error-reporting-in-MultiThreadedCompositor-start
lp:~alan-griffiths/unity-system-compositor/report-warnings-instead-of-crashing
These linked branches may not be a full solution but:
1. they log the underlying problem (which is "eaten" by bad error
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-system-compositor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mir (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/1528384
Title:
Got this crash over the week-end on my krillin running the latest rc-proposed.
I got a phone call, grabbed the phone from inside my jacket, but I was never
able to answer it as the screen remained blank.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't think MultiThreadedCompositor::start()/stop() locking is the
real issue. They are only called by MirScreen's "*_l()" functions which
(if I understand the convention correctly) should only be invoked under
lock of its mutex.
However, usc::MirScreen::power_off_alarm_notification() calls
Actually, I've misunderstood. power_off_alarm_notification() is only
called from MirScreen::PowerOffLockableCallback - which acquires the
lock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
** Changed in: canonical-devices-system-image
Milestone: ww04-2016 => ww08-2016
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528384
Title:
unity-system-compositor crashed with
** Summary changed:
- unity-system-compositor crashed with std::runtime_error in
mir::compositor::CompositingFunctor::wait_until_started()
+ unity-system-compositor crashed with std::runtime_error in
mir::compositor::CompositingFunctor::wait_until_started() from
Looking at the stack traces, it seems to generally happen on phones when
the screen tries to turn on due to a proximity event from dbus/powerd.
The only reasonable explanation I can find is due to the fact that
MultiThreadedCompositor::start/stop() are not locked. Instead they use
atomic
28 matches
Mail list logo
