Re: [Development] Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

2017-09-03 Thread Allan Sandfeld Jensen
On Sonntag, 3. September 2017 18:15:15 CEST Samuel Thibault wrote: > On the long run, it really should. Just hiding issues is not the way > forward :) > > Also, note that if the performance is so bad, it means something *needs* > to be fixed, otherwise blind users will get the bad performance,

Re: [Development] Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

2017-09-03 Thread Allan Sandfeld Jensen
On Sonntag, 3. September 2017 19:57:55 CEST Samuel Thibault wrote: > Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote: > > That's Qt's fault for not taking care of EventListenerRegistered > signals to determine whether someone is listening. > So it is Qt's fault that is doing

Re: [Development] Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

2017-09-03 Thread Allan Sandfeld Jensen
On Sonntag, 3. September 2017 20:23:30 CEST Samuel Thibault wrote: > Allan Sandfeld Jensen, on dim. 03 sept. 2017 20:19:31 +0200, wrote: > > On Sonntag, 3. September 2017 19:57:55 CEST Samuel Thibault wrote: > > > Allan Sandfeld Jensen, on dim. 03 sept. 2017 19:13:38 +0200, wrote: > > > > > >

Re: [Development] Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on

2017-09-03 Thread Lisandro Damián Nicanor Pérez Meyer
El 3 sep. 2017 4:39 p.m., "Samuel Thibault" escribió: Samuel Thibault, on dim. 03 sept. 2017 21:17:12 +0200, wrote: > I have checked with a vanilla reinstall of Debian 9, using the Mate > desktop, and Qt 5.7.1. > > When QT_LINUX_ACCESSIBILITY_ALWAYS_ON is not set, I don't

Re: [Development] Backporting the Keccak change

2017-09-03 Thread Harri Porten
On Sat, 2 Sep 2017, Oswald Buddenhagen wrote: if we wanted to be really conservative, we'd leave the old meaning of the sha3 constants and introduce realSha3 (or something to that effect) instead, in 5.10+. keccak aliases would be also provided for a smooth migration. Fwiw, I would have