This bug was fixed in the package evince - 42.3-2
---------------
evince (42.3-2) unstable; urgency=medium
[ Sebastien Bacher ]
* debian/apparmor-profile:
- authorize the new at-spi socket location (LP: #1978838)
[ Jeremy Bicha ]
* Cherry-pick patch to fix build with gnome-desktop 43
-- Jeremy Bicha <[email protected]> Thu, 28 Jul 2022 09:45:11 -0400
** Changed in: evince (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1978838
Title:
Couldn't connect to accessibility bus
Status in evince package in Ubuntu:
Fix Released
Status in evince source package in Jammy:
Fix Released
Bug description:
* Impact
the apparmor profile blocks the connection to the accessibility bus
since it hasn't been updated for the new socket location,
https://gitlab.gnome.org/GNOME/at-spi2-core/-/issues/43
* Test Case
start evince, it shouldn't print the warning
dbind-WARNING **: Couldn't connect to accessibility bus: Failed to
connect to socket /run/user/UID/at-spi/bus_0: Permission denied
start orca, it should be able to read the content of evince
* Regression potential
The change is only allowing an extra location in the apparmor profile,
we kept also the old path for compatibility reasons and for making the
profile easier to share between series. Allowing the extra location
shouldn't create a regression but if the change was incorrect it is
possible that evince would still bot be able to connect to the bus
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1978838/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
