Qb64 is inherently broken (simple example)

[JamesAlexander]

Next thing I'd ask is about anti-virus.  Is your QB64 folder in a whitelisted folder?  Is the EXE being quaranteed as fast as it's being generated?

It is Lubuntu Linux, so there generally is minimal intervention or none at all causing this problem from an antivirus standpoint.

I cannot tell if it is getting to the compilation or not, but after combing through the logs and dsman had mentioned "Untitled", I noticed "Untitled2" where it should say "Untitled" and there was a second folder named "temp2", where there should only be "temp" (hence, the original setting).

I am not sure if the Windows version does things under the hood differently from Linux, but it appears that it is very specific in what it wants.

If you deviate from the settings with with another instance, it will try to create that instance, but it will fail. Only then when you go back to the original setting will it succeed as if nothing is wrong.