Although the offending exception might have been a regression from:
------------------------------------------------------------
revno: 2870 [merge]
author: Kevin DuBois <[email protected]>
committer: Tarmac
branch nick: development-branch
timestamp: Fri 2015-08-21 14:52:44 +0000
message:
client: Do some internal refactoring to separate out mcl::BufferStream's
logic that ties it to the BufferDepository. If the client gets a buffer at
creation, it will use the exchange based system. If not, it will keep the
current behavior of throwing an exception.
.
Approved by PS Jenkins bot, Alan Griffiths, Chris Halse Rogers, Alexandros
Frantzis.
------------------------------------------------------------
We probably don't have to fix it directly... Because Mir 0.24.0 aims to
avoid this old code path for good, and you shouldn't ever hit it again.
** Changed in: mir
Milestone: 0.25.0 => 0.24.0
** Changed in: mir
Status: Confirmed => Fix Committed
** Changed in: mir
Assignee: (unassigned) => Kevin Dubois (kevin-dubois05)
** Changed in: mir (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
unity8/libmirclient gives up and terminates prematurely with
"std::exception::what: disconnected: no new buffers" via
ExchangeSemantics::submit()
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
