Certainly seems like a spurious value of $MIR_SOCKET. So Mir itself
isn't doing anything wrong *
* Except that, I would argue, occasions like this call for error
messages rather than exceptions leading to bug reports. It's not
something that should have made it to the Mir bug tracker really.
Although it's now useful that it did.
** Changed in: mir
Milestone: 0.8.0 => None
** Changed in: mir
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1355892
Title:
terminate called (uncaught exception) from
DefaultServerConfiguration::the_host_connection()
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1355892/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
