Version:           unspecified (using Devel) 
OS:                FreeBSD

We already use a QProcess in CliInterface, so there should be no reason for also running it from a separate thread.

Besides all the hell associated to running threaded code, it is unnecessary and causes problems with main loops such as the one in CliInterface::runProcess() -- if CliInterface::failOperation() is called (when a wrong password is entered in a header-protected file), KJob::emitResult() will end up being called somewhere in the call stack, and will terminate the auxiliary thread running our QProcess, finishing the event loop before the process is terminated correctly.

Reproducible: Always