Invalid Command Name

On some Linux systems, you may get the following (or similar) error:

Figure 11-5. Invalid Command Name Error

test@linux-nzgd:/mnt/hgfs/local/setup/Linux-x86> sudo ./ecospro-3.1.1-sam926x-Linux-x86-setup
Error in action ExecuteScript

invalid command name "font"
    while executing
"::InstallJammer::actions::$component $this"
    while executing
"$obj execute"
    (procedure "::InstallJammer::ExecuteActions" line 69)
    invoked from within
"::InstallJammer::ExecuteActions "Setup Actions""
    (procedure "::InstallJammer::ParseCommandLineArguments" line 142)
    invoked from within
"::InstallJammer::ParseCommandLineArguments $::argv"
    (procedure "::InstallJammer::InitInstall" line 62)
    invoked from within
"::InstallJammer::InitInstall"
    (file "/installkitvfs/main2.tcl" line 37426)
    invoked from within
"source [file join $::installkit::root main2.tcl]"
    (file "/installkitvfs/main.tcl" line 3)
test@linux-nzgd:/mnt/hgfs/local/setup/Linux-x86> 

This problem is typically encountered when attempting to run the installer in GUI mode, but the installer does not have sufficient privileges to access the display manager. For example, if you run the installer as a different user from what you have logged in as.

As the installer must install as the root user or an administrator, it always attempts to switch to the root administrator using the appropriate sudo mechanisms. You therefore do not normally need to execute sudo or su to switch to the root user or administrator before running the installer. However, in some cases sudo may not be installed, or may not be set up correctly. In these cases you must either log in as the root user or as an administrator before running the installer, or you must make sure that you permit the root user or administrator access to the display manager if you are logged in as a different user. This is normally achieved through the following command before switching users, where username is either root or the name of the administrative user that will be used when running the installer.

% xhost +username

An alternative solution is to run the installer(s) in console mode. To start in console mode, simply pass the arguments "-mode console" to the installer.

If this problem persists, please contact eCosCentric.

2017-02-09
Documentation license for this page: eCosPro License