Public bug reported: * 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 * 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 ** Affects: evince (Ubuntu) Importance: High Status: Fix Committed ** Changed in: evince (Ubuntu) Importance: Undecided => High ** Changed in: evince (Ubuntu) Status: New => In Progress ** Changed in: evince (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1978838 Title: Couldn't connect to accessibility bus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1978838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
