Found this issue on a SLES11 installation which did not have an active license. The effect is that the package repository appears broken to zypper. After installation I ran tl-setup which stopped when trying to install python-ldap with the following output: > Failed to install required packages and dependencies. > Please send a copy of /var/log/tlsetup.log to the ThinLinc support. > Visit http://www.cendio.com/support for information on how to contact us. And tlsetup.log does not contain any information regarding an error whatsoever: 2015-05-07 12:46:34,924: Adding package python-ldap 2015-05-07 12:46:39,210: Resolving packages... 2015-05-07 12:46:39,211: Creating zypper lock... 2015-05-07 12:46:39,211: Locked zypper 2015-05-07 12:46:39,211: Verifying package name python-ldap 2015-05-07 12:46:39,211: Unlocking zypper... 2015-05-07 12:46:39,211: Removed zypper lock 2015-05-07 12:46:39,810: zypper: Loading repository data... 2015-05-07 12:46:39,810: zypper: Reading installed packages... 2015-05-07 12:46:39,810: Creating zypper lock... 2015-05-07 12:46:39,811: Locked zypper 2015-05-07 12:46:39,811: Package python-ldap provides python-ldap 2015-05-07 12:46:39,811: Resolving dependencies for python-ldap 2015-05-07 12:46:39,811: Getting dependencies for python-ldap 2015-05-07 12:46:39,811: Unlocking zypper... 2015-05-07 12:46:39,811: Removed zypper lock 2015-05-07 12:46:55,185: Creating zypper lock... 2015-05-07 12:46:55,185: Locked zypper 2015-05-07 12:46:55,185: Finished dependency resolution 2015-05-07 12:46:55,185: Packages to install: 2015-05-07 12:46:55,185: - python-ldap-2.3.5-1.21.x86_64 2015-05-07 12:47:05,185: Installing python-ldap.x86_64=2.3.5-1.21 2015-05-07 12:47:05,185: Unlocking zypper... 2015-05-07 12:47:05,185: Removed zypper lock 2015-05-07 12:47:20,522: Done 2015-05-07 12:47:20,523: Creating zypper lock... 2015-05-07 12:47:20,523: Locked zypper However, when I run tl-setup again, I get this output: Resolving packages and dependencies... Internal error. The ThinLinc Server Setup Wizard will now terminate. And a traceback in the log, which is described in bug 5522.
*** This bug has been marked as a duplicate of bug 4877 ***