Cool VL Viewer forum

$ ./CoolVLViewer-1.32.2.24-Linux-x86_64-Setup
invalid command name "bind"
while executing
"::unknown bind Text <Tab>"
("uplevel" body line 1)
invoked from within
"uplevel 1 $next $args"
(procedure "::obj::Unknown" line 3)
invoked from within
"bind Text <Tab>"
(procedure "::InstallJammer::InitializeGui" line 19)
invoked from within
"::InstallJammer::InitializeGui "
(procedure "::InstallJammer::InitInstall" line 68)
invoked from within
"::InstallJammer::InitInstall"
(file "/installkitvfs/main.tcl" line 29794)

System information
CPU(*2): Intel(R) Xeon(R) CPU X5450 @ 3.00GHz (2992 MHz)
Memory: 32095MB
OS version: Linux-x86_64 v6.11.7-artix1-1
Memory manager: jemalloc v5.3.1-20240923
Graphics: AMD RADEON RX 580 SERIES (RADEONSI, POLARIS10, LLVM 18.1.8, DRM 3.59, 6.11.7-ARTIX1-1)
OpenGL version: 4.6 (Compatibility Profile) Mesa 24.2.7-arch1.1
Detected VRAM: 9849MB

That's a first...

The installer is a Tclkit package (i.e. a Tcl/Tk program with its built-in Tcl/Tk interpreter) and it should (and did, in the past 17 years) work just fine on any computer.

Not sure what is happening here, but most likely a configuration or unusual setting issue on your system. Using SELinux, perhaps ?

Here is what to try, in preference order:

• Make sure you are running a X11 session (both the installer and the viewer are genuine X11 applications), not Wayland alone (that can't work at all), and preferably not Wayland+XWayland (XWayland is buggy).
• From a terminal, type:

  	Code: set | grep -i TCL

  If you get TCL* environment variables listed (for example TCLLIBPATH), unset them (e.g. unset TCLLIBPATH) before launching the installer.
• If not already done, install your Linux distro Tcl and Tk packages (if it tries to override the built-in installer Tclkit, it might work just fine with your distro's Tcl/Tk).
• Try installing from a root X11 session (not using sudo, because you will need X11 display access permission, or maybe by typing xhost + before launching with sudo, but it's not guaranteed to work either).
• Try using the "unattended" (command line) installation method described here.
• If all these fail, build the viewer from sources (under Linux, that's easy). Read the linden/doc/LinuxBuildHowto.txt file in the viewer sources for the (few) prerequisites.

Let us know what worked for you...