[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
** Tags added: a11y -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [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: Fix Released 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
This bug was fixed in the package unity-greeter - 18.04.0+19.04.20190410-0ubuntu1 --- unity-greeter (18.04.0+19.04.20190410-0ubuntu1) disco; urgency=medium [ Khurshid Alam ] * src/list-stack.vala: Fix build with vala 0.43.x [ Luke Yelavich ] * Remove at-spi load/kill code (LP: #1670933) -- Marco Trevisan (Treviño) Wed, 10 Apr 2019 17:34:35 + ** Changed in: unity-greeter (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [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: Fix Released 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
** 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. https://bugs.launchpad.net/bugs/1670933 Title: [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: Confirmed 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
** Changed in: lightdm-gtk-greeter Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: Fix Released Status in unity-greeter package in Ubuntu: Confirmed 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
** Changed in: lightdm-gtk-greeter Milestone: None => 2.0.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: Fix Committed Status in unity-greeter package in Ubuntu: Confirmed 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
Applied Samuel Thibault's patch to master, which seems like a safe solution benefiting the most users. ** Changed in: lightdm-gtk-greeter Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: Fix Committed Status in unity-greeter package in Ubuntu: Confirmed 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
** Branch linked: lp:~samuel-thibault/lightdm-gtk-greeter/at-spi-bus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
I have pushed the AT_SPI_BUS removal patch to branch https://code.launchpad.net/~samuel-thibault/lightdm-gtk-greeter/at-spi- bus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
Hello, Still now news on this and #1366534 ? This is really hurting users... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
Hello, Looking at the patches I can see removal of at-spi2-bus-launcher related code however I am unable to see a fix related to cleaning up the X window root.Thus if the only patch to gtk-greeter is committed I am afraid it will leave us with broken a11y within the user session. Or should I be also looking elsewhere to see all the related activity? I would say this is a good move prone to all kinds of various possible setups however before removing ability to spawn at-spi2-bus-launcher we should make sure there are no traces of it when it's being started by something else e.g. by orca when called with orca --replace or by GTK as part of its ATK module. Again this only handles the case when at-spi2 is activated via systemd. So to sumarize all the recent a11y related spam that has popped up recently: These patches are only suitable for distros where at-spi is activated via systemd. For systemd less distros the patch proposed by Samuel Thibauld at the LP #1366534 is so far the working solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
Hello, Just to confirm that the approch proposed by Luke is sound. Removing the AT_SPI_BUS property would really be the safest for the user session: even if systemd doesn't manage to properly clean the at-spi dbus, at least the session isn't exposed to its existence. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
[Desktop-packages] [Bug 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
** Summary changed: - Accessibility partly broken due to X root window being kept from login session. + [PATCH] Accessibility partly broken due to X root window being kept from login session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: New Status in unity-greeter package in Ubuntu: Confirmed 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: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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
