Could not determine the accessibility bus address about browse-activity HOT 9 OPEN

Okay, thanks. This is probably expected, and caused by missing dependencies. Raspberry Pi OS is based on Debian. Is at-spi2-core a dependency of the sugar-browse-activity Debian package? If so, nothing to be done except add the dependencies in a list for this activity. I've checked and it doesn't seem to be. So if installing sugar-browse-activity does not automatically install at-spi2-core, as I would have tried in my original test, then you could report the mistake to Debian Bugs. If you only installed by cloning this repository, then yes, we don't track dependencies fully, and your result may not be immediately useful for fixing this issue. How did you install the activity?

from browse-activity.

I was getting 2 show:
Error retrieving acessibility bus address and could not determine the accessibility bus address.
sudo apt install at-spi2-core
and adding export NO_AT_BRIDGE=1 to profile file worked.

from browse-activity.

Thanks. What part of browse requires the accessibility bus?

from browse-activity.

Well I am unsure on that i just closed sugar opened my rpi terminal installed sudo apt install at-spi2-core and then in my config file i changed export NO_AT_BRIDGE=1 this and restarted again.
This is based on RPi stack exchange conversation where same error was published in general.

from browse-activity.

I installed sugar as package sucrose and it has already been reported as bugs in debian i think as it is similar problem with other orgs and project as well.
Also as there is no impact as such because i think there is no dependency involved so currently i think if this error affects then might have to install spi-2 core or else leave the error as it rest i dont think if anything else can be done until the issue is either resolved from debian side only because it is evident it is not downloading automatically.

from browse-activity.

Thanks. Which bug number?

from browse-activity.

https://unix.stackexchange.com/questions/230238/x-applications-warn-couldnt-connect-to-accessibility-bus-on-stderr
https://bbs.archlinux.org/viewtopic.php?id=176663
https://forums.raspberrypi.com/viewtopic.php?t=196070
I have gone through these error/bugs published on there sites i might have to check specifically in debian github but as you can see on almost all the unix based , rpi stack exchange it has been published.

from browse-activity.

That's not the point. If we're to fix the problem it has to be reported to the responsible developer, and so far that looks to be the developer responsible for one of the packages on Debian. So if you don't know of and can't find a Debian bug number, then we'll have to presume it's a Debian problem that hasn't been reported to Debian. Therefore next step is to report it to Debian? I've not searched the dependent packages and their bugs yet.

from browse-activity.

Yes you are absolutely correct , let me see what can i do.

from browse-activity.