Source: qt-at-spi Version: 0.3.1-4 Followup-For: Bug #762672 Control: severity -1 critical
Dear Maintainer, I have ventured to set the severity to critical as I agree this bug is pretty ugly since it breaks unrelated software on the system and uncovering the cause is highly non-trivial. In my scenario (MATE + KDE apps), QT programs actually start, but with about two minute delay. And the breakage was not due to lightdm (it happenned with both gdm3 and lightdm) but due to me uninstalling gnome-orca (or some of related packages: gir1.2-wnck-3.0 gnome-orca libdotconf0 liblouis-data liblouis2 python3-brlapi python3-louis python3-pyatspi python3-speechd python3-xdg speech-dispatcher speech-dispatcher-audio-plugins xbrlapi). So the timeout also seems to happen when there is no package providing an accessibility API; if this is not fixed upstream, aside of a fix in lightdm the package should carry a dependency on one. But it seems much more reasonable to me to just not make it hang for 1-2 minutes when no accessibility API can be contacted. :) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
