** Changed in: mir
Milestone: None = 0.7.0
** Changed in: mir
Status: Fix Released = Fix Committed
--
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/1347053
Title:
Sorry for the confusion. Most of the 0.7.0 series got merged into 0.6.0
at a late stage. I've verified everything in 0.6.0 is also fixed in
0.7.0. So although the branched fixes in 0.7.0 have not been released
yet, the equivalent fixes in 0.6.0 have. No need to mention them in 0.7
any more.
**
** Changed in: mir/0.6
Status: Fix Committed = Fix Released
--
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/1347053
Title:
Clients are crashing with a fatal exception
mir (0.6.0+14.10.20140811-0ubuntu1) utopic; urgency=medium
** Changed in: mir (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
Oh dear.
Fix backported to lp:mir/0.6 at revision 1826.
** Changed in: mir/0.6
Milestone: 0.6.1 = 0.6.0
** Changed in: mir/0.6
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir
Fix committed into lp:mir/devel at revision None, scheduled for release
in mir, milestone Unknown
** Changed in: mir
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Changed in: mir/0.6
Milestone: None = 0.6.1
--
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/1347053
Title:
Clients are crashing with a fatal exception in
** Branch linked: lp:~afrantzis/mir/fix-1347053
--
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/1347053
Title:
Clients are crashing with a fatal exception in
As I mentioned before, the failures shown in both the errors.u.c reports
(and which are really confusing, I don't really trust the backtraces to
be correct there, they don't make much sense) and the original
backtrace, just indicate that that the server has died and the clients
fail to communicate
** Changed in: mir
Assignee: (unassigned) = Alexandros Frantzis (afrantzis)
** Changed in: mir
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
It looks like this broken unit test is the same bug
https://bugs.launchpad.net/mir/+bug/1164838
** Tags added: qasoak
--
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/1347053
another report from errors.u.c https://bugs.launchpad.net/ubuntu/+source
/messaging-app/+bug/1350486
--
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/1347053
Title:
Clients are
The whole UI is hung when this happens.
** Tags added: qa-daily-testing rtm14
--
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/1347053
Title:
Clients are crashing with a fatal
** Changed in: mir
Milestone: 0.6.0 = 0.7.0
** Also affects: mir/0.6
Importance: Undecided
Status: New
** Changed in: mir/0.6
Importance: Undecided = High
** Changed in: mir/0.6
Status: New = Triaged
** Changed in: mir/0.6
Milestone: None = 0.6.0
--
You received
** Changed in: mir/0.5
Status: Triaged = Won't Fix
** Changed in: mir/0.5
Milestone: 0.5.1 = None
--
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/1347053
Title:
My understanding of the traces: the clients are failing because the
server has crashed (or is otherwise unreachable). The problem seems to
be that the failure happens in the context of a callback from the
Android driver which presumably doesn't handle C++ exceptions well
(probably not at all),
Report in errors.u.c:
https://errors.ubuntu.com/problem/4516e6922810983409f4f3aa7df79aa7b97f87b3
--
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/1347053
Title:
Clients are
Sorry, my mistake. It's clients that are crashing, not the server.
That's more severe. See also duplicate bug 1347901 where ubuntu-system-
settings is crashing in the same way.
** Summary changed:
- unity-system-compositor-spinner crashed with a fatal exception in
18 matches
Mail list logo
