Quote:
Originally Posted by nasser
Coplate, Sorry!
Your search bar command did run! But I failed to see the small "0" it had printed in the top left corner.
I checked the /var/log/messages:
For your command, I got the identical log like yours:
Code:
170823:191337 cvm[4740]: I GoButtonTask:Information::Debug command entered
170823:191337 SCRIPTEXECUTOR[6137]: I script-Executor:main:Ready for execution:Command=/var/local/flash.sh
170823:191342 cvm[4740]: W lipc:perf:prop=executeDebugCommand, source=com.lab126.system, ms=5026:lipc property access took too long
I then tried my ";kt" command to launch kterm. And here's the log I got:
Code:
170823:191637 cvm[4740]: I GoButtonTask:Information::Debug command entered
170823:191637 SCRIPTEXECUTOR[6524]: I script-Executor:main:Ready for execution:Command=/mnt/us/extensions/kterm/bin/kterm.sh
170823:191637 cvm[4740]: E def:jlipc:source=com.lab126.system,name=executeDebugCommand,value=;kt,errcode=2:LipcJNI cannot set string property
170823:191637 cvm[4740]: E GoButtonTask:Error::Cannot perform lipc set prop
170823:191637 cvm[4740]: com.amazon.kindle.util.lipc.LipcException: Cannot Set Property ErrCode=2
170823:191637 cvm[4740]: at com.lab126.linux.arm.LipcImpl.setProperty0(Native Method)
170823:191637 cvm[4740]: at com.lab126.linux.arm.LipcImpl.setProperty(crb:1233)
170823:191637 cvm[4740]: at com.amazon.kindle.util.lipc.impl.LipcTargetImpl.setProperty(uzb:1088)
170823:191637 cvm[4740]: at com.amazon.kindle.restricted.device.chrome.c.M.yK(lvd:488)
170823:191637 cvm[4740]: at com.amazon.kindle.restricted.device.chrome.k.run(poe:254)
170823:191637 cvm[4740]: at java.lang.Thread.run(Unknown Source)
170823:191637 cvm[4740]: at java.lang.Thread.startup(Unknown Source)
It says something about, error code 2, cannot set string property and cannot perform lipc set prop...
Request our experts' help to understand these error messages! |
Quote:
|
170823:191637 cvm[4740]: E def:jlipc:source=com.lab126.system,name=executeDeb ugCommand,value=;kt,errcode=2:LipcJNI cannot set string property
|
You can run the debug commands from the command line, like this: I cannot remember the exact spelling
Code:
lipc-set-string com.lab126.system executeDebugCommand ";kt"
If you if you do that, you will see that same error message from above.
I've only seen this before when trying to run a debug command that had special characters in it, like '%, |, &' and so on trying to inject commands.
You've probably just run into some other protection, maybe 'kt' is reserved, or you cannot use /mnt/us in the command?
Try putting that script into '/var/local' first, or put flash.sh into /mnt/us and see which one fails.