EDA Solutions logo

Tanner on Linux – Resolving the most common installation issues

Published by Khalid Teama – Latest update on 25/6/2021

ID: TN003
Relevant Product(s): L-Edit, S-Edit, T-SPICE, Waveform Viewer, Tanner Designer
Operating systems: Linux RHEL 6 and above
Versions affected: All
Area: Installation


This article will discuss how to resolve common installation issues on Linux, namely the following problems:

  1. “ld-linux.so.2 bad ELF interpreter” error when launching any of the tools

    tanner/win/bin/wine: /lib/ld-linux.so.2 bad ELF interpreter: No such file or directory
  • Nothing happens when invoking the tools, no error or warning messages are shown
  • Seeking further support if the issue persists


“ld-linux.so.2 bad ELF interpreter” error

Note: To resolve this issue, you need to have SUDO privileges on Linux to be able to install the missing shared libraries.

This error is a tell-tale that 32-bit glibc libraries are missing. Please follow these steps to resolve:

  1. Open a terminal window in Linux
  2. Enter the following command:

$ sudo yum install glibc.i686 libXext.i686 libXtst.i686 libXp.i686 ncurses-libs.i686 libXft.i686

The “i686” is the designator for a 32-bit package as opposed to “x86-64”, which identifies 64-bit packages.

  • Retry running any of the tools to test

Nothing happens when invoking the tools, no error or warning messages are shown

This issue could be related to low dedicated video memory on your Linux system. It commonly occurs with Virtual Machines. Before trying the below solution, please make sure you have dedicated at least 64 MB of video memory and retry running the tools to test.

If increasing the video memory does not help, please try the following suggestions to resolve the issue:

  1. Open a new terminal window
  2. Run the command “cleanupwineserver.py” and rerun any of the tools to test
  3. If step 2 did not help, please move the WINE profile folder elsewhere:

The WINE profile directory is usually stored under the $HOME directory and is appended with the version of the tools. Example path when using v2020.3:


To find out the name of your WINE profile directory, you can use the following command:

$ ls -a ~ | grep wine

Once you have the path, please move the directory elsewhere, for example to your Documents folder temporarily:

$ mv .wine-tanner-2020.3 ~/Documents

  • Rerun any of the tools to test

Seeking further support if the issue persists

If the issue is not discussed here, please raise a support ticket describing the behavior and any error messages that show when executing the software.

If no error messages are shown and the tools still do not work, please set this environment variable, and try again to run any of the tools:

$ export WINEDEBUG=+warn

Include in the messages you get after setting the above variable in the support ticket.

Note: please make sure that WINEDEBUG is turned back off after the problem is resolved as it may affect performance.