There's
a short thread on ubuntu-accessibility mailing list about this. Unfortunately, it didn't get any answers from Ubuntu developers. And
a longer thread on orca-list. No solution there either.
Could it be related to
LP#1923052 as well? The bug is not about snaps, it's about Ubuntu installer, but still.
As for snaps, I'd recommend you to review
Handling interfaces and permissions in your snaps. Sorry, I cannot give you anything more definitive as I'm using neither Orca nor snaps.
dbus is listed among
interfaces supported by snaps. I'd expect Orca to communicate with snaps via
desktop-legacy (which is enabled by default) rather than via D-Bus interface, but who knows?
BTW,
the Discord page on
snapcraft suggests running
Code:
sudo snap connect discord:system-observe
in order to enable all Discord features.
And
here are all plugs of the Discord snap that could be connected:
Code:
audio-playback
audio-record
browser-support
camera
home
mount-observe
network
network-observe
opengl
process-control
pulseaudio
removable-media
screen-inhibit-control
system-observe
unity7
To list all connected and unconnected plugs of the Discord snap installed on your system, run
Code:
snap connections discord
Another possiblility is to reinstall a snap in classic mode, thus completely disabling its security confinement:
Code:
sudo snap remove discord
sudo snap install --classic discord