Couldn't connect to accessibility bus
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evince (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned |
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:/
* 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/
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
Changed in evince (Ubuntu): | |
importance: | Undecided → High |
status: | New → In Progress |
status: | In Progress → Fix Committed |
description: | updated |
tags: |
added: verification-done verification-done-jammy removed: verification-needed verification-needed-jammy |
The fix for kinetic is in https:/ /salsa. debian. org/gnome- team/evince/ -/commit/ 0af145b1 and will be part of the next upload, SRU to 22.04 uploaded now