Thank you again!
Yes I can see the issue, in my case, in arch, I use appImageLauncher which conveniently moves the .Appimage into a specific folder and “integrate it” into the system. But I agree this goes against the appimage portable principle :)
I took the liberty of using your explanation (with credits) on the new website (wip) , hope its ok! https://drafft.dev/docs/troubleshooting/app-armour-issues
Absolutely that is ok, Thats why i suggested it, thought for sure you would encounter it at some point with another user, and its best to have an answer in some form to solve an existing problem (even if that problem isnt yours its related to something completely different), rather than a user having issues, and potentially giving a low rating for a simple problem.
I love arch, unfortunately i cant use it with the amount of commercial vfx and animation software i use. makes it really hard to use arch. it is my favourite how ever, its both fast and so customizable.
Im stuck with debian based tuxedo (kde) this means i really only have to worry about maya in the initial setup (i do use blender but not for animation, thats what i use maya for). rhel and rhel derivatives are recommended but they are so restrictive when it comes to packages and customisation.
Ahh appimage launcher is a fine program. i have used it many times. i do it manually now. but only because of the way i want my shortcuts to be created (with my attributes, and arguments)
