Bug#762672: qt-at-spi: when this package is installed, other programs fail to run
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 noticeably. Normally kile (or other KDE programs) start within
2-3sec and without any of the above stated it takes at least 10-15 sec
or more until the start up screen is coming up.
This is what I get in the shell in this case:
[kound@koundlap:~]$ kile
kdeinit4: Shutting down running client.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before
QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before
QCoreApplication. Application may misbehave.
Qt at-spi: error getting the accessibility dbus address: "Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken."
Connected to accessibility bus at:
"unix:abstract=/tmp/dbus-BrH3Uk3szS,guid=aada46509934349b7895ac9c54b2da53"
Registered DEC: true
Registered event listener change listener: true
kbuildsycoca4 running...
kbuildsycoca4(7474) KBuildSycoca::checkTimestamps: checking file timestamps
kbuildsycoca4(7474) KBuildSycoca::checkTimestamps: timestamps check ok
kbuildsycoca4(7474) kdemain: Emitting notifyDatabaseChanged ()
Qt at-spi: error getting the accessibility dbus address: "Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken."
Connected to accessibility bus at:
"unix:abstract=/tmp/dbus-BrH3Uk3szS,guid=aada46509934349b7895ac9c54b2da53"
Registered DEC: true
...
this it what I get in the other case (2-3 seconds)
kdeinit4: Shutting down running client.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before
QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before
QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
kbuildsycoca4(8663) KBuildSycoca::checkTimestamps: checking file timestamps
kbuildsycoca4(8663) KBuildSycoca::checkTimestamps: timestamps check ok
kbuildsycoca4(8663) kdemain: Emitting notifyDatabaseChanged ()
Object::connect: No such signal
org::freedesktop::UPower::DeviceAdded(QString)
Object::connect: No such signal
org::freedesktop::UPower::DeviceRemoved(QString)
kio_file(8667) kdemain: Starting 8667
kile(8653)/kdecore (KLibrary) findLibraryInternal: plugins should not
have a 'lib' prefix: "libkonsolepart.so"
Object::connect: No such signal
org::freedesktop::UPower::DeviceAdded(QString)
Object::connect: No such signal
org::freedesktop::UPower::DeviceRemoved(QString)
Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes.
kile(8653)/Kate (On-The-Fly Spellcheck)
KateOnTheFlyChecker::KateOnTheFlyChecker: created
...
In case the bug occurs this process are running:
7291 kound
/usr/lib/at-spi2-core/at-spi-bus-launcher
7297 kound \_ /usr/bin/dbus-daemon
--config-file=/etc/at-spi2/accessibility.conf --nofork --print-address
3
7321 kound /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
This is my fluxbox startup script:
logkde='/home/kound/.kde/log'
logprefix='/home/kound/.fluxbox/'
(/usr/bin/kglobalaccel >> $logkde 2>&1)&
(klipper >> $logkde 2>&1)&
(sleep 5 && kmix >> $logkde 2>&1)&
(gkrellm >> ${logprefix}gkrellm.log 2>&1)
&/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1&
pidgin&
skype&
nm-applet
(ck-launch-session dbus-launch fluxbox -log /home/kound/.fluxbox/log)&
2>> $log >>$log
fbpid=$!
wait $fbpid
Don't know if this is my special config but anyway, I decided to remove
qt-at-spi as I fortunately don't accessibility support for myself and if
it still works with a fresh install it seems to be related to my config,
isn't it?
So hopefully people who do need accessibility support won't run into the
same troubles.
Reply to: