Baspl++ Frequently Asked Questions

Program installation and execution

1.

Problems with graphics rendering

Problems with graphics rendering can occur, i.e with specific 3D hardware, resulting in bad performance or even program halt. A general remedy to this is to enable the Mesa OpenGL driver rather than making use of the system's OpenGL drive, however at the expense of reduced graphic performance. The Mesa libraries are always shipped with baspl++. To activate the Mesa OpenGL driver, issue

<prefix>/bin/mesa_opengl_enable

from a terminal. To inactivate the Mesa OpenGL driver, issue

<prefix>/bin/mesa_opengl_disable

from a terminal, where <prefix> is the path to the SMR package installation, usually $HOME/smr. You can check which driver is active by launching baspl++ and selecting help -> OpenGL info. If Mesa is active you will see something like

Version: 2.1 Mesa 7.8.2

and if Mesa is inactivated (default), you will see something like

Version: 3.3.0 NVIDIA 260.19.36

2.

Execution of programs: cannot restore segment prot after reloc: Permission denied

Recent releases of Linux® distributions are configured with SElinux enabled. Disable SElinux.

3.

When launching baspl++ under GNOME desktop, the following message appears:

Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-module.so: cannot open shared object file: No such file or directory Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory.

This does not affect the proper working of baspl++. To get rid of the message, add the path /usr/lib64/gtk-2.0/modules to your LD_LIBRARY_PATH environment variable.

Problems and workarounds

1.

Default execution mode opens terminal window.

By default baspl++ places the interpreter shell in the GUI main window. If you want to run the interpreter in the shell from where you started baspl++, please execute baspl++ with the -t option.

2.

Message "Did not find any field that matches the given parameters exactly" appears.

Version 2 message. This message appears if you try to select fields with wrong attributes. Example: When loading a field resulting from a linear analysis with the cycle=0 the message is issued, because, during a linear analysis, there is no cycle defined. This message appears when working with scripts only.

3.

baspl++ main window is too large and cannot be resized.

This can happen if a script is executed which sets the screen size to a value larger that the current screen. Remedy: Consult your window managers help pages.

4.

Printing a scene to a printer fails.

This can happen because Print scene recovers the printers resolution. If the resolution is too high (usually above 300 dpi) the tiling algorithm of baspl++ may fail. Remedy: Make a screen shot instead of trying to print the scene directly.

5.

When trying to print a graph to a printer with Print scene the result is different from the one on the screen.

Symbols and dotted lines in graphs are not rendered properly. Remedy: Make a screen shot instead of trying to print the scene directly.