I have an odd problem I am hoping a Linux guru can help me sort out.
The problem is that the play and test buttons do not work. It appears Twine is creating the files in the /tmp/ directory, but that my web browser(s) do not have permission to view those files so I get a 404 error “File Not Found.”
I know the files are there. I can browse to them with the file manager or in the terminal, but no matter how I try to bring them up in the browser, they are invisible.
I assume this is a permission/ownership issue, but I am hesitant to start messing with it without a clue what I am doing. Any help would be appreciated.
It is working out of the box on my Xubuntu 20.04 installation.
First, which web browser are you using? I have had occasional trouble with Chrome and Chromium accessing /tmp files. It seems like Chromium, especially if you’ve installed it through snap, points to its own special /tmp directory that is not the same as the system one.
I’ve had better luck with Firefox…make sure to set it to the default browser even if you’re already using it.
If /tmp files continue to cause issues, you can try exporting a non-temporary file with the menu on the bottom left hand part of the Twine window. [Story title] > Publish to file
If all else fails you try creating a new Ubuntu account. This will at least let you know whether the problem is system-wide.
I started with Firefox and then switched to Chromium just to see if it made any difference. It did not. The issue almost has to be that Twine is creating files that the browser(s) do not have permission to view. I may try creating a new account, but I’m not hopeful. I wish I could fully install the program, rather than just running it from a folder.
Ubuntu recently switched package managers from Apt to Snap. Snap is an improvement from a security point of view. It keeps every application in its own “sandbox,” not allowing it to access any temp files that the app itself did not create. So the browser can’t “see” temp files created by other apps. I think we can all see the problem with that.
Snap is the default package manager for all new Ubuntu installations, so this will come up again.
The solution is to simply uninstall the browser and reinstall it using the old package manager, Apt. Works like a charm.