This is a follow-up to D4725. Not having Krusader path configurable protects against the same scenario: malware running with user's permissions might change the configured Krusader path so that "Start Root Mode Krusader" runs a malicious application with root privileges. While in theory this is less problematic because the user will see the command line they are approving, in practice there are plenty of ways to make it look unsuspicious and most users won't check the command line every time anyway.

There is also a usability aspect here: Krusader might not be installed under PATH, or there might be two Krusader instances installed (particularly for developers). So autoconfiguration won't necessarily do the right thing. In the end, configuring this is unnecessary - there is QCoreApplication::applicationFilePath() which will always point to the correct Krusader instance (namely the one running right now).

I considered adding another special case to KrServices::fullPathName() but Krusader path is being used in exactly one place and using QCoreApplication::applicationFilePath() directly makes the code more obvious.