This is a follow-up on my comments regarding the inaccessibility of
pidgin. Below is the console output resulting from starting pidgin from
a terminal. Looks like something called apparmor is preventing Pidgin
from using the accessibility? Is this something to do with the way
Pidgin is built in Trisquel 8, 64-bit? How do we know which aparmor
profile is stopping pidgin, and how do we correct this? Electrum
accessibility may be effected by this or similar bug.
Best Regards,
Dave
Script started on Fri 29 Dec 2017 01:45:51 PM EST
]0;dave@thinkpad: ~/Desktopdave@thinkpad:~/Desktop$ pidgin &
[1] 5664
]0;dave@thinkpad: ~/Desktopdave@thinkpad:~/Desktop$ Gtk-Message:
Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "topmenu-gtk-module"
** (Pidgin:5664): WARNING **: Couldn't register with accessibility bus:
An AppArmor policy prevents this sender from sending this message to
this recipient; type="method_call", sender="(null)" (inactive)
interface="org.freedesktop.DBus" member="Hello" error name="(unset)"
requested_reply="0" destination="org.freedesktop.DBus" (bus)
exit
exit
Script done on Fri 29 Dec 2017 01:46:50 PM EST
On 12/24/2017 12:26 AM, Rubén Rodríguez wrote:
* Accessibility: test that the screen reader and other accessibility
features work as expected.
_______________________________________________
Trisquel-devel mailing list
[email protected]
https://listas.trisquel.info/mailman/listinfo/trisquel-devel
