On Sat, 2015-08-08 at 00:39 -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > I'm afraid this is a hard one. As a team policy we do not patch qt > except for > patches ACKed by upstream. And that means pushed to upstream's > gerrit. > > Moreover this one comes from a RH employee, and in my experience > getting them > to properly push the patches tends to be... complicated. > > So I did report the bug upstream and I'll try to track down the > original coder > of the patch.
Having followed the upstream report, I understand this will now have to be cherry picked for Debian ? Also, do you think this should be documented somewhere ? Especially the last section. https://techbase.kde.org/Development/Tutorials/Accessibil ity/Screen_Reader_Setup#How_to_test_at-spi2_with_Qt For QT4 based apps, this works after setting QT_ACCESSIBILITY=1. Otherwise, the on-screen keyboard won't show. The above link says that for Qt 5, the env variable is not needed. But, for QT5 apps (For now tested only with Calibre ebook tool) it does not seem to work. I think these details should go into README.Debian. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
