Comment 53 for bug 1532607

I'm happy to let this become another confused bug and it get closed. We have plenty of those and it's an unavoidable consequence of Launchpad's awesome openness. Managing popular bugs is often like herding cats.

There is however still absolute proof here that the original reporter hit bug 1506358 at 13:31 on 10 January, exactly when he described. Yes, there is a possibility the two bugs are related, however they will need to be kept separate now. Because bug 1506358 is known to occur on a simple Mir server that itself is not restarting or faulty.

So if anyone continues to see:
  std::exception::what: disconnected: no new buffers
please discuss that in bug 1506358 instead.