On Linux, if you are not using a Desktop Manager (for example, GNOME, KDE, Unity), and you are installing the Safeguard Desktop Player with user privileges, registering the .zat, .zatx, and .srs files to the Safeguard Desktop Player might fail. To solve this problem, perform a system-wide installation (run the installer with sudo).
If fonts are not displayed correctly, or the Safeguard Desktop Player application crashes when started in VirtualBox, ensure that you have 3D acceleration enabled (Machine > Settings > Display > Screen > Enable 3D Acceleration), and install VirtualBox Guest Additions.
If these do not solve the problem, see Force software rendering.
Some video card drivers might have issues with OpenGL rendering: fonts do not appear correctly, or the Safeguard Desktop Player application crashes when started with warnings about the graphics card. If this happens, Safeguard Desktop Player tries to fall back to software rendering, but it might fail to do so.
To force software rendering, start the Safeguard Desktop Player using the Safeguard Desktop Player - software rendering item in your application menu, or with the --software command-line option:
Windows: player.exe --software
Linux: ./player --software
Note that on Microsoft Windows, you cannot import CA certificates from a shared drive. In this case, copy the certificate to a local folder and import it from there. Also, the Safeguard Desktop Player application must be installed locally, you cannot start the player.exe file from a shared drive.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
