3D viewer background transparent when using XRDP
If connecting remotely to a Linux machine using XRDP, the 3D viewers in NORSAR Software Suite can get a transparent background. To fix this, edit the XRDP settings:
Edit the file: /etc/xrdp/xrdp.ini
Change max_bpp=32 to max_bpp=24
Uncomment the line: serverbpp=24
Restart the XRDP server.
Errors when a project is located on the root folder of a disk on Windows
A project located directly on the root folder of a Windows disk can cause various problems. Moving it to a sub folder solves the issues.
This can cause problems:
A project can safely be moved to a sub folder after it has been created.
"KDOPWS: glXMakeCurrent failed!" error when starting NORSAR-3D or NORSAR-3D legacy tools
This can happen when running NORSAR-3D or NORSAR-3D legacy tools using a remote X server solution, like FastX.
It can usually be solved by either enabling indirect rendering (for FastX, see OpenGL Support for legacy apps: https://www.starnet.com/xwin32kb/opengl-support-for-legacy-apps/)
setting the DISPLAY variable to the machine running the X server:
If X server is running on a Windows PC named WinPC, set environment variable DISPLAY=WinPC:0
Cannot mix incompatible Qt library on Linux
Error message when trying to start NORSAR Software Suite on Linux: "Cannot mix incompatible Qt library (version 0x40805) with this library (version 0x40807)"
Unsetting or setting blank QT_PLUGIN_PATH environment variable should fix the problem.
Self extracting installer hangs on Linux
If the self extracing NORSAR Software Suite installer hangs on Linux (never finishes unpacking), you can extract the tar.gz file for manual extraction. To get a tar.gz file type:
tail -n +165 NORSAR_Software_Suite_<version>_Installer.sh > NORSAR_Software_Suite_Installer.tar.gz
Then extract the tar.gz file with:
tar zxvf NORSAR_Software_Suite_Installer.tar.gz
Note: This will extract the files in the current directory.
No text (blank user interface) in some modules
If you experience a blank user interface with no text in some modules, please follow these instructions.
If the user interface is blank again after a restart (after following the instructions above), please update to the latest version of the software.
Fonts are too small or too big in some modules
If you experience too small or too big fonts in some NORSAR-2D or NORSAR-3D modules, you can use a tool called qtconfig-qt4 to adjust the font sizes. qtconfig-qt4 is usually included with most Linux distributions. If you don't have this tool it can be installed using the provided package manager in your Linux distribution.
Font problems when starting NORSAR-2D or NORSAR-3D
- If you get font warning messages like:
"Warning: Cannot convert string "-adobe-courier-bold-r-normal--18-180-75-75-m-*-iso8859-1" to type FontStruct"
the font pack called "A set of 75dpi ISO-8859-1 fonts for X" or "xfonts-75dpi" must be installed on your system.
- If you get messages like:
XngOpenX: Could not find font 8x13
XngOpenX: Could not find font 9x15
the font pack called "ucs-miscfixed-fonts.noarch" must be installed on your system.
The font packs can vary from Linux distribution to Linux distribution. If unsure or the above doesn't solve the problems, install all available font packs: yum install *fonts*
- If you get font warning messages like:
Missing libraries when starting NORSAR software
If you get messages about missing libraries when starting NORSAR software (for example missing libraries libXp.so.6 or libGLU.so.1 etc.), you will have to install these libraries. On RedHat or CentOS, they can be installed by using yum:
As root user, type:
yum search libXp
Only type in the name of the library, not the extensions (.so.6 in this example. Also try without lib if nothing is found). This will show a list of packages, for example:
libXp.i686 : X.Org X11 libXp runtime library
libXp.x86_64 : X.Org X11 libXp runtime library
libXp-devel.i686 : X.Org X11 libXp development package
libXp-devel.x86_64 : X.Org X11 libXp development package
libXpm.i686 : X.Org X11 libXpm runtime library
libXpm.x86_64 : X.Org X11 libXpm runtime library
libXpm-devel.i686 : X.Org X11 libXpm development package
libXpm-devel.x86_64 : X.Org X11 libXpm development package
We want to install the X.Org X11 libXp runtime library. To install the 32-bit version of the library, type:
yum install libXp.i686
To install the 64-bit version, type:
yum install libXp.x86_64
Make sure that you install the correct 32 or 64-bit version, or if you are unsure, install both.
You can also use the yum provides command, but this will sometimes only list the 32 or 64-bit version of a library and also different versions numbers, so yum search is safer to use. Type:
yum provides libXp.so.6
Look for something like this:
libXp-1.0.0-15.1.el6.i686 : X.Org X11 libXp runtime library
yum install libXp-1.0.0-15.1.el6.i686
Error message "NVIDIA: could not open device file /dev/nvidiactl (Permission denied)" in printfile when starting IMAP or Flower Plot
To fix this, log in as root and do the following:
chmod 0666 /dev/nvidia* chown root /dev/nvidia*