GNOME Bugzilla – Bug 673632
If In Nautilus file browser enabled the side, Nautilus launch is very slow and Orca begin talking later
Last modified: 2021-07-05 10:45:22 UTC
Dear Developers, If In Nautilus file browser enabled the side in the view menu with shows for example the computer places, Orca begin talking later, and Nautilus launching little slow. If Orca not running, if my wife see right Nautilus launching faster. Reproducation steps: 1. Launch your home folder. If the side is not enabled, Nautilus launch faster and Orca begin responsing faster with directory list. If the side is enabled, not always focusing the file list window. I maked a debug.out with showing two trying opening HOME folder. Possible doing anything with Orca level, or this is a known Nautilus 3.4 bug? Attila
Created attachment 211461 [details] Debug file with possible showing what happening if the side is enabled in Nautilus file browser
Created attachment 211470 [details] Orca-free listener The following listener does not require or use Orca. It merely listens for object:property-change:accessible-name events and prints them out along with a count. If I have the side bar enabled, launching Nautilus results in 425 such events; if I do not, I get approximately 100.
Attila, this looks somewhat similar to your Thunderbird delay bug. I don't know if a similar fix is possible in AT-SPI2 or Nautilus. Transfering to AT-SPI2 for Mike's assessment.
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/ Thank you for your understanding and your help.