Re: brltty 6.0 is in Debian experimental
Hello, Alex ARNAUD, le mer. 09 oct. 2019 08:50:56 +0200, a ecrit: > After thinking and discusssing I assume pushing BRLTTY 6.0 to Sid seems the > way to go to expect having feedback from users. Sure! I'm just waiting for my transition request for the libbrlapi0.7 name change #941237 Samuel
Re: brltty 6.0 is in Debian experimental
Hello Samuel, I know that Jean-Philippe has tested this release without encountering any issue. After thinking and discusssing I assume pushing BRLTTY 6.0 to Sid seems the way to go to expect having feedback from users. Also, as Testing could be buggy I assume having a buggy software is a assumed risk of each testing/sid users. Best regards, Alex. Le 17/09/2019 à 20:56, Samuel Thibault a écrit : Hello, Brltty 6.0 has landed in experimental, up for your giving a try! Samuel
Re: Unusually long time to log in on fresh testing install
On Sun, Oct 6, 2019, at 10:05 PM, thom...@fastmail.cn wrote: > I just did a fresh install of testing with the Mate desktop and > standard system utilities. I notice that after logging in it takes a > very long time for Orca to start. Can anyone reproduce this or is it just > me? Turns out its not just me and this is not related to accessibility. I dug into this and locally traced it down to a conflict between mate-session-manager and the new version of Gnome Keyring. I was going to try and fix it but noticed there is already a patch under mate-session-manager on salsa. Building with that patch resulted in no delay. I hope this helps someone.
Re: dbus-broker vs dbus-daemon for the accessibility bus
Howdy, We use dbus-broker exclusive here. No issues at all and like you noted, it seems to perform faster, specially on heavy operations. Cheers chrys > Am 08.10.2019 um 14:29 schrieb thom...@fastmail.cn: > > For those not in the know, dbus-broker is a reimplementation of the > dbus-daemon. > I am very interested in this subject when it comes to the accessibility bus. > I have done two types of tests on debian. This requires building the broker > from source and rebuilding at-spi2-core. Used cpu was an 8550u. > Test 1: Load large pages in Chrome with its accessibility enabled with Orca > on. I find that the accessibility bus often uses up to 50 percent of a core > with the daemon and 30 percent with the broker. You need to use Chrome 77 or > older because a change was recently made to Chrome master which makes it send > far less across the bus when loading a page. World War ii page on wikipedia > works nicely. > Test 2: Put the daemon and broker processes in a cgroup and limit their cpu. > In my unscientific testing, I find that the broker seems to perform a bit > better with less cpu. As you choke off the cpu more and more, the gap widens. > Just curious if anyone has done similar testing on debian or even other > distros. I have a core i7 8550u so I don't notice a huge difference but I > suspect users with less cpu might. I have an older core 2 duo machine. It > would be very interesting to get another of those and do side by side testing. >
dbus-broker vs dbus-daemon for the accessibility bus
For those not in the know, dbus-broker is a reimplementation of the dbus-daemon. I am very interested in this subject when it comes to the accessibility bus. I have done two types of tests on debian. This requires building the broker from source and rebuilding at-spi2-core. Used cpu was an 8550u. Test 1: Load large pages in Chrome with its accessibility enabled with Orca on. I find that the accessibility bus often uses up to 50 percent of a core with the daemon and 30 percent with the broker. You need to use Chrome 77 or older because a change was recently made to Chrome master which makes it send far less across the bus when loading a page. World War ii page on wikipedia works nicely. Test 2: Put the daemon and broker processes in a cgroup and limit their cpu. In my unscientific testing, I find that the broker seems to perform a bit better with less cpu. As you choke off the cpu more and more, the gap widens. Just curious if anyone has done similar testing on debian or even other distros. I have a core i7 8550u so I don't notice a huge difference but I suspect users with less cpu might. I have an older core 2 duo machine. It would be very interesting to get another of those and do side by side testing.
