This very very annoying thing happened to me also on Qubes 3.2. Essentially, on a whonix-based template, (whonix-ws or whonix-gw, doesn't really matter), every time I type something (aside of some basic commands such as sudo, firefox, ls etc) I receive the message:
"Could not find the database of available applications, run update-command-not-found as root to fix this"
If I try to give sudo update-command-not found then whonix tries to curl some files, but not having any connection (template vm) fails. The result of this is that I have to run this command directly in the interested appvm, EVERY TIME I start them up. Is there a way to make whonix communicate with the outside world, so that curl succeeds?
Cheers,
Fab
"Could not find the database of available applications, run update-command-not-found as root to fix this"
Equivalently, you may just directly try to type 'update-command-not-found' and find that the template tries to curl some files without success...
Sometimes, the fact that the template doesn't really distinguish between a command and random stuff typed on terminal gets in the way quite a lot. I remember, for instance, that I had enormous issues trying to install npm: npm installation is performed locally and I didn't know that at the time (I know, I'm a n00b), so I was trying to see what was going on. The output from whonix was always the same: run update-command-not-found.
Essentially what pisses me off is that I'm forced to work with a buggy terminal, which is not really a problem when you know what you are doing but it is a very big issue when you are doing something that requires some heuristics. So if there is a way to fix this I'd be superhappy :D
Cheers,
Fab