Re: mate desktop area not accessible after testing last update?

2016-06-05 Thread Jude DaShiell
I wonder would running mate-caja --replace at all help? The mate-panel is also buggy in terms of accessibility and running mate-panel --replace as a workaround helps with that problem. Over on the sonargnulinux mailing list where mate is run by a few of us with low memory machines someone was

Re: mate desktop area not accessible after testing last update?

2016-06-05 Thread MENGUAL Jean-Philippe
Hi, Thanks for report. Yes, I confirm the problem. I don't know wether the problem is upstream, or due to the fact Debian maintainers haven't finished packaging. But given that mate 1.14 had other problems with applets, I suspect it's upstream. I've just reported here: https://github.com/mate-des

mate desktop area not accessible after testing last update?

2016-06-05 Thread Michelangelo Rodriguez
Hi all, After i upgraded caja to the version 1.14.1-1 orca does'nt read icons in the desktop area anymore. Someone had the same problem? Thanks in advance, Miguel

mate desktop area not accessible after testing last update?

2016-06-05 Thread Michelangelo Rodriguez
Hi all, After i upgraded caja to the version 1.14.1-1 orca does'nt read icons in the desktop area anymore. Someone had the same problem? Thanks in advance, Miguel

Bug#826329: brltty: Please make easier braille driver setting

2016-06-05 Thread Jean-Philippe MENGUAL
Hi, > > Do you know that you can also put settings you are overriding > into /etc/xdg/brltty/brltty.conf ? I didn't know. I hope it doesn't make things a bit more complex. >> >> With capability to check several choices and, for devices, enter it manually >> (useful when serial device is ttyUSB0)

Bug#826329: brltty: Please make easier braille driver setting

2016-06-05 Thread Mario Lang
Jean-Philippe MENGUAL writes: > Today, braille display support is correct, but automate recognition is > not warrantied > at all. Either due to USB IDs, or because the driver needs additional > parameters > (e.g. Eurobraille), or because braille display needs serial ports (ttyS0 > or ttyUSB0), >