Description Zdenek Veleba 2020-05-06 15:14:33 UTC Description of problem:at-spi is not working properly in the installation environment, in this case accessed via pyatspi, see error below.The issue is not present on a installed system. I think the problem could be that at-spi2-registryd service is not running in the installation environment, I've tried to start it without success, no errors printed anywhere, but maybe I didn't do it right.EDIT: I was able to start the at-spi2-registryd and now it's working. The issue still is that it should be started automatically.How reproducible:AlwaysSteps to Reproduce:- Boot installation media, for example: Fedora-Everything-netinst-x86_64-32-1.6.iso- When the system starts switch to tty2- Run `DISPLAY=":1" python3` and enter>>> import pyatspi>>> pyatspi.Registry.getDesktop(0)Actual results:(process:2072): dbind-WARNING **: 08:29:44.342: Couldn't get application list: Could not activate remote peer./usr/lib/python3.8/site-packages/pyatspi/registry.py:206: Warning: g_object_unref: assertion 'G_IS_OBJECT (object)' failed return Atspi.get_desktop(i)<Atspi.Accessible object at 0x7efc2d39a540 (AtspiAccessible at 0x55c02938b3b0)>Expected results:no errorAdditional info:at-spi-bus-launcher is running Comment 1 Jan Stodola 2020-05-07 07:37:31 UTC Also reproduced using Fedora-Rawhide-20200505.n.0.Unfortunately, this issue blocks our automated testing of the installer.Matthias, do you have any idea how to work around this problem? Comment 2 Zdenek Veleba 2020-05-07 09:33:09 UTC Even after starting the at-spi2-registryd service manually, I get empty desktop (but there is anaconda running). So maybe I'm still doing it wrong or there is something else missing. Comment 3 Zdenek Veleba 2020-05-11 14:11:45 UTC Just to clarify, here is what I am trying to do now:On RHEL:ps aux | grep at-spiroot 2023 0.0 0.2 111172 10140 ? Sl 14:05 0:00 /usr/libexec/at-spi-bus-launcherroot 2027 0.0 0.1 62028 4080 ? Sl 14:05 0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3root 2030 0.0 0.2 117368 8668 ? Sl 14:05 0:00 /usr/libexec/at-spi2-registryd --use-gnome-sessionroot 2377 0.0 0.0 9180 1068 pts/5 S+ 14:06 0:00 grep at-spiDISPLAY=:1 /usr/libexec/platform-python>>> import pyatspi>>> for app in pyatspi.Registry.getDesktop(0):... print(app.name)... metacityanaconda>>> On Fedora:ps aux | grep at-spiroot 1808 0.0 0.1 34644 6236 ? Sl 14:00 0:00 /usr/libexec/at-spi-bus-launcherroot 1812 0.0 0.0 268464 3412 ? S 14:00 0:00 /usr/bin/dbus-broker-launch --config-file=/usr/share/defaults/at-spi2/accessibility.conf --scope userroot 2098 0.0 0.0 3116 720 pts/5 S+ 14:01 0:00 grep at-spiDISPLAY=:1 /usr/libexec/at-spi2-registryd --use-gnome-session &[1] 2105SpiRegistry daemon is running with well-known name - org.a11y.atspi.RegistryDISPLAY=:1 python3>>> import pyatspi>>> for app in pyatspi.Registry.getDesktop(0):... print(app.name)... >>> Comment 4 Matthias Clasen 2020-05-12 16:33:09 UTC | - Boot installation media, for example: Fedora-Everything-netinst-x86_64-32-1.6.iso| - When the system starts switch to tty2| - Run `DISPLAY=":1" python3` and enterWell, thats not the way to set up a working desktop session, so it is not too surprising that desktop functionality is not working.| Matthias, do you have any idea how to work around this problem?If working accessibility is a requirement for the installer, it needs to set up a working destkop sessionto run in.I would suggezt that the live environment is the closest you get to running the installer in a working session.Alternatively, you can try to chase down whatever bits and pieces are missing to make the a11y bus come up,but a) thats not fun and b) it will be fragile and eternally broken Comment 5 Matthias Clasen 2020-05-12 16:35:04 UTC Or maybe I'm misunderstanding. Is accessibility working in the installer environment ?What happens when you turn on the screen reader ? Comment 6 Jan Stodola 2020-05-12 17:31:42 UTC Created attachment 1687781 [details]syslog, Fedora 32Actually, we already do the installer testing on RHEL-7 and RHEL-8 this way, so we know it works fine there.It also seems to work on Fedora 29:[anaconda root@localhost ~]# DISPLAY=:1 python3Python 3.7.0 (default, Aug 30 2018, 14:32:33) [GCC 8.2.1 20180801 (Red Hat 8.2.1-2)] on linuxType "help", "copyright", "credits" or "license" for more information.>>> import pyatspi>>> for app in pyatspi.Registry.getDesktop(0):... print(app.name)... metacityanaconda>>>These steps don't work on Fedora 30 and later, and I can see the following warning messages in the console (Fedora-Server-netinst.iso was used in all cases):17:21:24 Please manually connect your vnc client to 192.168.122.237:1 to begin the install.17:21:24 Attempting to start vncconfig** (anaconda:1635): WARNING **: 17:21:38.743: AT-SPI: Could not obtain desktop path or name** (anaconda:1635): WARNING **: 17:21:40.148: atk-bridge: GetRegisteredEvents returned message with unknown signature** (anaconda:1635): WARNING **: 17:21:40.148: atk-bridge: get_device_events_reply: unknown signature** (anaconda:1635): WARNING **: 17:21:40.148: atk-bridge: get_device_events_reply: unknown signatureI'm attaching syslog from the Fedora 32 installation environment, where you can see errors related to at-spi:17:21:26,201 INFO dbus-daemon:[session uid=0 pid=1832] Activating service name='org.a11y.Bus' requested by ':1.0' (uid=0 pid=1820 comm="metacity --display :1 --sm-disable " label="system_u:system_r:kernel_t:s0")17:21:26,215 INFO dbus-daemon:[session uid=0 pid=1832] Successfully activated service 'org.a11y.Bus'17:21:26,231 WARNING org.a11y.Bus:Policy to allow eavesdropping in /usr/share/defaults/at-spi2/accessibility.conf +15: Eavesdropping is deprecated and ignored17:21:26,232 WARNING org.a11y.Bus:Policy to allow eavesdropping in /usr/share/defaults/at-spi2/accessibility.conf +17: Eavesdropping is deprecated and ignored17:21:26,234 NOTICE journal:Ready17:21:26,623 INFO dbus-daemon:[session uid=0 pid=1832] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=0 pid=1841 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha" label="system_u:system_r:kernel_t:s0")17:21:26,642 INFO dbus-daemon:[session uid=0 pid=1832] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 117:21:26,642 ERR dbus-broker-launch:Activation request for 'org.a11y.atspi.Registry' failed.17:21:26,643 INFO dbus-daemon:[session uid=0 pid=1832] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=0 pid=1841 comm="/usr/bin/dbus-broker-launch --config-file=/usr/sha" label="system_u:system_r:kernel_t:s0")17:21:26,644 INFO dbus-daemon:[session uid=0 pid=1832] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 117:21:26,644 ERR dbus-broker-launch:Activation request for 'org.a11y.atspi.Registry' failed. Comment 8 Jan Stodola 2020-05-14 19:19:18 UTC FYI, I've tried the steps from Zdenek in the live environment (Fedora-Workstation-Live) when the installer was started. While anaconda was listed in F-29, it wasn't listed in case of F-32:* Fedora-29:[liveuser@localhost-live ~]$ python3Python 3.7.0 (default, Aug 30 2018, 14:32:33) [GCC 8.2.1 20180801 (Red Hat 8.2.1-2)] on linuxType "help", "copyright", "credits" or "license" for more information.>>> import pyatspi>>> for i in pyatspi.Registry.getDesktop(0):... print(i.name)... gnome-shellibus-x11gsd-powergsd-xsettingsgsd-wacomgsd-clipboardgsd-keyboardgsd-colorgsd-media-keysabrtevolution-alarm-notifyanacondagnome-terminal-server>>>* Fedora-32:[liveuser@localhost-live ~]$ pythonPython 3.8.2 (default, Feb 28 2020, 00:00:00) [GCC 10.0.1 20200216 (Red Hat 10.0.1-0.8)] on linuxType "help", "copyright", "credits" or "license" for more information.>>> import pyatspi>>> for i in pyatspi.Registry.getDesktop(0):... print(i.name)... gnome-shellgsd-keyboardgsd-media-keysgsd-powergsd-colorgsd-wacomibus-x11gsd-xsettingsevolution-alarm-notifygnome-terminal-server>>> Comment 9 Vendula Poncova 2020-07-15 13:47:39 UTC It looks like this isssue is caused by the dbus-broker support. See the commit:https://gitlab.gnome.org/GNOME/at-spi2-core/commit/d7f47c99d093ba91eb18523e14b23bde1794f5bcThe service org.a11y.Bus runs dbus-broker-launch in the user scope that requires the user instance of systemd. However, there is no such instance in the installation environment. If Anaconda starts 'systemd --user', it seems to fix the problem. See the pull request:https://github.com/rhinstaller/anaconda/pull/2737/filesI guess that live environments are affected by the same change, but the situation is more complicated. Anaconda is started from the user session with root privileges and GDK_BACKEND=x11. I have no idea how to fix it there. Comment 10 Vendula Poncova 2020-09-25 10:44:35 UTC The anaconda fix will be released in anaconda-34.7-1. Comment 11 Fedora Program Management 2021-04-29 17:12:56 UTC This message is a reminder that Fedora 32 is nearing its end of life.Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.It is Fedora's policy to close all bug reports from releases that are no longermaintained. At that time this bug will be closed as EOL if it remains open with aFedora 'version' of '32'.Package Maintainer: If you wish for this bug to remain open because youplan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Comment 12 Ben Cotton 2021-05-25 18:01:55 UTC Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 isno longer maintained, which means that it will not receive any furthersecurity or bug fix updates. As a result we are closing this bug.If you can reproduce this bug against a currently maintained version ofFedora please feel free to reopen this bug against that version. If youare unable to reopen this bug, please file a new report against thecurrent release. If you experience problems, please add a comment to thisbug.Thank you for reporting this bug and we are sorry it could not be fixed. |
