Hello,
Norman Carl Freudenberg, le Tue 06 Jan 2015 12:13:12 +0100, a écrit :
I am using kdm and fluxbox and still get the same problem (kde programs
take up to 2min to start).
With QT_ACCESSIBILITY=0 in the startup script of fluxbox the problem is
fixed.
I tried to reproduce this but
On 11-01-15 17:54, Samuel Thibault wrote:
Again, could you try to reduce service_start_timeout in
/etc/at-spi2/accessibility.conf? I guess the unit is ms, which indeed
makes 12000 two minutes...
No idea if this is a contribution to this bug, but if it is really 12000
(ms) than it is still 12
Paul Gevers, le Sun 11 Jan 2015 20:34:58 +0100, a écrit :
On 11-01-15 17:54, Samuel Thibault wrote:
Again, could you try to reduce service_start_timeout in
/etc/at-spi2/accessibility.conf? I guess the unit is ms, which indeed
makes 12000 two minutes...
No idea if this is a contribution
Well the bug is still there for me.
Either QT_ACCESSIBILITY=0, gsettings set org.gnome.desktop.interface
toolkit-accessibility false OR removing qt-at-spi is fixing it.
Lowering service_start_timeout to 500ms in
/etc/at-spi2/accessibility.conf (and restart kdm) doesn't reduce start
up time
Hello,
Norman Carl Freudenberg, le Tue 06 Jan 2015 12:13:12 +0100, a écrit :
I am using kdm and fluxbox and still get the same problem (kde programs
take up to 2min to start).
Could you try to reduce service_start_timeout in
/etc/at-spi2/accessibility.conf? I guess the unit is ms, which indeed
Hello,
I am using kdm and fluxbox and still get the same problem (kde programs
take up to 2min to start).
With QT_ACCESSIBILITY=0 in the startup script of fluxbox the problem is
fixed.
Maybe of interest: WIthout QT_ACCESSIBILITY=0 there are always two KDE
Accessibility symbols in my tray (I am
Control: severity -1 important
Hello,
lightdm-gtk-greeter has been fixed, both in Debian with a small hack,
and upstream with proper at-spi termination. I believe the severity of
this bug can thus be downgraded to important, since it will not show up
in any normal conditions any more.
Samuel
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
pa...@ucw.cz, le Sun 19 Oct 2014 19:19:34 +0200, a écrit :
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)
I'm very surprised by this happening with gdm3 too, I'd
Samuel Thibault, le Sun 19 Oct 2014 20:12:33 +0200, a écrit :
pa...@ucw.cz, le Sun 19 Oct 2014 19:19:34 +0200, a écrit :
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. :)
I agree. I'm however wondering how much
Hi!
On Sun, Oct 19, 2014 at 08:12:33PM +0200, Samuel Thibault wrote:
pa...@ucw.cz, le Sun 19 Oct 2014 19:19:34 +0200, a écrit :
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
Petr Baudis, le Sun 19 Oct 2014 20:24:25 +0200, a écrit :
However, the picture clearly is more complicated. Right now, I have
lightdm session without lightdm's at-spi running anymore and since I do
not have gnome-orca and its dependencies installed, clearly qt apps
shouldn't be able to
On Sun, Oct 19, 2014 at 08:46:01PM +0200, Samuel Thibault wrote:
Petr Baudis, le Sun 19 Oct 2014 20:24:25 +0200, a écrit :
However, the picture clearly is more complicated. Right now, I have
lightdm session without lightdm's at-spi running anymore and since I do
not have gnome-orca and
Petr Baudis, le Sun 19 Oct 2014 20:57:26 +0200, a écrit :
Not sure how comes, since at-spi as lightdm is still running, but
a second instance running with my uid comes up fine...
That's the idea: managing to shutdown the processes left behind will
probably be not trivial, so my patch just drops
I've made another, even more severe observation.
I'm running a rather mixed setup using lightdm, xfce4-session and kwin
as window manager, started via the session Client0_Command way.
One of the issues I recently had was a freeze at session startup,
disallowing any login unless I reverted to
I confirm that I've encountered this same problem after upgrading from
wheezy to testing, and that removing qt-at-spi solves it. It seems to me
that this bug deserves critical severity, on the basis that it
completely breaks unrelated packages just by being installed.
--
To UNSUBSCRIBE, email
Hello,
Just for the record, this only happens with environment variable
QT_ACCESSIBILITY=1
Also, that actually happens because of #760740, reported upstream as
https://bugs.launchpad.net/bugs/1366534
Perhaps we can make qt-at-spi at least cope with it less badly.
Samuel
--
To UNSUBSCRIBE,
Also, from reading the upstream bug report, I tried killing the dangling
at-spi processes at-spi-bus-laun and at-spi2-registr, and that fixed it
too. The processes seem to respawn after killing, and the new instances
seem to work fine for the session.
Cheers,
Udo
--
To UNSUBSCRIBE, email to
Udo Richter, le Fri 26 Sep 2014 00:11:27 +0200, a écrit :
Also, from reading the upstream bug report, I tried killing the dangling
at-spi processes at-spi-bus-laun and at-spi2-registr, and that fixed it
too. The processes seem to respawn after killing, and the new instances
seem to work fine
Package: qt-at-spi
Version: 0.3.1-4
Severity: normal
new xfce-task recommends orca that depends on this
After installing it, several programs refused to start: vlc, virtualbox,
clementine, amarok, vlc,...
I had orca installed in the past... so I purged qt-at-spi and reinstalled
again. After
20 matches
Mail list logo
