** Description changed: + [Impact] + LightDM reports the system compositor socket to Mir clients using the MIR_SOCKET variable. This stopped working in Mir 0.21. The Mir team says the correct variable is MIR_SERVER_HOST_SOCKET and MIR_SOCKET was a fallback to that. + + [Test Case] + 1. Start LightDM with a Mir greeter + + Expected result: + Greeter starts + + Observed result: + Mir greeter fails to start. It is attempting to access the video drivers directly (i.e. not through a compositor). + + [Regression Potential] + Risk of using LightDM with older version of Mir that doesn't support MIR_SERVER_HOST_SOCKET. Risk of behaviour change in Mir using MIR_SERVER_HOST_SOCKET. + From mir-greeter.log (and with minor instrumentation from RAOF) ERROR: QMirServer - Mir failed to start qtmir.screens: ScreenController::ScreenController qtmir.mir: MirServer created qtmir.mir: Command line arguments passed to Qt: ("/usr/bin/unity8", "--mode=greeter") ERROR: /home/josh/Documents/mir/verbose-error-for-vt-finding/src/server/graphics/default_configuration.cpp(133): Throw in function mir::DefaultServerConfiguration::the_graphics_platform()::<lambda()> Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> > std::exception::what: Exception while creating graphics platform ERROR: /home/josh/Documents/mir/verbose-error-for-vt-finding/src/platforms/mesa/server/kms/linux_virtual_terminal.cpp(238): Throw in function int mir::graphics::mesa::LinuxVirtualTerminal::find_active_vt_number() Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> > std::exception::what: Failed to find the current VT. Tried: - /dev/tty0: - Failed to open read-only: Permission denied - Failed to open write-only: Permission denied - /dev/tty: - Failed to open read-only: No such device or address - Failed to open write-only: No such device or address + /dev/tty0: + Failed to open read-only: Permission denied + Failed to open write-only: Permission denied + /dev/tty: + Failed to open read-only: No such device or address + Failed to open write-only: No such device or address - - This occurs when trying to start the unity8 greeter under unity system compositor + This occurs when trying to start the unity8 greeter under unity system + compositor
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583624 Title: Mir cannot open a tty when started by lightdm To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1583624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs