Closed glennDittmann closed 1 year ago
Hey @glennDittmann . Thank you.
If the problem was only with the aseprite
command I'd ask you if you were running godot from a different user (like root). However, as you tried the full path it kind of rules out environment PATH issues.
Another thing that comes to my mind is how Godot was installed? Are you by any chance using an appimage? I'm not too familiar with them but I've heard about appimages with limited disk access.
As soon I have time I'll try running pop os on a virtual machine to give this a try. Let me know in case you solved the issue already.
Hey @glennDittmann I know it has been 2 years but I found the issue.
I faced this exact problem too. It appears to not be an issue with AsepriteWizard but with the Flatpak image available in Pop!_Shop. To mitigate this, download the official executable from Godot's website. Unfortunately, I cannot pin-point what is wrong the the Flatpak Image.
Oooh! Thanks a lot for sharing this. I think you hit the nail. Flatpak apps are sandboxed, so they probably don´t have access to the host folders. I've just searched here and this is a very common case and people use a program called "flatseal" to give permissions to certain directories. Cheers.
Wow, great you found it after all ! :D
Hey, first thanks for the great tool ! I have a problem, as I get the error message above, when testing the command path with the Aseprite Wizard Config.
I can start Aseprite from my terminal with either
aseprite
or/usr/bin/aseprite
. And I have tried both versions for the command path in godot... without success though.Do you have any ideas what could be wrong? (As described in your nice README
/usr/bin/
is in my path.)Best regards Glenn