Public bug reported: The current XMir support works by running "X -mir <id> -mirSocket <socket>". The new XMir has a separate binary "Xmir" that should be run instead of "X".
We should use "Xmir" if it is available. ** Affects: lightdm Importance: Medium Status: Fix Released ** Affects: lightdm/1.10 Importance: Medium Status: Fix Committed ** Affects: lightdm/1.12 Importance: Medium Status: Fix Committed ** Affects: lightdm/1.14 Importance: Medium Status: Fix Committed ** Affects: lightdm (Ubuntu) Importance: Medium Status: Fix Released ** Affects: lightdm (Ubuntu Trusty) Importance: Medium Status: Triaged ** Affects: lightdm (Ubuntu Utopic) Importance: Medium Status: Triaged ** Affects: lightdm (Ubuntu Vivid) Importance: Medium Status: Triaged ** Affects: lightdm (Ubuntu Wily) Importance: Medium Status: Fix Released ** Changed in: lightdm Status: New => Fix Released ** Changed in: lightdm Milestone: None => 1.15.0 ** Changed in: lightdm Importance: Undecided => Medium ** Also affects: lightdm/1.12 Importance: Undecided Status: New ** Also affects: lightdm/1.10 Importance: Undecided Status: New ** Also affects: lightdm/1.14 Importance: Undecided Status: New ** Changed in: lightdm/1.10 Status: New => Fix Committed ** Changed in: lightdm/1.12 Status: New => Fix Committed ** Changed in: lightdm/1.14 Status: New => Fix Committed ** Changed in: lightdm/1.12 Importance: Undecided => Medium ** Changed in: lightdm/1.10 Importance: Undecided => Medium ** Changed in: lightdm/1.14 Importance: Undecided => Medium ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Wily) Status: New => Fix Released ** Changed in: lightdm (Ubuntu Wily) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu Vivid) Importance: Undecided => Medium ** Changed in: lightdm/1.14 Milestone: None => 1.14.1 ** Also affects: lightdm (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: lightdm (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu Utopic) Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu Vivid) Status: New => Triaged ** Changed in: lightdm (Ubuntu Utopic) Status: New => Triaged ** Changed in: lightdm (Ubuntu Trusty) Status: New => Triaged ** Changed in: lightdm/1.10 Milestone: None => 1.10.6 ** Changed in: lightdm/1.12 Milestone: None => 1.12.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1458696 Title: Doesn't work with new Xmir binary name Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.12 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Utopic: Triaged Status in lightdm source package in Vivid: Triaged Status in lightdm source package in Wily: Fix Released Bug description: The current XMir support works by running "X -mir <id> -mirSocket <socket>". The new XMir has a separate binary "Xmir" that should be run instead of "X". We should use "Xmir" if it is available. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1458696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp