So after the latest reboot to my laptop, kdeaccessibleapp (or KDE Accessibility) has appeared in my system tray. I cannot quit this program. If I quit, it starts immediately. If I terminate via terminal ot KSysGuard, it starts back up immediately. I have rebooted twice.

The solution found online is to uninstall the app. I have a distaste for workarounds, however, specially when I feel the solution should be simple (i.e. why won't the app quit?) Presumably this is an issue on my end. Any ideas on how to debug? I am using KDE 4.12.3.

Many thanks!

Please check the Accessibility settings in System Settings - disabling them there may help.

I only had one checkbox checked (Use system bell). I unchecked even that and it still does not quit. It is also not in Autostart. Any other ideas?

What is the name of it's process in the System Monitor (KSysguard)?

The name is kaccessibleapp. If I quit via Right Click > Quit, Via KSysGuard (End Process), or terminal (kquitapp or killall) it starts back up immediately.

As it doesn't seem to have a special handler for sigterm/sigseg there'll likely be a watchdog keeping it up or clients start it automatically (from some a11y routines)
This would make sense as /usr/lib/kde4/libexec/* is not supposed to be started by the user.

I can however start and exit kaccessibleapp (regularly, through the systray context) - it does not launch automatically here (while i've only just installed it for testing)

Which distribution are you using?

me? arch.

I am on Ubuntu 13.10 and installed "kubuntu-full" from the kubuntu backports. I have looked around for how to restart an application automatically and the suggestions are cron, /etc/init, and /etc/init.d for Ubuntu. I didn't find anything there.

luebking wrote:As it doesn't seem to have a special handler for sigterm/sigseg there'll likely be a watchdog keeping it up or clients start it automatically (from some a11y routines)
This would make sense as /usr/lib/kde4/libexec/* is not supposed to be started by the user.

I can however start and exit kaccessibleapp (regularly, through the systray context) - it does not launch automatically here (while i've only just installed it for testing)

I do have kaccessibleapp under /usr/lib/kde4/libexec/kaccessibleapp. But I don't follow the rest of your comment.

- a process can intercept it's exits (including "normal" crashes) and perform some action (including self-restart) in this occasion, but kaccessibleapp does not have such code (in the upstream source, ie. ubuntu could have added such and i would not have seen)
- as alternative, a process can of course be launced by other processes that need it (ie. you do sth. and the program thinks: "now i need that a11y app, i'll launch it")
- kde also has a daemon service "kded", it can be configured by "kcmshell4 kded", but i didn't see any a11y related there.

executables in /usr/lib/kde4/libexec are usually not supposed to be called by the user directly, so it would make sense that something else (see above) invokes ka11yapp