Appendix B. Troubleshooting ThinLinc
B.2.1.7. Couldn’t set up secure tunnel to VNC! (Couldn’t establish SSH tunnel,
SSH terminated.)
This error is caused by failure to connect to the SSH daemon on the selected VSM agent. This could be
caused by the fact that the SSH daemon is simply not running, or that it is not letting the user in for some
reason.
Another possible reason is that there is a firewall between the user and the selected VSM agent that
disallows communication.
B.2.2. Problems that Occur After Session Start
In this section we will discuss some problems that can occur after the successful login, that is, after the
ThinLinc login window has closed. In this phase, a number of session startup problems can occur
B.2.2.1. Session starts, but closes down immediately
If the ThinLinc login window closes, and the session starts up but then immediately shuts down, inspect
xinit.log found in /var/opt/thinlinc/sessions/<username>/last/on the selected VSM agent.
Some of the commands run during session startup will probably have written an error message that will
be stored in that file.
It may also be of value to inspect the VSM agent log on the selected server.
B.2.2.2. At login, user is reconnected to previous, faulty, session
If a previous session still exists and is faulty, for example because of desktop environment failures, the
user is reconnected to the same session when logging in. Disconnect from the session, enable the "End
existing session" checkbox and log in again. That will terminate the current session and start a new one.
B.2.2.3. Login Succeeds, but the ThinLinc Desktop Configuration fails
When using the ThinLinc Desktop Customizer, as documented in Chapter 17, the KDE or Gnome menu
and the entries on the desktop are customized at each login. If this fails, quota problems are very often
the problem. Check the quota of the user in question.
B.2.2.4. Login Succeeds, but KDE Fails to Start
If KDE fails to start, complaining about being unable to create symlinks and similiar, quota problems are
very often the real problem. Check the quota of the user in question.
204
Komentarze do niniejszej Instrukcji