1

some programs may need other programs, esp. daemons to operate, i.e. padevchooser needs avahi-daemon, and if not present it refuses to start, and whereas in current distributions X is started early, then sometimes daemon may start when KDE session is loaded, therefore 'wait for process before start' option may be useful

This is distro-specific as far as I know. Initing services and daemons are done by the distribution and not for the applications to concern themselves over.

Also, it seems as though padevchooser is a gtk application, and if it chooses the start blindly without checking if necessary daemons are up that's what it chooses to do.

Waiting for somebody with more knowledge on this to give their opinion.

I'm speaking purely hypothetically...
But if this would be Arch I'd edit the order of daemons. Putting avahi-daemon before padevchooser.
And i would do this in rc.conf. For your distro I have no idea...

It would be the same in Gentoo - in fact in Gentoo if padevchooser needed avahi-daemon and didn't have "after/need avahi-daemon" in the init script it would be considered a bug.

I'm willing to close this as a distro-problem unless you can convince me otherwise.