This is happening due to an issue in kdesudo, where it doesn't actually terminate and thus it doesn't unlock parent processes.
AFAIK this issue is addressed in latest kdesudo source, not yet published though
This is happening due to an issue in kdesudo, where it doesn't actually terminate and thus it doesn't unlock parent processes.
AFAIK this issue is addressed in latest kdesudo source, not yet published though