Re: Some crazy AT-SPI2 delay related to Qt/KDE accessibility

I have QT version 5.11.1 (it's what ships with Fedora 28). I notice you
don't have akonadi running. Do you have it installed? Anyhoo, since you
cannot reproduce the problem, next time it happens I'll see what I can
figure out.

Thanks!
--joanie

On 10/17/18 10:03 PM, chrys wrote:
> Howdy Joanie,
> 
> hehe, no its ok to me. What KDE/ QT version are you using? i us latest
> KDE 5.14.1 with QT Qt 5.11.2. you can see this by type "qtdiag-qt5" in
> terminal. its the first line in output. also working with orca seems to
> be very smooth here.
> 
> I dont see the lag here (but i keep on track), here my output:
>> 21:13:30   pid:   744 kglobalaccel               /usr/bin/kglobalaccel5
>> 21:13:30   pid:   720   kaccess /usr/bin/kaccess
>> 21:13:30   pid:   703   klauncher /usr/lib/kf5/klauncher --fd=9
>> 21:13:30   pid:   724   ksmserver /usr/bin/ksmserver
>> 21:13:30   pid:   733   ActivityManager /usr/bin/kactivitymanagerd
>> start-daemon
>> 21:13:30   pid:   803   xembedsniproxy /usr/bin/xembedsniproxy
>> 21:13:30   pid:   707   kded5                      kded5 [kdeinit5]
>> 21:13:30   pid:   861   kscreen_backend_launcher
>> /usr/lib/kf5/kscreen_backend_launcher
>> 21:13:30   pid:   884   pamac-tray-appindicator
>> /usr/bin/pamac-tray-appindicator
>> 21:13:30   pid:   801   polkit-kde-authentication-agent-1
>> /usr/lib/polkit-kde-authentication-agent-1
>> 21:13:30   pid:   814   kdeconnectd /usr/lib/kdeconnectd
>> 21:13:30   pid:   797   plasmashell /usr/bin/plasmashell
>> 21:13:30   pid:   886   org_kde_powerdevil /usr/lib/org_kde_powerdevil
>> 21:13:30   pid:   765   kwin /usr/bin/kwin_x11
>> 21:13:30   pid:   812   gmenudbusmenuproxy /usr/bin/gmenudbusmenuproxy
>> 21:13:30   pid:   795   krunner /usr/bin/krunner
>> 21:13:30   pid:   997   kuiserver /usr/bin/kuiserver5
>> 21:13:30   pid:  1076   kwalletd5 /usr/bin/kwalletd5
>> 21:13:30   pid:  4291   baloorunner /usr/lib/baloorunner
>> 21:13:30   pid: 12219   Thunderbird /usr/lib/thunderbird/thunderbird
>> 21:13:30   pid: 13312   Firefox /usr/lib/firefox/firefox
>> 21:13:30   pid: 21219   orca /usr/bin/python /usr/bin/orca -l
> 
> cheers chrys
> 
> Am 17.10.18 um 21:03 schrieb Joanmarie Diggs:
>> Hey Chrys.
>>
>> I hope you don't mind being official liaison between me and the KDE
>> community. :) I'm just super busy these days....
>>
>> After I looked into and fixed your Dolphin issue today, I noticed that
>> Accerciser was super unresponsive each time I launched it, ditto for
>> each subsequent launch of Orca. Finally, without Orca running I did an
>> Orca -l to figure out if there was a badly-behaved app. Sure enough
>> there was. Here's the trimmed output:
>>
>> 20:30:02   pid:  2318   gsd-power                  /usr/libexec/gsd-power
>> 20:30:02   pid:  2384   abrt                       abrt-applet
>> 20:30:02   pid:  2398   gnome-software
>> /usr/bin/gnome-software --gapplication-service
>> 20:30:02   pid:  2385   evolution-alarm-notify
>> /usr/libexec/evolution/evolution-alarm-notify
>> 20:30:02   pid:  2419   seapplet                   /usr/bin/python3
>> /usr/bin/seapplet
>> 20:30:17   pid:  3232   (none)
>> /usr/libexec/kf5/klauncher --fd=8
>> 20:30:17   pid: 26081   emacs                      emacs
>> 20:30:17   pid:   564   kdeinit4: kded4 [kdeinit]  kdeinit4: kded4
>> [kdeinit]
>>
>> Notice that a full 15 seconds pass before we get a response from
>> klauncher. 15 seconds.... Since one of the things Orca does upon launch
>> -- and occasionally here and there afterwards -- is obtain the list of
>> running applications, this delay is super awful for Orca users. And
>> since Accerciser creates a tree based on all running apps upon launch,
>> it's a similar issue.
>>
>> Anyhoo, I killed klauncher and did another orca -l looking at the
>> timestamps to find non-responsive (or slowly responsive) apps. After
>> killing klauncher a couple more times (as it kept respawning and being
>> non-responsive), I killed anything starting with "akonadi" or "kdeinit".
>> Now Orca is happy again.
>>
>> Can you reproduce this reliably? If so, could you work with the KDE
>> community to figure out what might be causing this? Like I said, I see
>> the lack of responsiveness using Accerciser without Orca, so I don't
>> think it's an Orca thing.... If you cannot reproduce it reliably, I'll
>> add reporting it to my list.
>>
>> Thanks either way!
>> --joanie
> 
> 
>