** 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/1661508
Title:
[regression] Nested server segfaults or rapidly logs exceptions when a
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2818
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661508
Title:
[regression] Nested server segfaults or rapidly logs exceptions when a
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-artful-2806
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661508
Title:
[regression] Nested server segfaults or rapidly logs exceptions when a
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661508
Title:
[regression] Nested server segfaults or rapidly logs exceptions when a
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-xenial-2736
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-yakkety-2783.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661508
Title:
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2683
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661508
Title:
[regression] Nested server segfaults or rapidly logs exceptions when a
** Changed in: mir/0.26
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/1661508
Title:
[regression] Nested server segfaults or rapidly logs exceptions
This bug was fixed in the package mir - 0.26.1+17.04.20170209.1-0ubuntu1
---
mir (0.26.1+17.04.20170209.1-0ubuntu1) zesty; urgency=medium
* New upstream release 0.26.1 (https://launchpad.net/mir/+milestone/0.26.1)
- ABI summary:
. mirclient ABI unchanged at 9
.
Fix committed to lp:mir/0.26 at revision 4007, scheduled for release in
Mir 0.26.1
** Changed in: mir/0.26
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mir
Assignee: (unassigned) => Kevin DuBois (kdub)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661508
Title:
[regression] Nested server segfaults or rapidly logs exceptions
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2435
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661508
Title:
[regression] Nested server segfaults or rapidly logs exceptions when a
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 1.0.0
** Changed in: mir
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:mir/0.26
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661508
Title:
[regression] Nested server segfaults or rapidly logs exceptions when a
fullscreen client starts [in
Why this crashes sometimes and other times spams is that wait_for_all()
is sometimes called on a nullptr MirWaitHandle. The first thing that fn
does is grab a lock. Some libc's seem smart enough to recognize that the
memory isn't there and throw system_error, but its pretty conceivable
that this
yep, was the removal-of waithandle MP. needed some more checks before
waiting for interval configuration.
** Changed in: mir/0.26
Assignee: (unassigned) => Kevin DuBois (kdub)
** Changed in: mir/0.26
Status: Triaged => In Progress
** Branch linked: lp:~kdub/mir/fix-1661508
--
You
As a workaround on zesty (0.26.0) you can use --nested-passthrough=OFF
However that workaround stops being useful in lp:mir and lp:mir/0.26
because it will trigger bug 1661521.
** Description changed:
Nested server segfaults when a fullscreen client starts
Using Mir 0.26.0 (zesty
Bisected somewhat. The flood of exceptions started here:
revno: 3982 [merge]
author: Brandon Schaefer
committer: Cemil Azizoglu
branch nick: mir
timestamp: Tue 2017-01-24
** Summary changed:
- Nested server segfaults or rapidly logs exceptions when a fullscreen client
starts [in mir_presentation_chain_set_dropping_mode ... std::exception::what:
Operation not permitted]
+ [regression] Nested server segfaults or rapidly logs exceptions when a
fullscreen client
18 matches
Mail list logo