Enabling accessibility stack by default in Qt4/Qt5
Hello, As discussed at DebConf [1,2,3], we would like to make the accessibility stack enabled by default, so that all a user who needs it has to do is just to start orca (while at the moment she has to find an option in the control panel, and logout/login again, thus closing all running applications...). For Qt4, this is implemented in the qt-at-spi package, which has been developped mostly between 2009 and 2013. There doesn't seem to be much activity there since early 2013. For Qt5, this is implemented directly in the Qt core, and seems to be actively maintained and improved. So it seems safer to enable accessibility in Qt5 than in Qt4, but for now it seems to me that most Debian applications are still using Qt4, so people will mostly need Qt4 accessibility. Considering that we are just at the beginning of the Stretch development, perhaps we can try to enable accessibility by default in both Qt4 and Qt5, see how well this goes, and at worse not enable it by default for Qt4 if the possibly-revealed bugs become really not solvable? The way I see it is simply by making the at-spi2-core package define QT_ACCESSIBILITY (for Qt4) and QT_LINUX_ACCESSIBILITY_ALWAYS_ON (for Qt5) to 1 from a script in /etc/X11/Xsession.d. Is it OK with Qt people? Samuel [1] https://summit.debconf.org/debconf15/meeting/290/thanks-for-maintaining-a-desktop-environment-but-is-it-accessible/ [2] http://brl.thefreecat.org/2015-08-22-debconf.pdf [3] http://brl.thefreecat.org/2015-08-22-debconf.txt
java-atk-wrapper_0.33.0-3_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 31 Aug 2015 20:56:38 +0200 Source: java-atk-wrapper Binary: libatk-wrapper-java libatk-wrapper-java-jni Architecture: source amd64 all Version: 0.33.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Accessibility Team Changed-By: Samuel Thibault Description: libatk-wrapper-java - ATK implementation for Java using JNI libatk-wrapper-java-jni - ATK implementation for Java using JNI (JNI bindings) Closes: 788189 Changes: java-atk-wrapper (0.33.0-3) unstable; urgency=medium . * Revert to depending on default-jdk, but it'll have to support java 6 to be able to build us (Closes: #788189). Checksums-Sha1: 916ef723e014bf5d967fa2fb5ab59cc7b5f2dc43 2317 java-atk-wrapper_0.33.0-3.dsc 2024dc387e599cf8f8374a88cd7691982176d0d7 3415 java-atk-wrapper_0.33.0-3.debian.tar.bz2 f649b5c3c393177cafbd27dd2d6e4da8c23350c0 32380 libatk-wrapper-java-jni_0.33.0-3_amd64.deb cc696ebc7446640c1c0bd14add29efa1c7d69703 38214 libatk-wrapper-java_0.33.0-3_all.deb Checksums-Sha256: fb273a6f370e3174fe03cc336adb80265cac99f7f51a76599e84175449b740aa 2317 java-atk-wrapper_0.33.0-3.dsc d371592a4410a0785bfc5e8dd6f154d234cd87ee97983776a5fc9ce242051092 3415 java-atk-wrapper_0.33.0-3.debian.tar.bz2 91f73c8c98cbb8ee6e29911727a358e6b0e6fb8bbf95a10ebd13517a9a3970e4 32380 libatk-wrapper-java-jni_0.33.0-3_amd64.deb e48ed9b653a747f7ef89f55197785bdd4e5d1b5d76cecb738f1116851071220e 38214 libatk-wrapper-java_0.33.0-3_all.deb Files: ed65291d93d1fca0c8628c689040e570 2317 java optional java-atk-wrapper_0.33.0-3.dsc 721ae14f23a531c9d0c6a9780402fc42 3415 java optional java-atk-wrapper_0.33.0-3.debian.tar.bz2 13c2dae9e3a295f51fc2c71670206644 32380 java optional libatk-wrapper-java-jni_0.33.0-3_amd64.deb 92b047f4a20a3b90fd185f543a057bef 38214 java optional libatk-wrapper-java_0.33.0-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJV5KVcAAoJEAdNJfYUJ+jAeh4QAMW8KW4Zb/FrkcsFVp1strkH Qk97MOWnKjo18rhfGL4EMeoTYP4WfMXx82SgckgU2A6+srsHIM+XTXIgzdvx6OOx sQoT0XxLT4swXDix/a00sE5Un9hKaTxJSyZR6c7pwEhqpM786oAy36ccDf3otP8W Gquen+GxtkyfHCfCaSbl4vCbOywOnYkgQLwwX4zIdvlX8VebH6wnGd0DKRd7/ldh XJ45qVlkiaMPbk/xvu2DmQOk5GhxXcefxw+2+EdE1BG0nvMJx6qcJywDH2mRxnQl 4y8JhMWsTKL7dW7AovDWqhUR9XmStB/q2gU5cwzec8w5PNjgwaemYWmLTaom3isd tJa8oEW6JTAwRQrStHoRi1H6dXn3xrpcHBNbaYwI9LDDtCPUPJmn66gQqan/E8En C0sA0FFsFqMcvqMaRAjOPHtptS3H/37Ddw8QkfiARm5Ch1rx5yt8rB4+r7tp7o54 KSXK/lZPQ5VVXl4T9WyZAnDQcuf0h9L8p0dnuM+oPyF3iAygpgq52lhV//S0rtXD P98uuwpJuc6tS71EQPhqIrJsK8dcxq2nG9zpnP2kU1dK3RxPLvj+AdoCVY9kv7d2 7zFhvq3ZLKau1Cp6eTZWH6ha2qvQyvxPhnWQpkS1CLKOBD6uvM8puc2u1ygNRBmW u+fEoszRTECFYzgYOBQT =Abuv -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of java-atk-wrapper_0.33.0-3_amd64.changes
java-atk-wrapper_0.33.0-3_amd64.changes uploaded successfully to localhost along with the files: java-atk-wrapper_0.33.0-3.dsc java-atk-wrapper_0.33.0-3.debian.tar.bz2 libatk-wrapper-java-jni_0.33.0-3_amd64.deb libatk-wrapper-java_0.33.0-3_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)
Processing of java-atk-wrapper_0.33.0-3_amd64.changes
java-atk-wrapper_0.33.0-3_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: java-atk-wrapper_0.33.0-3.dsc java-atk-wrapper_0.33.0-3.debian.tar.bz2 libatk-wrapper-java-jni_0.33.0-3_amd64.deb libatk-wrapper-java_0.33.0-3_all.deb Greetings, Your Debian queue daemon (running on host coccia.debian.org)
Bug#788189: marked as done (java-atk-wrapper: build depends on openjdk-6 which is going away)
Your message dated Mon, 31 Aug 2015 19:19:18 + with message-id and subject line Bug#788189: fixed in java-atk-wrapper 0.33.0-3 has caused the Debian Bug report #788189, regarding java-atk-wrapper: build depends on openjdk-6 which is going away to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 788189: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: java-atk-wrapper Version: 0.33.0-2 Severity: important Hi, java-atk-wrapper build depends on openjdk-6 like this: openjdk-6-jdk | java6-sdk However since the buildds ignore all but the first choice in an ORed group, this is effectively a hard dependency on openjdk-6. If you didn't know openjdk-6 is not in testing and will probably disappear some time before stretch is released. It's probably better to just depend on default-jdk. For most arches this is OpenJDK 7 and for gcj arches you can just let the build fail and possibly have the package removed on those arches. Thanks, James signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: java-atk-wrapper Source-Version: 0.33.0-3 We believe that the bug you reported is fixed in the latest version of java-atk-wrapper, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 788...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated java-atk-wrapper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 31 Aug 2015 20:56:38 +0200 Source: java-atk-wrapper Binary: libatk-wrapper-java libatk-wrapper-java-jni Architecture: source amd64 all Version: 0.33.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Accessibility Team Changed-By: Samuel Thibault Description: libatk-wrapper-java - ATK implementation for Java using JNI libatk-wrapper-java-jni - ATK implementation for Java using JNI (JNI bindings) Closes: 788189 Changes: java-atk-wrapper (0.33.0-3) unstable; urgency=medium . * Revert to depending on default-jdk, but it'll have to support java 6 to be able to build us (Closes: #788189). Checksums-Sha1: 916ef723e014bf5d967fa2fb5ab59cc7b5f2dc43 2317 java-atk-wrapper_0.33.0-3.dsc 2024dc387e599cf8f8374a88cd7691982176d0d7 3415 java-atk-wrapper_0.33.0-3.debian.tar.bz2 f649b5c3c393177cafbd27dd2d6e4da8c23350c0 32380 libatk-wrapper-java-jni_0.33.0-3_amd64.deb cc696ebc7446640c1c0bd14add29efa1c7d69703 38214 libatk-wrapper-java_0.33.0-3_all.deb Checksums-Sha256: fb273a6f370e3174fe03cc336adb80265cac99f7f51a76599e84175449b740aa 2317 java-atk-wrapper_0.33.0-3.dsc d371592a4410a0785bfc5e8dd6f154d234cd87ee97983776a5fc9ce242051092 3415 java-atk-wrapper_0.33.0-3.debian.tar.bz2 91f73c8c98cbb8ee6e29911727a358e6b0e6fb8bbf95a10ebd13517a9a3970e4 32380 libatk-wrapper-java-jni_0.33.0-3_amd64.deb e48ed9b653a747f7ef89f55197785bdd4e5d1b5d76cecb738f1116851071220e 38214 libatk-wrapper-java_0.33.0-3_all.deb Files: ed65291d93d1fca0c8628c689040e570 2317 java optional java-atk-wrapper_0.33.0-3.dsc 721ae14f23a531c9d0c6a9780402fc42 3415 java optional java-atk-wrapper_0.33.0-3.debian.tar.bz2 13c2dae9e3a295f51fc2c71670206644 32380 java optional libatk-wrapper-java-jni_0.33.0-3_amd64.deb 92b047f4a20a3b90fd185f543a057bef 38214 java optional libatk-wrapper-java_0.33.0-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJV5KVcAAoJEAdNJfYUJ+jAeh4QAMW8KW4Zb/FrkcsFVp1strkH Qk97MOWnKjo18rhfGL4EMeoTYP4WfMXx82SgckgU2A6+srsHIM+XTXIgzdvx6OOx sQoT0XxLT4swXDix/a00sE5Un9hKaTxJSyZR6c7pwEhqpM786oAy36ccDf3otP8W Gquen+GxtkyfHCfCaSbl4vCbOywOnYkgQLwwX4zIdvlX8VebH6wnGd0DKRd7/ldh XJ45qVlkiaMPbk/xvu2DmQOk5GhxXcefxw+2+EdE1BG0nvMJx6qcJywDH2mRxnQl 4y8JhMWsTKL7dW7AovDWqhUR9XmStB/q2gU5cwzec8w5PNjgwaemYWmLTaom3isd tJa8oEW6JTAwRQrStHoRi1H6dXn3xrpcHBNbaYwI9LDDtCPUPJmn66gQqan/E8En C0sA0FFsFqMcvqMaRAjOPHtptS3H/37Ddw8QkfiARm5Ch1rx5yt8rB4+r7tp7o54 KSXK/lZPQ5VVXl4T9WyZAnDQcuf0h9L8p0dnuM+oPyF3iAygpgq52lhV//S0rtXD P98uuwpJuc6tS71EQPhqIrJsK8dcxq2nG9zpnP2kU1dK3RxPLvj+AdoCVY9kv7d2 7zFhvq3ZLKau1Cp6eTZWH6ha2qvQyvxPhnWQpkS1CLKOBD6uvM8puc2u1ygNRBmW u+fEoszRTECFYzgYOBQ
Re: New Debian Single Signon
Enrico Zini writes: > On Thu, Aug 27, 2015 at 02:20:35PM +0200, Mario Lang wrote: > >> works, but that is barely a solution since you will not be able to >> follow any site-specific links. It is a shame lynx apparently doesn't >> have support for client certificates. > > I tried to patch it but ran into #797059. Interesting find, since this one (or at least the symptom) is bugging me since quite a while now. > However, can you please try the attached patch with links? Work for me. Nice patch! This is one of these moments where I am happy to see that Debian is not just about packaging upstream software. For me, the fun just begins if we identify and implement improvements upstream. -- CYa, ⡍⠁⠗⠊⠕ signature.asc Description: PGP signature
Pluseaudio, speech-dispatcher, and console + graphical screen readers
Christian Schoepplein writes: > On Fri, Aug 28, 2015 at 12:33:41AM +0200, Samuel Thibault wrote: >>As discussed during DebConf15, we target enabling the accessibility >>stack by default. I've studied that a bit more, here are my thoughts: > > Diskussing accessibility of Debian should not only be reduced to the > issues you mensioned, Samuel, there are a few more things that need to > be worked out, I think. > For example the fact, that the way pulseaudio, speech-dispatcher and all > this stuff needs to be configured to work propperly, when orca and a > console screen reader is used. Of course, there is a ton of issues that need to be worked out. However, this thread is trying to deal with a rather specific topic, namely, pushing for default enabled accessibility stacks in graphical toolkits. I have changed the subject of your thread, to keep matters seprataed and avoid hijacking this other thread, which is actually also important to work on. > I've installed a fresh Debian 8 a few months ago and it wasn't really > easy and especialy for beginners this stuff isn't manageable IMHO. Now > pulseaudio and speech-dispatcher are running in system mode and > everything is working well, but that kind of setup is not wanted for > security reasons. I am tempted to agree with you that we need far too much manual configuration interventions for certain accessibility features to cooperate, just by my own experience. However, could you be a little bit more specific? Particularily: * What sort of setup were you aiming to achieve? * What was particularily difficult to figure out? * What did you have to change, from the default, to get what you want? > So what about these things? Since pulseaudio is used as default for > sound output, the barriers using Debian with some setups have been > increased... I agree, pulseaudio has been a source of many bugs in the user experience. I myself remember several incidents where ALSA soft mixing (which is, AFAIU, supposed to be the default) failing and pulseaudio effectively preventing a console ALSA application from gaining access to the sound card. I admit that I was not investigative enough in this situations, and mostly just ended up "apt-get remove"'ing pulseaudio. I know this is no solution, and I am guilty of just giving up on that front in the past. The Linux audio ecysystem is sort of a nightmare. For a long time, all we had was OSS (/dev/dsp). Then came ALSA, which resulted in a long period of programs either missing ALSA support, or ALSA support not quite working. That was the time when you still were suppposed to buy a soundcard which supports hardware mixing, such that you could have several programs talking to the soundcard at the same time. At some point, ALSA soft mixing support was mature enough that some distributions started to enable it by default. However, Linux audio has other audio servers, like JACK, and later PulseAudio. JACK is for the pro audio people, a really nice realtime audio routing engine. However, if you use JACK, you also loose ALSA soft mixing because the JACK server opens the soundcard in such a way that soft mixing can no longer work (or at least, usually does). Once JACK was really stable and doing a lot of things, and many Linux audio applications added actual direct support for it, the PulseAudio team decided to do yet another audio server, specifically targeted for the Linux desktop (whatever that may be). The JACK people were not happy, but PulseAudio was somehow pushed into existance. So now a Linux audio application is more or less supposed to implement direct support for ALSA, and support for two different audio servers, JACK and PulseAido. If they are portable across UNIXes, they are likely to have /dev/dsp as well. This is just unrealistic, so the reality is, that most applications have a subset of support for these mechanisms. And some of the scenarios a user might encounter are just incompatible. Such as using JACK as the primary audio server while using other legacy ALSA applications at the same time. It also appeared to me in several occasions that PulseAudio does sometimes make legacy ALSA applications unusable. We need a pulseaudio expert to chime in on this. Or someone from our group needs to become one. From POV of the Accessibility Team, our goals are easily summarized: * Configure whatever audio system is in use automatically, loading necessary modules, starting user-space support and ensuring the primary audio output channel levels are up, *not* muted. This needs to happen independent from the desktop in use, and should also work if no graphical environment has been started at all. * Make sure that the speech synthesis backend of the screen reading solution does not block any other audio applications. In the simplest case, desktop sounds should still work while the speech synthesizer is talking. We need to identify common use cases which currently have proble
Re: lynx cannot connect to https://contributors.debian.org
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, just a tiny information, maybe someone is more involved in GNUTL/SSl stuff: Trying to tracking down the location of the error, i found the following : Lynx aborts the SSL connection with : Rehandshake was requested by the peer. (which is error code -37, btw) in HTTP.c, around line 1690 (look for SSLerror = ERR_get_error()) != 0) So, apparnetly lynx is not able to cope with a rehandshake request from the server. Cheers, Simon -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCgAGBQJV5GACAAoJEBy08PeN7K/pkBMP/0wcbk3dMsR6k8f0yjhknELY 837y+x0NhCnkMShinNnHp4MVWaXK6OcgLBLlt3GJ9/QlZIuF6Ccd4voFjPU88ZT5 0wTZEQdkMKAKXwZaW95aBKwBe7KS8FMW+JcMbNSWCsoWjXubI6NzyERA5mDQO18S nvcJEX7VqpODc6J9/yk0FSDF7EaBRGj1ipeR6LXzu900+7q/V33i2AutA6yyCj4i +8aDLOEGNNOfx1HgqbLvXpwnbauo7v5alfAvnTMbqxxlfZwTtvWi0mJRfSN0Iq90 SO+06UsfgdLQcZA4YHTvAOGV13gWxrfy10yhshyj8FbXK3D0gY9n77ZAhAg23BW6 8GnTrYGrqUrPvNUSF2v4TRR+iaD3XsaXjXyqqXyBfzWYA9Q4kvCj3NmAfPApajAS Noyz1xXAmlcSYeFn+uE9aojobyaLXhCjxJoxr8HPgxtquEIdPemolomurPrR/DPC E+SHRS0JKbC51j2QUyLPHBg2jCFN3t1P5gsroikpufnZ1ZJk5fwdl2Nfa36Xu2hR +0vkxEbm+uOQZfr9R0BY3RHkCgZ0Eh0NEnXYrN80TlbBvzD9T7W2fJgbs1306g0/ FljMyxQoYUjanuvTt1OKf9xYXeyPIt/zfeSirHymp/S6rpQO3LQfqTAHngqys3Qm 8/6rYzyEw6x1arupneZT =nqVx -END PGP SIGNATURE-
Re: Making the accessibility stack enabled by default
Christian Schoepplein, le Mon 31 Aug 2015 15:02:18 +0200, a écrit : > On Fri, Aug 28, 2015 at 12:33:41AM +0200, Samuel Thibault wrote: > >As discussed during DebConf15, we target enabling the accessibility > >stack by default. I've studied that a bit more, here are my thoughts: > > Diskussing accessibility of Debian should not only be reduced to the > issues you mensioned, Samuel, there are a few more things that need to > be worked out, I think. Of course, but that's an independent matter. I never said we were reducing it to these issues. See the recipients of the mail: it was intended for the discussion with the gtk team. The gtk team only cares about enabling the stack in gtk. > For example the fact, that the way pulseaudio, speech-dispatcher and all > this stuff needs to be configured to work propperly, when orca and a > console screen reader is used. In the matter at stake, i.e. being able to run orca on a system which was never explicitly configured for accessibility, there is no console screen reader, actually. > So what about these things? Since pulseaudio is used as default for > sound output, the barriers using Debian with some setups have been > increased... Sure, that has to be worked on too. Samuel
Re: Making the accessibility stack enabled by default
Hi, On Fri, Aug 28, 2015 at 12:33:41AM +0200, Samuel Thibault wrote: >As discussed during DebConf15, we target enabling the accessibility >stack by default. I've studied that a bit more, here are my thoughts: Diskussing accessibility of Debian should not only be reduced to the issues you mensioned, Samuel, there are a few more things that need to be worked out, I think. For example the fact, that the way pulseaudio, speech-dispatcher and all this stuff needs to be configured to work propperly, when orca and a console screen reader is used. I've installed a fresh Debian 8 a few months ago and it wasn't really easy and especialy for beginners this stuff isn't manageable IMHO. Now pulseaudio and speech-dispatcher are running in system mode and everything is working well, but that kind of setup is not wanted for security reasons. So what about these things? Since pulseaudio is used as default for sound output, the barriers using Debian with some setups have been increased... Cheers, Christian signature.asc Description: Digital signature
