[Bug 1978838] Re: Couldn't connect to accessibility bus

2024-01-13 Thread tomdean
> evince (evince:58774): dbind-WARNING **: 10:34:53.828: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_0: Permission denied > uname -a Linux aorus 6.5.0-14-generic #14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_6

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-12-18 Thread Ubfan
Fully patched Ubuntu 22.04, Dec 18, evince 43.3.2 runs fine until a print or print preview is tried on a ps file, resulting in the same error: $ evince fern.ps GPL Ghostscript 9.55.0: Unrecoverable error, exit code 1 (libspectre) ghostscript reports: fatal internal error -100 (evince-previewer:136

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-07-29 Thread Launchpad Bug Tracker
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 4

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-07-05 Thread Launchpad Bug Tracker
This bug was fixed in the package evince - 42.3-0ubuntu2 --- evince (42.3-0ubuntu2) jammy; urgency=medium * debian/apparmor-profile: - authorize the new at-spi socket location, fix warnings displayed and the screen reader not working (lp: #1978838) -- Sebastien Bacher

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-07-04 Thread Sebastien Bacher
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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:

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-07-04 Thread Tushar
Yes, I edited that file, and that caused the error. Sorry for the inconvenience. Now, I can confirm that this is a successful fix. Thanks, Sebastien. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launc

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-07-04 Thread Sebastien Bacher
did you ever edit that file manually? if so the packaging system is going to preserve your version it seems the file is outdated, could you try to restore to the package version by doing? $ sudo apt install --reinstall -o Dpkg::Options::="--force- confask,confnew,confmiss" evince -- You receive

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-07-04 Thread Tushar
$ grep at-spi /etc/apparmor.d/usr.bin.evince owner /{,var/}run/user/*/at-spi2-*/ rw, owner /{,var/}run/user/*/at-spi2-*/** rw, -- 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/197

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-07-04 Thread Sebastien Bacher
and $ grep at-spi /etc/apparmor.d/usr.bin.evince ? -- 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 abou

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-07-03 Thread Tushar
@Sebastien, here are the outputs: $ dpkg -l | grep evince ii evince 42.3-0ubuntu2 amd64Document (PostScript, PDF) viewer ii evince-common 42.3-0ubuntu2 all Docu

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-07-03 Thread Sebastien Bacher
@Tushar, could you share the output for $ dpkg -l | grep evince? and do $ journalctl -f then start evince and share in the bug what was printed? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpa

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-07-03 Thread Tushar
Hello, Sebastien. Adding evince 42.3-0ubuntu2 from jammy-proposed does not solve this issue. I am still getting "dbind-WARNING **: [XX:XX:XX.XXX]: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/[UID]/at-spi/bus: Permission denied". -- You received this bug notifi

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-06-22 Thread Robie Basak
Hello Sebastien, or anyone else affected, Accepted evince into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evince/42.3-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wi

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-06-17 Thread Sebastien Bacher
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 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launc

[Bug 1978838] Re: Couldn't connect to accessibility bus

2022-06-17 Thread Sebastien Bacher
** Description changed: * 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