** Also affects: lightdm-gtk-greeter (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: lightdm-gtk-greeter (Ubuntu)
       Status: New => Fix Released

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.

  [PATCH] Accessibility partly broken due to X root window being kept
  from login session.

Status in LightDM GTK+ Greeter:
  Fix Released
Status in lightdm-gtk-greeter package in Ubuntu:
  Fix Released
Status in unity-greeter package in Ubuntu:

Bug description:
   affects lightdm

  Lightdm version 1.21.5, in 17.04. Some components of the Unity and
  Mate desktops are currently not accessible when logging in using
  lightdm. So far I've tested and reproduced this problem with both
  unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I
  mentioned in the title, i.e the X root window is kept around.

  At-spi gets loaded in the greeter for use with Orca. At-spi ads a
  property atom, AT_SPI_BUS, to the root X window to allow software to
  be able to find the accessibility bus. If my understanding is correct,
  this root window is kept around for the user login session. What then
  happens is software either using Qt or Gtk loads its accessibility
  support code, which in turn looks for the AT_SPI_BUS property.
  Normally on session load, this property is not present, at which point
  the support code then connects to org.a11y.bus, which in turn via
  systemd loads the at-spi bus launcher and registry to respond to the
  bus activation/request. At-spi adds the AT_SPI_BUS property to the X
  root window at load.

  However the AT_SPI_BUS property is hanging around from the greeter
  session, which is confusing software. At-spi only then gets loaded
  from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome
  session binaries, but this happens after unity-panel-service and mate-
  panel are loaded. As such they are inaccessible for the session, or
  until the user kills them and they get reloaded.

To manage notifications about this bug go to:

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

Reply via email to