If SmartSVN does not start any more on some Linux systems, e.g. Manjaro, the file ~/.config/smartsvn/14.2/logs/log.txt.0 might indicate a problem loading libcrypt.so.1. This could be related to a recent update of the glibc bundle where /usr/lib/libcrypt.so.1 had been removed. To fix this, please find out which bundle contains this file now:
$ pacman -F libcrypt.so.1
On Manjaro one has to install the libxcrypt-compat bundle.
For Linux we are offering since ever a .tar.gz bundle and since a couple of years a .deb bundle.
We recommend the .tar.gz bundle, because
SmartGit, SmartSVN and SmartSynchronize are using SWT as a GUI library. In the Eclipse FAQ you can find the GTK versions which are supported by which SWT version.
If you are a Linux user which has problems with autohiding scrollbars that make it hard to select the last item in a table, tree or text control, you should try to set the environment variable GTK_OVERLAY_SCROLLING to 0 before launching the application. For SmartGit, open bin/smartgit.sh in a text editor and add the line
export GTK_OVERLAY_SCROLLING=0
before the last line.
If SmartSVN fails to load apr-1 on Fedora 30, it most likely is caused by the removal of libcrypt.so.1. To fix, you need to install the libxcrypt-compat bundle:
sudo yum install libxcrypt-compat
If SmartGit 18.2 does not start on your Linux while SmartGit 18.1 worked fine, the reason might be that 18.1 used GTK2 and 18.2 uses GTK3. Use following instructions to let SmartGit 18.2 use GTK2, too:
The tasks 2 and 3 you will need to do after each SmartGit update.
If SmartGit, SmartSVN or SmartSynchronize crashes for you on dialogs where (on other platforms) comboboxes are visible, please check whether the oxygen-gtk style is selected. It is reported to be extremely buggy and better should be replaced with either Adwaita or Clearlooks-Phenix:
Please also check out javaclipse.blogspot.de/2015/06/mars-on-linux.html for alternative hints.