Anyone got an autostart appimage command?

Axios

brent I got several appimages I launch but they are in there own directory not downloads
I just added them with startup applications and they work.

brent

Axios give me a 'for example' of a startup command of yours please.
Mate would rather see a DIR rather than the Downloads folder? that makes sense.
Do your appimages live in BIN or OPT or something?

Axios

brent Home/ninja/Appimage/Lanshare/Lanshare.appimage
I think it should work anywhere.

brent

will try it next time I reboot. so Mate it liked the Appimage folder and the folder with the apps name? wonder why it disliked my downloads folder but budgie did like it? so autostart does like the /path/to/file thang but just a certain way? (to a dir).
guess I will answer all my questions soon. thanks Axios ! have a good xmas eve day

Axios

brent lanshare.appimage is the file it’s launching not a directory
Have a good Xmas yourself

brent

Axios OK my Bizarre Theory was right. Or was it yours? Autostart doesn't care for seeing a bare-a** .appimage file just sitting in the downloads folder. I looked it up online. Appimage people themselves reccomend 3 places to store your appimage...........two I forgot but the one I did was create an Applications folder in/home/.local.

In the applications folder I stuck the app in a folder with their name on it. ungoogled-chromium*.appimage went into a folder called ungoogled_chromium in Applications.

so this works:
/home/brent/.local/Applications/ungoogled_chromium/ungoogled-chromium**.appimage
this does not work:
/home/brent/Downloads/ungoogled-chromium**.appimage

As much as I would really want to know why, what the hell could possibly be the difference, and beg my question to the universe, I will let this one pass. I did it your way @Axios.

SOLVED but still a mystery to me🙂

Axios

brent I am creature of habit on computers I do what works
When I download stuff I always test stuff out in a temp folder that way it’s easy to delete if it makes a lot a files if I like it Gets moved to the proper place I honestly can’t say if I have tried running to many apps from downloads

Ran across a guy that complained about your issue he said that kde was the only one that worked properly with appimages and auto start ect

Next time I get one that does not run will pay more attention to it

brent

Axios that kde was the only one that worked properly with appimages and auto start ect

that might be. whatever worked for me so long in Solus stopped working. My apps don't launch consistently (n Bunsen either) with the above /path/to/file and I have to imagine that an appimage suffers from the same thing as Flatpak: uber-sandboxed so always problems with system files etc.

Axios I am creature of habit on computers I do what works

I am too. But things sometimes seem to stop working and have to re-figure it out.

Axios

This is interesting test on an appimage not sure yet of the info

Quote from website
Many AppImages get made using too new ingredients (and not bundling everything), resulting in those AppImages not being able to run on all still-supported LTS releases of major Linux distributions.
So the run on anything linux is kinda misleading
Which I kinda already knew because I have had them not run.

Interesting diff between another appimage you can see it runs on more ubuntu versions

So I would say its just something to be aware of

brent

Axios So the run on anything linux is kinda misleading

absolutely. I have Buster on the deb rig (which shows 'kosher') but they don't always launch. strange (to me) the temp file activity.
great info.

so technically there's a big difference between a terminal command (mostly fail) and a mouse double-click (always successful)?

Axios

brent The top pic was ungoogled chrome and the bottom was Xnview they will be different for every appimage and its prob caused by incorrect packaging be my guess and we all know the funny little problems thats causes on linux

brent

Axios its prob caused by incorrect packaging be my guess and we all know the funny little problems thats causes on linux

when I tried to make my own ungoogled binaries (fail) the instructions say you can save it as an appimage at the very end. huh? many build instructions have a force-over-ride command to gloss over errors and rundeps.
While I knew nothing about package engagement a couple days ago I now know enough fill a tiny doll cup I guess.
I'm learning in the murky world of appimages/debs/forks that some maintainers will spend years dedicated to the project (Eloston the ungoogled creator for example) and some will spend 15 minutes and bail leaving live links to their deprecated product all over the web and you have to be able to tell these things apart...

....the only reason I am in this world is SOME appimage/flatpak browsers know how to utilize a system's dictionaries, some do not. in solus, the flapak ungoogled will not spellcheck me in solus forum. or bunsen. but the appimage will....if its the right maintainer....

brent

Axios https://forums.bunsenlabs.org/viewtopic.php?id=6939

tucked in this thread here is a conversation about 'full path' vs 'relative path' and "/" when running/writing a script...interesting