Closed FunFighter closed 9 months ago
It sounds like the Flatpak doesn't have permission to create the ~/stl
folder, although it should (https://github.com/flathub/net.davidotek.pupgui2/blob/master/net.davidotek.pupgui2.json#L31). Even if the user does, Flatpaks have separate permissions as well afaik. I know Flathub has started flagging apps as "potentially insecure", but I wonder if as a result of this, they have changed some default permissions for Flatpaks? Maybe the permission we're setting here for STL is no longer working?
It may be worth checking in something like Flatseal to see if the permission for this folder is not set in your case. You can take a look under the "Filesystem" heading, in the "Other files" section, to see if for some reason ProtonUp-Qt does not have ~/stl:create
.
Out of curiosity, though it should be the same, does this happen with STL-git? It's preferred to use that anyway as v12.12 is very old at this point, so I'm curious if it also affects that ctmod for that reason as well.
Just did a quick check and I can't see anything to suggest the :create
option may have been revoked. Unless I'm looking in the wrong place, the latest Flatpak docs still mention it under "Filesystem Permissions".
That wouldn't necessarily stop Flathub or a software center frontend from enforcing different regulations on Flatpaks, though I imagine this could be pretty bad for Flatpak functionality, so I would think it would be opt-in rather than a default.
Making the directory beforehand shouldn't be a required step, and unless this has been a problem ignored en-mass for a while, the existing ProtonUp-Qt code should be creating the directory (https://github.com/DavidoTek/ProtonUp-Qt/blob/main/pupgui2/resources/ctmods/ctmod_steamtinkerlaunch.py#L276-L277). Unless this stopped working somewhere along the way for some unknown reason, but this ctmod hasn't been touched in a while (the file history is pretty sparse, and I'm hoping to do a little bit of cleanup to bring it in line with some other ctmods in the future). So a change shouldn't have broken this, instead something external must be happening. That's my theory anyway :-)
Thank you for the referral to Flatseal.
The json you linked properly created the permission. It does have access ~/stl:create. I manually deleted ~/stl again and relaunched the program. Installing STL this time worked. Manually deleting ~/stl while the process is live and then installing STL does result in the dir not found error. It seems ~/stl gets created on the launch of the ProtonUp-Qt. However yesterday restarting the process did not create ~/stl.
I am unable to replicate the error today. Assuming an unrelated process to ProtonUp-Qt was blocking the mkdir.
Thank you for the help.
It seems ~/stl gets created on the launch of the ProtonUp-Qt. However yesterday restarting the process did not create ~/stl.
Maybe the folder had wrongs permissions from a previous installation.
Extracting SteamTinkerLaunch... [Errno 2] No such file or directory: '/home/brand/stl/sonic2kk-steamtinkerlaunch-9de3341' rm: cannot remove '/home/brand/stl': No such file or directory brand@taco:~$ ####
I wonder what caused this output...
remove_steamtinkerlaunch
wouldn't delete anything without printing Removing SteamTinkerLaunch compatibility tool
or Removing SteamTinkerLaunch installation
first. tar.extractall
and os.rename
are the only functions that are called before printing Setting up SteamTinkerLaunch
, but it doesn't even come that far.
After some investigation I found that tarfile's tarextract
uses os.makedirs
to create the directory for extraction. Maybe it got confused with the permissions somehow.
I am unable to replicate the error today. Assuming an unrelated process to ProtonUp-Qt was blocking the mkdir.
I think we can close the issue then.
Agreed not able to reproduce. Closing
Process would get frozen because it could not find /home/brand/stl Making the directory fixed the issue. Not sure if should have been installed in a prior step.
mkdir ~/stl
User has permission to write in /home/brand/Desktop
Terminal output
Highlight
Full log