But none of the external system calls have anything to do with ollama, and I really only use it in Qt Linguist which is referenced through the External Tools menu in Qt Creator. Maybe over the weekend I will have time to investigate further.

I noticed that when ollama is running as my own user, I get a folder .nv in my home directory which has my user listed as owner and group. Presumably, Qt Creator is just checking to see whether it can access Ollama as my user or not, and uses the find command to locate the .nv folder -- perhaps without ever actually needing to use it. If this is the case, "Permission denied" errors should be ignored and not propagated to Qt Creator application output. This is the offending behavior.

Does the .pro file that you open in Qt Creator contain some $$system command or such that triggers find? These might be executed whenever Qt Creator parses the project. You can turn that off in "Preferences > Build & Run > Qmake > Ignore qmake's system() function", but that might also break project loading if that does something essential for your .pro file. The find command might also be triggered by some other included .pri file, or .prf file or by some other tool that is run (no idea what e.g. pkg_config might do for finding packages, though I'd assume that that doesn't do a global find....)

If you can reproduce the issue when running qmake for the project from the command line, you can try running qmake with the "-d" option (possibly multiple 'd's to increase verbosity) to find out what calls find.

No. Why should I have to do that?

Because you would see if that makes a difference and allows it to work. I quoted you where it says it's a temporary directory and can be deleted anyway. But instead of trying that you are welcome to live with the warning message you do not like.

If Ollama sets those permissions by default, then there must be a reason for that, IMHO

The permissions look like they may be fine if/when Ollama runs as ollama user. Your problem seems to be Creator (if that is what is issuing the message) choosing to run some find command, for whatever reason, which may be nothing to do with Ollama itself.

have you tried deleting it or changing its permissions?

No. Why should I have to do that? If Ollama sets those permissions by default, then there must be a reason for that, IMHO.

Yes, you can delete the .nv folder. It is simply a temporary cache. However, the very next time you run a heavy model on your NVIDIA GPU, Ollama and the CUDA driver will automatically regenerate the folder to store the necessary computational kernels.

have you tried deleting it or changing its permissions?

However, I looked at the way ollama installs the directory under /usr/shared . I'm surprised that this could ever work since permissions for the .nv directory are severely restricted::

bob@laptop:/usr/share/ollama$ ls -al
total 40
drwxr-x---   4 ollama ollama  4096 Dec 25 17:23 .
drwxr-xr-x 377 root   root   16384 May 25 12:17 ..
-rw-r--r--   1 ollama ollama   220 Mar 31  2024 .bash_logout
-rw-r--r--   1 ollama ollama  3771 Mar 31  2024 .bashrc
drwx------   3 ollama ollama  4096 Dec 25 17:23 .nv     <== permissions?
drwxr-xr-x   3 ollama ollama  4096 Dec 25 17:23 .ollama
-rw-r--r--   1 ollama ollama   807 Mar 31  2024 .profile

To install ollama, I just followed the instructions given on their website -- nothing special.

Maybe you can use strace to find out who is trying to access the folder.

This feature was added a while ago to help with error messages, and AFAIK it uses ollama.