[Bug 1634508] Re: Clients cannot connect when MIR_SOCKET=""

[jim dan]

** Also affects: debconf (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1634508

Title:
  Clients cannot connect when MIR_SOCKET=""

Status in Mir:
  Fix Released
Status in debconf package in Ubuntu:
  New
Status in mir package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Launch a Unity 8 desktop session, log out, then log into a Unity 7
  session. Launch a Mir-on-X shell like MirAL and then try to launch a
  Mir client like mir_demo_client_egltriangle. The client will refuse to
  connect.

  Unity 8's upstart script always sets MIR_SOCKET to its old value when
  the session ends. If MIR_SOCKET wasn't set, then the post-stop script
  will still set MIR_SOCKET, setting it to "". Mir should interpret this
  as if MIR_SOCKET were unset.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1634508/+subscriptions