Re: --force-renderer-accessibility not working lately

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



No idea, I'm assuming on reboot it picked up the variable being set right and it took a reboot to pick up on it.

Hey it works,  don't knock it really

On 11/29/21 15:40, Linux for blind general discussion wrote:
Ok, interesting, after rebooting my system it is working as expected. What the hell?


Warm regards,

Brandt Steenkamp

Sent from the Fedora machine, using Thunderbird

On 2021/11/29 17:25, Linux for blind general discussion wrote:
Do you have the right environment variables set? In my .bashrc I have


export ACCESSIBILITY_ENABLED=1


In it. That makes Chromium based things work on Arch/Ubuntu for me

On 11/29/21 15:13, Linux for blind general discussion wrote:
Hi all,


I have tried this in both Slint and Fedora, and I've not had any luck making the --force-renderer-accessibility flag work with either Google-Chrome or Skype, both applications for which this flag use to work very well in the past.


Am I missing something, or am I just out of luck here.


Unfortunately, I actually need this to work, otherwise, I'll just have to use the MacBook to do my job.


_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/blinux-list


_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/blinux-list


_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/blinux-list




[Index of Archives]     [Linux Speakup]     [Fedora]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]