group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1583624@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package lightdm - 1.18.2-0ubuntu1

---------------
lightdm (1.18.2-0ubuntu1) xenial; urgency=medium

  * New upstream release:
    - Don't quit on SIGUSR1, SIGUSR2 or SIGHUP (LP: #960157)
    - Use MIR_SERVER_HOST_SOCKET instead of MIR_SOCKET to report compositor
      socket to sessions. This used to work but no longer works in Mir 0.21
      (LP: #1583624)
    - Use only a single compositor on xlocal seats (LP: #1594229)
    - Fix Mir greeter log filename having "(null)" in the name (LP: #1590582)
    - Set XDMCP hostname field in to system hostname or configured value
      (LP: #1578442)
    - Improve XDMCP IPv6 address selection (LP: #1575200)
    - Allow fcitx and mozc to run in guest session (LP: #1509829)
    - Fix uninitialized memory errors
  * debian/lightdm.dirs:
    - Ensure user configuration directories /etc/lightdm/lightdm.conf.d and
      /etc/guest-session exist
  * debian/guest-account.sh:
  * debian/guest-session-setup.sh:
    - Source prefs.sh as privileged user to allow user modification
      (LP: #1581853)

 -- Robert Ancell <robert.ancell@xxxxxxxxxxxxx>  Tue, 21 Jun 2016
12:49:01 +1200

** Changed in: lightdm (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1583624

Title:
  Mir cannot open a tty when started by lightdm

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.18 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Xenial:
  Fix Released

Bug description:
  [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

  This occurs when trying to start the unity8 greeter under unity system
  compositor

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