Running command in Run Shell action stopped working after last beta update

24 views
Skip to first unread message

Jiří Netopil

unread,
Nov 24, 2021, 5:27:41 PM (4 days ago) Nov 24
to Tasker
Hi,

this morning my Tasker was updated to 5.15.3-beta version. After that I realized that starting the LinuxDeploy container using the /data_mirror/data_ce/null/0/ru.meefik.linuxdeploy/files/bin/linuxdeploy start -m command in Run Shell action stopped working because of the following error:
23.02.38/E Run Shell: %output -> %output
23.02.38/E Run Shell:  -> 
23.02.38/E Run Shell:  -> 
23.02.38/Shell runBackground /data_mirror/data_ce/null/0/ru.meefik.linuxdeploy/files/bin/linuxdeploy start -m root: true timeout: 15000
23.02.38/Shell start process-thread ID 1357
23.02.38/E add wait type Shell1 time 2147483647
23.02.38/E add wait type Shell1 done
23.02.38/E add wait task
23.02.38/Variables doreplresult: |%output| -> |%output|
23.02.38/E Error: 1

I tried to run other commands in the same directory (for example /data_mirror/data_ce/null/0/ru.meefik.linuxdeploy/files/bin/free) with the same result. But if I change the command in Run Shell action to cat /data_mirror/data_ce/null/0/ru.meefik.linuxdeploy/files/bin/linuxdeploy I get the file content listed. So I have access to this file, but cannot run it.

The file has all executable rights, see here:
$ ls -l bin/linuxdeploy
-rwxr-xr-x    1 u0_a334  u0_a334        179 Jun  7 19:34 bin/linuxdeploy

And I can start the container using the same command from LinuxDeploy own shell or from Termux just fine. In both cases it works. But not from Tasker anymore.

Yesterday, i.e. just while before updating the Tasker I granted the following permission:
net.dinglisch.android.taskerm com.termux.permission.RUN_COMMAND,
but I hope this did not caused this problem. I tried to revoke this permission and i did not helped.

Thank you for any idea on what might be wrong and how to solve it.

Jiri.

Jiří Netopil

unread,
Nov 24, 2021, 5:35:10 PM (4 days ago) Nov 24
to Tasker
One more info. At the time when Tasker was updated this morning, the LinuxDeploy container started from the previous Tasker version was running. Couldn't this messed something? 

Dne středa 24. listopadu 2021 v 23:27:41 UTC+1 uživatel Jiří Netopil napsal:

EW

unread,
Nov 24, 2021, 6:38:32 PM (4 days ago) Nov 24
to Tasker
Lots of discussion in the redit thread on this https://www.reddit.com/r/tasker/comments/qwwenb/dev_tasker_5152beta_target_api_30_for_everyone/?sort=new

Also, check the latest beta - seems like this folder https://drive.google.com/drive/folders/1D9bzragPYBT-v3mIx6OV2ocQlxZMtPr6

Fixed the issue for me.

Jiří Netopil

unread,
Nov 25, 2021, 6:28:45 AM (4 days ago) Nov 25
to Tasker
Great! That was exacly what I needed. I can confirm that the Tasker-5.15.3-beta-20211123_1455.apk version fixed this issue for me too.

Thank you so much!

Dne čtvrtek 25. listopadu 2021 v 0:38:32 UTC+1 uživatel EW napsal:

EW

unread,
Nov 25, 2021, 9:04:50 AM (4 days ago) Nov 25
to Tasker
Glad to help and good to hear that the fix works for you as well.
Reply all
Reply to author
Forward
0 new messages