Bug#874054: Setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a huge negative performance impact, should not be always on
Lisandro Damián Nicanor Pérez Meyer
lisandro at debian.org
Sat Sep 2 14:02:15 UTC 2017
Package: at-spi2-core
Version: 2.24.1-2
Severity: important
According to [upstream] setting QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 has a
huge negative performace impact on Qt, so it should not be enabled by
default. And, if I understand correctly, this is the current behavior.
Upstream suggested that maybe we should try to only set this variable if
the appropriate hardware is found. Do you have any ideas on how we could
achieve this?
[upstream]
<http://lists.qt-project.org/pipermail/development/2017-June/030148.html>
Trying to improve everyone's experience, Lisandro.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages at-spi2-core depends on:
ii libatspi2.0-0 2.24.1-2
ii libc6 2.24-17
ii libdbus-1-3 1.11.16+really1.10.22-1
ii libglib2.0-0 2.53.6-1
ii libx11-6 2:1.6.4-3
ii libxtst6 2:1.2.3-1
at-spi2-core recommends no packages.
at-spi2-core suggests no packages.
-- no debconf information
More information about the Pkg-a11y-devel
mailing list