Timeline for Unable to run flatpak independent of the script that started it
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 15 at 7:17 | answer | added | AnoE | timeline score: 0 | |
| Jul 27, 2023 at 10:20 | answer | added | Vince Pike | timeline score: 0 | |
| Nov 30, 2022 at 15:12 | comment | added | RuntimeException |
Great. Thanks for the info, I will keep that in mind in case I ever face such a thing with bash scripts and flatpaks. I think you may start the flatpak apps by invoking another bash script from the .bashrc itself, if that is what you want. Or start the script that loops from .bashrc using the bash -c ; disown; thing so that it starts in another shell and the .bashrc completes successfully. But anyway, if your problem is solved, then no need to bother.
|
|
| Nov 19, 2022 at 8:22 | comment | added | wayan |
@RuntimeException I still don't understand the inner workings, but https://unix.stackexchange.com/a/352923 has a working solution by preceeding the command with "setsid" and ending with "&", as in setsid /usr/bin/flatpak run --command=de.manuel_kehl.go-for-it de.manuel_kehl.go-for-it &
|
|
| Nov 8, 2022 at 14:11 | comment | added | wayan | @RuntimeException Yeah, that's sort of what I'm doing now. Run the script and start the flatpaks manually. Thanks for your input! | |
| Nov 7, 2022 at 10:16 | comment | added | RuntimeException | You may want to have two separate scripts. One script starts the flatpaks and exits. Then you start another script which loops and checks things. | |
| Nov 7, 2022 at 6:12 | comment | added | wayan | @RuntimeException Thanks! My system complained about the semicolon after the ampersand, i had to remove it. The flatpak now stays active after terminating the script, but still not when the script contains an endless loop like in the original post. | |
| Nov 5, 2022 at 14:37 | comment | added | RuntimeException |
You might want to try bash -c '/usr/bin/flatpak run --command=de.manuel_kehl.go-for-it de.manuel_kehl.go-for-it &; disown; '
|
|
| Oct 27, 2022 at 2:13 | comment | added | wayan | @RuntimeException Thank you for replying! I experimented with your suggestion, but like you, I can't get it to work from a shell script. Oh well. Thanks anyway! | |
| Oct 21, 2022 at 16:06 | comment | added | RuntimeException |
function runapp() { if [ $1 == "geany" ]; then echo file to open [$2]; /usr/bin/flatpak run --command=geany --file-forwarding org.geany.Geany @@ $2 @@ 1>~/logs/geany.out 2>~/logs/geany.out &; disown; return 0; fi } export -f run; declare -f run;
|
|
| Oct 21, 2022 at 16:06 | comment | added | RuntimeException | No luck here either. I finally decided to make a function which I invoke from the terminal to launch flatpaks and disown. Closing the terminal does not close the flatpak applications. Posting function in next comment. I cannot post it in answers because it does not work when launched from a shell script. | |
| Sep 11, 2022 at 9:57 | history | asked | wayan | CC BY-SA 4.0 |