Veracrypt. Ownership problem.

cwizardone · 05-27-2016, 09:03 PM

I had noticed a small problem with the previous version of Veracyrpt and now, having just used it, see the same problem with latest version, 1.17. Both packages were from Alien BOB.

When I go to exit, i.e., unmount the container and close the program entirely, it tells me it is still busy. OK, I've seen that, but it this case it is not busy.
So, I bring up the task manger and see there are two entries for the user and two more entries for root. Using the task manager I can terminate the user instances, but have to forcibly kill the root entries.
I have no idea what causes it and it is not a major inconvenience, but I thought it might systematic of another problem.
Any ideas?

Thanks.

cwizardone · 05-29-2016, 11:16 AM

Just used it again and this time the taskmanager showed there were two instances for the user and three for root. To shut it down each instance had to be closed one by one.

titopoquito · 05-29-2016, 02:41 PM

I don't know if it might help you, but I cannot reproduce the problem. I'm running Slackware 14.1 though (32-bit) with the latest veracrypt from Eric. If I mount a volume and click on the "X" on the top right of the window it is staying in the system tray and the output of "ps aux" looks like you describe it.

Code:

# ps aux | grep veracr | grep -v grep
tito      7847  2.6  0.5 215720 22012 tty1     Sl   21:37   0:01 veracrypt
tito      7848  0.0  0.0  49100  2580 tty1     S    21:37   0:00 veracrypt
root      7890 28.3  0.0  49100  3772 tty1     S    21:37   0:09 /usr/bin/veracrypt --core-service
root      7905  0.0  0.0  49100  1692 ?        S    21:37   0:00 /usr/bin/veracrypt --core-service
root      7907  0.3  0.2 100572  8864 ?        Ssl  21:37   0:00 /usr/bin/veracrypt --core-service

If I reopen the window by clicking on the tray icon, unmount the volume and click the "X" again veracrypt gets killed normally. ps shows no more running processes.

I have no Slackware current box to test it, and also no multilib. But at least the two/three processes owned by the user and root should not per se be a problem.