Can't execute file via dot slash in terminal

[vtpup]

What the heck am I doing wrong?? Is it me? It's gotta be.....

Screenshot121-1.jpg (48.22 KiB) Viewed 236 times

I just did the usual Window>Terminal here in the folder of interest, intending to run it. Why can't terminal find the files?

[vtpup]

Very weird testing after:

so if I shorten the extension of Test it finds it and executes it (ignore the other error messages -- I can deal with those):

# ./Test.App
[0324/122209.238476:FATAL:electron_main_delegate.cc(294)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap

then I tried a little longer extension, also works:

# ./Test.Appima
[0324/122305.002588:FATAL:electron_main_delegate.cc(294)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap

and so on:

# ./Test.Appimag
[0324/122346.183936:FATAL:electron_main_delegate.cc(294)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap

and so forth until...hell now it works full length:

# ./Test.Appimage
[0324/122432.380013:FATAL:electron_main_delegate.cc(294)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
Trace/breakpoint trap

but the unchanged other file doesn't!!??

# ./gSender-1.4.12-Linux-Intel-64Bit.Appimage
bash: ./gSender-1.4.12-Linux-Intel-64Bit.Appimage: No such file or directory

what the heck????

[Trapster]

Your first command in the first photo needs a capital "I" in *Test.AppImage

[Jasper]

How to run a Appimage in Puppy Linux.png (148.7 KiB) Viewed 211 times

[vtpup]

How to run a Appimage in Puppy Linux.png

Yup, thanks, knew that part -- it was the file not found that was the hangup.

[mikewalsh]

@vtpup :-

This is why I usually make my AppImage names as short as possible, Steve.....AND remove the '.AppImage' extension completely. If that was me, I'd rename that to just "gSender64". If it's going to run, it'll run......trust me!

Most of the long-winded names they give these things are for archival purposes, so the individual developer knows exactly what file you're talking about if you ever need to contact them about it. But for actually running/executing it? Nah.

When you execute it in the terminal, it's exactly as though you've clicked on it.....and with an AppImage, what that does is to 'transfer' the executable action to the 'AppRun' file within. Hence, you can name it what you like.....because the outer shell of the AppImage, the bit you see, is just a container for the program itself inside.

I've been doing this for years with these AppImages.....and it always, but ALWAYS, "works". Does that make sense?

Mike.

[vtpup]

Yes Mike! I agree.

I thought I was going crazy re. above until Trapster spotted my idiocy it!

I do have glasses. Obviously I should have worn them that time!

[wizard]

@vtpup

Mikes way is best, but many times have resorted to copy and pasting the file name to eliminate my errors.

wizard