Tarantella Administration Guide > Before you begin > Tarantella Base Component Release Notes

Tarantella Base Component Release Notes

This topic lists the known issues for the Tarantella Base Component. Please read carefully.

The numbers in square brackets [ ] are our reference numbers. If you observe different behavior than we've described in these notes, please let us know, quoting the reference number.

Summary of known issues

Applications
[124987]Users experience some text corruption when using an SCO Console character application object.
[128519]If you use Tarantella to run the xterm program, the xterm program may not end when you expect it to.
[129350]Unable to map the keypad Enter key (KPENTER) on the user's client keyboard to keys found on a real terminal.
[129508]Part of the X root window pattern appears at the edges of Windows applications displayed using the Windows Terminal Services Windows protocol.
[511589]Trying to start an application on a UNIX application server as root does not succeed.
[511963]The Native Client Document Viewer object is not configured with any application when Tarantella is installed on Solaris systems.
[514597]X applications run on the same machine as the Tarantella server fail to launch.
[517146]When using client drive mapping (CDM), in some circumstances two mappings for the same drive display for the same user.
[600935]Whilst running a KDE2 session, the UNIX Native Client appears to be slow or there appears to be a lot of cut and paste traffic on the network.
[601320]Large (complex) images fail to display when accessed on a UnixWare 7.1.1 server using a display other than the local X server.
[601631]Users can't use the numeric keypad in an aixterm application.
[601954]On UnixWare 7.1.1+ and Open Unix 8+, after changing an expired password, a user cannot launch any applications through Tarantella.
Arrays
[513856]A Tarantella server may hang when joining or leaving an array.
[514224]Webtop sessions do not relocate successfully when a user logs in to one Tarantella server without logging out of another.
[517279]A "FATAL ERROR" message is logged when running the array make_primary command.
[600232]The distribution of application launches is skewed towards the servers hosted on a particular UNIX type.
[600380]Clients cannot connect because they cannot resolve the external DNS name or it resolves to an uncontactable IP address.
[600931]When traversing a firewall, attempts to connect to Tarantella either fail or result in error messages. Tarantella may also crash.
Array Manager, Object Manager, and command-line tools
[511140]Changes made using command-line administration tools are not reflected in running instances of Object Manager or Array Manager.
[512334]Some displayed times, for example the session start times shown in the Object Manager Sessions tab, use the wrong timezone.
[512839]Object names appear with different names in other parts of Object Manager.
[513097]In Object Manager, changing the Inherit Parent's Webtop Content attribute for an object doesn't update the Links tab.
[513995]The summary information shown at the bottom of the Sessions tab is wrong for some application objects.
[514014]Users can't start Object Manager or Array Manager.
[600130]A javax.naming.NameNotFoundException warning occurs when you create an object whose name contains a forward slash. The object is not created.
Microsoft Internet Explorer web browsers
[513685]Internet Explorer 4.x users can't log in to Tarantella Enterprise 3 after logging in to Tarantella Enterprise II (or the reverse)
[513920]With Internet Explorer on Microsoft Windows 2000 systems, users are unable to log in to Tarantella.
[601214]On Windows 98SE Internet Explorer 6 fails to connect to Tarantella when a DNS lookup is unavailable.
[601286]On Windows 2000 and Windows XP, some users are unable to download and install the Tarantella distribution units (cab4 files).
Netscape web browsers
[510747]With Netscape browsers on UNIX or Linux client devices running the Enlightenment window manager, applications configured to display using Client Window Management do not appear correctly.
[512669]Netscape users can't log in to the current release of Tarantella after logging in to an earlier release.
[514003]With Netscape browsers on Red Hat Linux client devices, the Caps Lock and Num Lock keys do not work as expected with a VT420 character application.
[514144]Unable to cut and paste between Tarantella applications running under Netscape Communicator 4.05+ on UNIX and local applications.
[514398/9]Netscape browsers on Linux client devices freeze (using 100% of CPU) or exit randomly.
[601214]Netscape Navigator 4.x fails to connect to Tarantella when a DNS lookup is unavailable.
[601228]After upgrading to Tarantella Enterprise 3 version 3.2, Netscape 6.x users with customized webtop themes cannot use client drive mapping.
[601576]With Netscape 6.x, you cannot use JavaScript to call Java™ technology. This means you cannot use proxy autoconfig processing or run web applications.
Printing
[600841]Users can't print from Tarantella using the Common UNIX Printing System (CUPS).
[601300]When Tarantella printing has been disabled, print jobs can still be queued.
Tarantella installation
[601586]The Tarantella installation script on Linux hangs in some circumstances.
[601858]Tarantella Enterprise 3 version 3.2 installation fails when installing on UnixWare 7.1.1.
Tarantella Native Client for UNIX
[515536]The webtop displays with the left-hand pane significantly wider than the webtop object buttons.
[515624]Highlights within the window bar may be rendered as black boxes instead of the Solaris 3D effect.
[515726]Vt420 applications sometimes start with a '>' prompt.
[515734]There are problems with specifying the initial size of a window, either from the command line or from the application defaults file.
[516453]Support is required for multiple font set definitions for localization to languages with 16-bit character sets.
[516519]Cannot type the Euro character using ALT+0128 (on the numeric keypad).
Tarantella Native Client for Windows
[516519]Cannot type the Euro character using ALT+0128 (on the numeric keypad).
Upgrading from Version 1.4x (Tarantella Enterprise II)
[513683]Custom webtop, login and icon themes are not always upgraded successfully.
[514279]Some customized login scripts may need changes to be used with this release.
Upgrading from Tarantella Enterprise 3.0x
[516098]Password cache and web cache entries are lost for users who log in using the LDAP login authority.
Web servers
[125591]Users can't download the Tarantella Native Client.
[515326]An EAPI warning message is displayed when starting the Apache webserver.
[515788]Unable to find matching tokens when connecting to the Netscape webserver.
[601657]The Apache event log shows a "Premature end of script headers" error every time a user logs in to Tarantella.
[601888]Users are unable to download Tarantella Java™ archives.

Applications

Problem Using an SCO Console (SCO OpenServer 5.0.5+) character application object to run applications such as SCO Shell (scosh) and SCOadmin (scoadmin), users experience some text corruption. [124987]
Cause The tab3 terminal setting is not set.
Solution To correct this, set the tab3 terminal setting by entering "stty tab3" at the system prompt.
Problem If you use Tarantella to run the xterm program, the xterm program may not end when you expect it to. For example, if you set its application object's Resumable attribute to Tarantella Webtop Session, the application may not end when users log out of Tarantella. [128519]
Cause This is a problem with the xterm binary on UnixWare 7.
Solution Make sure the application object's Keep Launch Connection Open attribute is checked.
Problem It is not possible to map the keypad Enter key (KPENTER) on the user's client keyboard to keys found on a real terminal using Tarantella terminal emulators. [129350]
Cause Limitations in current versions of the virtual machine for the Java™ platform ('Java Virtual Machine' or 'JVM') on client devices.
Solution Future revisions of client device JVMs may resolve these limitations.
Problem Part of the X root window pattern may appear at the edges of Windows applications displayed using the Windows Terminal Services Windows protocol. [129508]
Cause This occurs if the Windows application's width or height attribute is not a multiple of 4.
Solution Define the width and height to be multiples of 4.
Problem On any user's webtop, trying to start an application on a UNIX application server as root may not succeed. [511589]
Cause On most UNIX systems, the root user is not normally allowed to log into the system remotely, for example using telnet.
Solution Start applications as another user, or configure your UNIX system to allow root to access the system remotely. See your UNIX documentation.
Problem The Native Client Document Viewer object is not configured with any application when Tarantella is installed on Solaris systems. [511963]
Cause Tarantella Setup attempts to find Netscape binaries. If it can't, for example if Netscape Navigator is installed on another application server or in a non-standard location on the Tarantella server, it leaves the Application attribute blank.
Solution Using Object Manager, enter the full pathname for Netscape Navigator into the Application attribute of the Native Client Document Viewer object, located in the Tarantella System Objects organization.
Problem X applications run on the same machine as the Tarantella server fail to launch, reporting an error such as "Can't open display: unix:10" in the application launch dialog's Launch Details area. [514597]
Cause X applications built with the UDK on OpenServer may not work if the DISPLAY environment variable is set to "unix:n".
Solution In Object Manager, ensure that the Command-line Arguments attribute of your X application object contains the following setting: 
-display $ALTDISPLAY
Problem When using client drive mapping (CDM), in some circumstances the drive displayed has a strange name. [517146]
Cause A known issue.
Solution Increase the default timeout values in the Windows registry for the client drive mapping application (ttatdm.exe) on the application server. To do this:
  1. In the Windows Registry Editor (regedit), drill down to the
    HKEY_LOCAL_MACHINE\Software\Tarantella, Inc.\Enhancement Module for Windows key.
  2. Double-click Initial Timeout. The Edit DWord Value window displays.
  3. In the Base part of the screen, click Decimal.
  4. In the Value data field increase the value to something like 8000. (The value is in milliseconds and the default is 3000.)
  5. Click OK.
  6. Double-click Subsequent Timeout. The Edit DWord Value window displays.
  7. In the Base part of the screen, click Decimal.
  8. In the Value data field increase the value to something like 8000. (The value is in milliseconds and the default is 1000.)
  9. Click OK.
  10. Close the Registry Editor.
  11. Reboot the server for the change to take effect.
Problem Whilst running a KDE2 session, the UNIX Native Client appears to be slow or there appears to be a lot of cut and paste traffic on the network. [600935]
Cause The problem is caused by the klipper application which comes with KDE 2.x.
Solution Quit the klipper application in the panel at the bottom of the screen.

Alternatively:

  • On KDE 2.0.x you can edit $BIN/startkde and remove the line that starts klipper, or
  • On KDE 2.1.x you can remove $KDEDIR/share/autostart/klipper.desktop to stop klipper starting when you start a KDE session.
Problem Large (complex) images fail to display when accessed on a UnixWare 7.1.1 server using a display other than the local X server. [601320]
Cause The TCP extensions for high performance (rfc1323) are switched on by default on UnixWare servers. If the Tarantella server is installed on another operating system, rfc1323 may not be switched on by default or it may not be supported.
Solution Either switch on rfc1323 on the host where Tarantella is installed or switch it off on the UnixWare server.
Problem Users can't use the numeric keypad in an aixterm application. [601631]
Cause A known issue.
Solution The X application keyboard map file needs to be adjusted for aixterm. The keyboard map files can be found in the install_dir/etc/data/keymaps directory.

Add the following entries at the end of the file:

KEYMORPH  96 0 0
KEYMORPH  97 1 1
KEYMORPH  98 2 2
KEYMORPH  99 3 3
KEYMORPH 100 4 4
KEYMORPH 101 5 5
KEYMORPH 102 6 6
KEYMORPH 103 7 7
KEYMORPH 104 8 8
KEYMORPH 105 9 9
KEYMORPH 110 period period

These entries change what is sent to the application when a key is pressed. For example, keycode 96 is mapped to KP_0, however the key morph entry causes 0 (zero) to be sent.

Note Make sure you edit the correct map for your locale, for example xuk.txt for English (United Kingdom).

Problem On UnixWare 7.1.1+ and Open Unix 8+, after changing an expired password, a user cannot launch any applications through Tarantella. [601954]
Cause UnixWare 7.1.1+ and Open Unix 8+ do not correctly handle password changes through the PAM (Pluggable Authentication Module) interface.
Solution The workaround is to install the Linux Kernel Personality (LKP) on the host on which Tarantella is installed.

Arrays

Problem A Tarantella server may hang when joining or leaving an array, if other servers are simultaneously joining or leaving the array. [513856]
Cause A thread deadlock between a thread on the primary server and a thread on the secondary server.
Solution We recommend that you add or remove servers from an array one by one. If you experience this problem, use tarantella stop --kill on the secondary server.
Problem If the clocks on all array members are not synchronized, webtop sessions may not relocate successfully when a user logs in to one Tarantella server without logging out of another. [514224]
Cause The timestamps on the webtop sessions determine which is newer. The newer webtop session is considered to be current. If clocks are not synchronized, the timestamps may give misleading information.
Solution Make sure that clocks are synchronized between Tarantella servers in the array. For example, you can use rdate.
Problem A "FATAL ERROR" message may be logged when when running the array make_primary command if a synchronization is occurring elsewhere in the array. [517279]
Cause This error message is displayed as a consequence of the data distribution mechanism readjusting after the array topology has been changed.
Solution In these circumstances, the error message is innocuous and may safely be ignored.
Problem In an array of Tarantella 3.01/3.00 servers using CPU-based load balancing which are hosted on a mixture of UNIX platforms (for example, Solaris and Linux), the distribution of application launches can be skewed towards the servers hosted on a particular UNIX type. [600232]
Cause A known issue.
Solution There is a partial solution available with Tarantella 3.11 which has not been available before.

The load of each server in the array is measured periodically as the CPU idle percentage. This is multiplied by a per-server weighting factor to form a weighted idle value which is replicated around the array for use in launch decisions. When an application launch decision is to be made, the servers in the array are categorized (by weighted CPU idle value) into two sets of servers: the least-loaded set and the most-loaded set. After this the Adaptive Internet Protocol (AIP) routing constraints determine the choice of server made from the least-loaded set and the choice is not necessarily the server with the highest weighted CPU idle value.

The default weighting is 100 and can be found in
/opt/tarantella/var/serverconfig/local/server.properties
in the property tarantella.config.server.tier2loadbalancing.weighting.
This value can be changed using a suitable editor. The new value takes effect when the server is restarted.

In an array, increasing the weighting increases the likelihood of launches being made on a server and decreasing the weighting decreases the likelihood of launches on a server, assuming that the weightings on all of the other servers in the array remain unchanged.

In an array of Tarantella servers on different UNIX platforms (for example, Linux and Solaris) of roughly the same power, it is expected that the effect of a launch (the amount by which each successful launch affects the CPU idle percentage) will be UNIX platform dependent and that each launch will show less of an impact on Solaris than on Linux. Therefore, in these circumstances, we suggest you use a weighting of 50 on the Solaris servers versus the default value of 100 on the Linux servers. Beyond that, to get an even spread of launches across disparate servers, it is a matter of trying different values for the weighting until you achieve the desired effect.

Note:

  1. The primary server in an array is more heavily loaded than a secondary because it is the primary. It should not be expected to handle the same number of launches as a secondary server. In a very large array, it may be prudent to set the weighting of the primary server to 0 so that it handles no launches at all.
  2. The CPU idle is measured as a percentage and so is in the range 0-100. The weighted idle must fit into a signed 32-bit integer so weightings in excess of 21,000,000 are not recommended. In practice, weightings should be kept to much smaller numbers than this (for example, < 1000).
  3. CPU-based load balancing of an array where all of the servers in the array run the same UNIX platform and are of similar power is known to work successfully in Tarantella 3.01/3.00.
Problem Clients cannot connect because:
  • they cannot resolve the external DNS name from the network they are on, or
  • they can resolve the name but it resolves to an IP address uncontactable from the network they are on.
[600380]
Cause Clients connect to the server by using the external DNS name. This name may only be resolvable by a DNS server located on an internal network, so clients external to this network may not be able to resolve it. Alternatively the name may be resolvable but the IP it resolves to may only be accessible via either an external or an internal network (for example if a server has two network interface cards, one connected to an internal network and one connected to an external network).
Solution Ensure the client can resolve the external DNS to an IP address that it can connect to. To do this either:
  • Configure DNS to return a different IP address for the external DNS name depending on which network the client is accessing it from. This means the external DNS name from a client on the internal network would give a different IP address from a client connecting from an external network, or
  • Amend the clients' hosts files so that the external name is resolves to the appropriate IP address connectable by that client.

Example:

The external name of the server is www1.indigo-insurance.com.
The server has two network interface cards (NICs), one connected to the company's internal network and one connected to an external network (for example, the internet).

The IP address of the internal NIC is 192.168.10.13.
The IP address of the external NIC is 192.168.10.57.

Clients on the internal network should be configured (either using DNS or in their hosts files)
to resolve www1.indigo-insurance.com as 192.168.10.13.

Clients on the external network should be configured to resolve www1.indigo-insurance.com as 192.168.10.57.

Problem When traversing a firewall, attempts to connect to Tarantella either fail or result in error messages. Tarantella may also crash. [600931]
Cause In the default configuration of firewall forwarding, the web server is set to listen to 127.0.0.1:443.

If the Tarantella server is started before the web server is started, Tarantella uses all the interfaces which results in web connections being proxied to itself in an infinite loop. The connection fails and may result in Tarantella crashing.

If the web server is started before the Tarantella server, an error message displays. The error appears to be serious but is in fact harmless.

Solution If you want to use firewall traversal and avoid these issues, you must:
  1. Configure the web server to bind only to the 127.0.0.1 (local host) interface, and
  2. Configure Tarantella to use all the other interfaces.

Consult your web server documentation for information on how you configure the web server to bind only to the 127.0.0.1 interface.

To configure Tarantella to use all the other interfaces, run the following command: 

tarantella config edit --tarantella-config-server-bindaddresses-external \
  "!127.0.0.1"

If you wish to specify exactly which other interfaces you want Tarantella to use, run the following command: 

tarantella config edit --tarantella-config-server-bindaddresses-external \
  "[comma-separated list of DNS names and/or IP addresses]"

Note On some shells you cannot use double quotes ("!127.0.0.1") as the !127 may get substituted. Use single quotes instead ('!127.0.0.1').

Array Manager, Object Manager, and command-line tools

Problem Changes made using command-line administration tools are not reflected in running instances of Object Manager or Array Manager. [511140]
Cause Simultaneous configuration by more than one administration tool is not supported, and may lead to inconsistencies in the datastore.
Solution Do not run more than one administration tool (for example, the tarantella object command and Object Manager) at the same time.
Problem Some displayed times, for example the session start times shown in the Object Manager Sessions tab, use the wrong timezone. [512334]
Cause The timezone is not supported by JDK™ 1.1.
Solution Edit the install_dir/etc/data/timezone file to define your timezone. See the file for instructions. Alternatively, you can set the TZ environment variable to the POSIX description of your timezone before you start Tarantella.
Problem The characters backslash \ and plus + cause problems in object names, appearing with different names in different parts of Object Manager. [512839]
Cause These are special characters that must be escaped, using a backslash \. In this release, Object Manager escapes them inconsistently.
Solution We recommend that you avoid using backslash \ and plus + characters in object names.
Problem In Object Manager, changing the Inherit Parent's Webtop Content attribute for an object doesn't update the Links tab. [513097]
Cause A known Object Manager issue.
Solution To update the Links tab, choose Properties for the object again.
Problem The summary information shown at the bottom of the Sessions tab may be wrong for some application objects (upgrades from Tarantella version 3.0 only). [513995]
Cause Part of the object name is passed to the case-sensitive views table in lower case characters.
Solution Stop the server and remove the file install_dir/var/ens/.object. Restart the server. Ignore the error message.
Problem Users can't start Object Manager or Array Manager if there is an apostrophe ' within their person object name (for example, .../_ens/o=Indigo Insurance/ou=Bill's OU/cn=Bill Orange). [514014]
Cause A known issue.
Solution We recommend that you avoid using apostrophes in object names.
Problem A javax.naming.NameNotFoundException warning occurs when you create an object whose name contains a forward slash. The object is not created. [600130]
Cause Tarantella interprets the forward slash as a part of the organisational hierachy. For example, if you try to create an object with the relative name cn=a/b beneath o=organisation , Tarantella will try to create an object called b within the o=organisation/cn=a object. This fails because o=organisation/cn=a does not exist.
Solution If you use a forward slash, you must backslash protect (escape) it. For example, to create an object with the relative name cn=a/b beneath o=organisation, type cn=a\/b. This will create an object o=organisation/"cn=a/b".

Microsoft Internet Explorer web browsers

Problem Internet Explorer 4.x users can't log in to Tarantella Enterprise 3 after logging in to Tarantella Enterprise II (or the reverse). [513685]
Cause Internet Explorer 4.x uses the wrong set of Java™ archives when connecting to the Tarantella server.
Solution Users should do either of the following:
  • Log out of Windows and log back in again before switching Tarantella versions.
  • Upgrade to Internet Explorer 5.x.
Problem With Internet Explorer on Microsoft Windows 2000 systems, users are unable to log in to Tarantella. The Tarantella splash screen doesn't progress to the login page. [513920]
Cause Our tests indicate that Windows Administrator privileges are needed to install the Tarantella Java™ archives for Internet Explorer on Windows 2000 systems.
Solution Users should log in to Windows 2000 as a Windows Administrator before trying to log in to Tarantella for the first time. After the archives are installed, Administration privileges are not required when logging in to Tarantella.
Problem On Windows 98SE Internet Explorer 6 fails to connect to Tarantella when a DNS lookup is unavailable. [601214]
Cause The virtual machine for the Java™ platform ('Java Virtual Machine' or 'JVM') needs a DNS lookup to be able to download the Java archives. If there is an entry, or even if the entry resolves to the wrong IP address, Intenet Explorer will be able to connect to Tarantella. Internet Explorer 5 on Windows 98SE and Internet Explorer 6 on Windows 2000 do not seen to be affected by this problem.
Solution The solution is to add a name resolution entry for the Tarantella server into the hosts' files (in C:\windows).

Note This does not have to be the correct IP address (for example, 127.0.0.1 will work).

Problem On Windows 2000 and Windows XP, some users are unable to download and install the Tarantella distribution units (cab4 files). [601286]
Cause Users without Administrator privileges are unable to download and install the Tarantella distribution units because this involves write-access to the Windows registry and possibly also to the Windows directory.
Solution Tarantella now supports cab archives which are cached and not installed. However, users who have already installed Tarantella distribution units may have problems connecting to Tarantella or accessing new functionality. This is because Internet Explorer uses the installed 3.1x archives in preference to the cached 3.20 archives. The only solution is for users to remove the installed archives.

Note You can control which distribution unit all users receive by editing the install_dir/etc/data/archives.txt file. An alternative is for individual users to visit the URL http://server/tarantella/cgi-bin/ttaarchives.cgi?cab before they log in to Tarantella. This forces the browser to use the cab archive but this only lasts for the browser session lifetime. For information on either of these options, see Tarantella and Java™ archives.

Netscape web browsers

Problem With Netscape browsers on UNIX or Linux client devices running the Enlightenment window manager, applications configured to Display Using Client Window Management may not appear correctly. [510747]
Cause Issues concerning the compatibility of the Enlightenment window manager with Netscape browsers.
Solution Use an alternative window manager on the client device.
Problem Netscape users can't log in to the current release of Tarantella after logging in to an earlier release, if the earlier and current releases both used the Tarantella Security Pack. The Java™ archives download, but the login page doesn't appear even after restarting the browser. [512669]
Cause Problems with Netscape browsers and Java archives.
Solution If the Tarantella Security Pack is in use, users must delete archives from earlier releases of Tarantella before connecting to the current release.

To delete the earlier archives: On the Edit menu, click Preferences. Open the Advanced category, and then click SmartUpdate. Select both "Tarantella Framework Java Archive" and "Tarantella Security Java Archive", and then click Uninstall.

Problem With Netscape browsers on Red Hat Linux client devices, the Caps Lock and Num Lock keys do not work as expected with a VT420 character application. [514003]
Cause Problems with Netscape browsers on this platform.
Solution The problem may be fixed in a future release of the browser.
Problem Unable to cut and paste between Tarantella applications running under Netscape Communicator 4.05+ on UNIX and local applications. [514144]
Cause The Netscape JDK™ clipboard does not interact with the X clipboard. See http://developer.netscape.com/software/jdk/relnotes_unix.html.
Solution There is no known solution.
Problem Netscape browsers on Linux client devices may occasionally freeze (using 100% of CPU) or exit randomly. [514398, 514399]
Cause There are problems with the virtual machine for the Java™ platform ('Java Virtual Machine' or 'JVM') with this browser. The problems may occur on any web page that includes Java technology, and are not restricted to web pages used for Tarantella.
Solution Users should if necessary kill the runaway process, then restart the browser and log in again. Some applications may be resumable, so no work is lost.

Future releases of Netscape may include JVM improvements.

Problem Netscape Navigator 4.x fails to connect to Tarantella when a DNS lookup is unavailable. [601214]
Cause The Media Tracker within the virtual machine for the Java™ platform ('Java Virtual Machine' or 'JVM') needs a DNS lookup to be able to download the Java archives. If there is an entry, or even if the entry resolves to the wrong IP address, Netscape will be able to connect to Tarantella.
Solution The preferred workaround is to add the following entry to the user's Netscape User Preferences file:
user_pref("security.lower_java_network_security_by_trusting_proxies", true");

The file usually lives in:
program files\Netscape\users\username\prefs.js (Windows)
user_home/.netscape/preferences.js (UNIX)

Note Only edit this file when Navigator is not running, otherwise the file will be overwritten when Navigator exits.

An alternative solution is to add a name resolution entry for the Tarantella server into the hosts' files.

Note This does not have to be the correct IP address (for example, 127.0.0.1 will work).

Problem After upgrading to Tarantella Enterprise 3 version 3.2, Netscape 6.x users with customized webtop themes cannot use client drive mapping. [601228]
Cause A known issue.
Solution In Tarantella Enterprise 3 version 3.2, all four default webtop themes have been adjusted so that the print and client drive mapping applets no longer share the same frame. This fixes the problems with client drive mapping when using Netscape 6.x.

If you have customized your webtop themes and Netscape 6.x users experience problems with client drive mapping, you will need to make the same change.

Problem With Netscape 6.x, you cannot use JavaScript to call Java™ technology. This means you cannot use proxy autoconfig processing or run web applications. [601576]
Cause The scripting of applets is not supported when using the Java Plug-in with Netscape Navigator 6.x and either the <OBJECT> or <EMBED> tags. JavaScript is supported if the <APPLET> tag is used. However Netscape 6 and Java seem to be less stable when <APPLET> tags are used.
Solution Either:

Printing

Problem Users can't print from Tarantella using the Common UNIX Printing System (CUPS). [600841]
Cause Extra configuration is required because /user/bin/lp will not work with CUPS.
Solution To be able to print using CUPS, the following extra configuration is needed:
  1. Enable the CUPS LPD compatibility mode. This allows CUPS to accept remote print jobs from LPD clients. If you you don't have any LPD clients on your application server, this step is optional. The CUPS Software Administrators Manual explains how you enable LPD compatibility mode.
  2. Enable 'raw printing' in CUPS by editing the /etc/cups/mime.conv and /etc/cups/mime.types files. These files contain comments explaining how to do this (search for 'raw').
  3. Run the prtinstall.en.sh script provided with Tarantella to configure a printer on a UNIX application server.
  4. Print using install_dir/bin/lp.

Limitation: LPD print jobs from Windows NT systems fail, this is a known issue.

Problem When Tarantella printing has been disabled, print jobs can still be queued. [601300]
Cause After disabling the Tarantella print system by running tarantella print stop, it is still possible to spool print jobs on application servers. These jobs will remained queued until Tarantella printing is restarted.
Solution To prevent these print jobs from being submitted, Tarantella Administrators must manually disable the Tarantella print queue on the application servers.

Tarantella installation

Problem The Tarantella installation script on Linux hangs in some circumstances. [601586]
Cause A known issue.
Solution Run ps -ef to see if the command lpc reread is running. If it has been running for more than a minute or so, kill it. The installation should then complete successfully.
Problem Tarantella Enterprise 3 version 3.2 installation fails when installing on UnixWare 7.1.1. [601858]
Cause Out of date UnixWare UDK FS runtime library packages.
Solution UnixWare 7.1.1 needs new/updated UDK FS runtime library packages (libc.so.1, libC.so.1 and libm.so.1) in order to use Java™ 2 version 1.3.0. Download the packages from the Caldera download site. On this site select UnixWare and OpenServer Development Kit Feature Supplement 7.1.1b and then select the udkrtfs package.

Tarantella Native Client for UNIX

Problem The webtop is first displayed with the left-hand pane significantly wider than the webtop object buttons. [515536]
Cause A known issue.
Solution Resize the webtop frame.
Problem On the HP-UX port of the Tarantella Native Client for UNIX, highlights within the window bar may be rendered as black boxes instead of the Solaris 3D effect. [515624]
Cause A known issue.
Solution This problem will be resolved in a future release.
Problem If your login password ends in an unusual character, vt420 applications may sometimes start with a '>' prompt. [515726]
Cause A known issue.
Solution Type 'CTRL-C' to return to the regular command prompt.
Problem There are problems with specifying the initial size of a window, either from the command line using '-geometry' or from the application defaults file. [515734]
Cause A known issue.
Solution A partial workaround is to set the size of the webtopFrame to half the required width: 
./ttwebtop -xrm "*webtopForm.width:512" -xrm "*webtopForm.height:768"
Problem Support is required for multiple font set definitions for localization to languages with 16-bit character sets. [516453]
Cause A known issue.
Solution This problem will be resolved in a future release.
Problem Cannot type the Euro character using ALT+0128 (on the numeric keypad). [516519]
Cause The Tarantella Native Client for UNIX does not support this method of typing the Euro character.
Solution Type the Euro character using ALT GR+4.

Tarantella Native Client for Windows

Problem Cannot type the Euro character using ALT+0128 (on the numeric keypad). [516519]
Cause The Tarantella Native Client for Windows does not support this method of typing the Euro character.
Solution Type the Euro character using ALT GR+4.

Version 1.4x (Tarantella Enterprise II)

Problem Custom webtop, login and icon themes are not always upgraded successfully. [513683]
Cause The directory structure of webtop, login and icon themes has changed significantly from previous releases of Tarantella.
Solution When upgrading, Tarantella Setup tries to convert any customized themes to the new format. However, you may still need to modify your upgraded customized themes to fix any problems. Known problem areas:
  • Customized webtop themes must not use any "shared" files, such as graphics files, from any of the default themes.
  • Any icons added to the 32x32 standard icon theme are correctly copied to the install_dir/var/docroot/resources/icons/sco/tta/standard directory. However, the sco/tta/standard icon theme in this release uses 24x24 icons. If your custom webtop theme uses 32x32 icons, you will see your custom icons but none of the new sco/tta/standard icons. To fix, create 24x24 custom icons. Alternatively, you can use the original 32x32 standard icon theme by specifying the IconTheme webtop tray applet parameter as "sco/tta/1.x".
Problem Some customized login scripts may need changes to be used with this release. [514279]
Cause Necessary changes for this release.
Solution Known problem areas:
  • The values of the TTA_WindowsApplicationServer variable are now all lower case. For example, "merge" or "wcpwts". Previously these values were mixed case.
  • The TTA_UserName variable may contain spaces, and should be quoted where necessary.

Upgrading from Tarantella Version 3.0x

Problem Password cache and web cache entries are lost for users who log in using the LDAP login authority. [516098]
Cause Changes made for more efficient LDAP authentication.
Solution Users can add their password cache entries again in the normal way. Tarantella Administrators can also add password cache and web cache entries using the tarantella passcache and tarantella webcache commands.

Web servers

Note These are problems and issues that we've identified with web servers that you may notice when using Tarantella. They might be fixed by the web server's vendor in a later release.

Problem Users can't download the Tarantella Native Client. [125591]
Cause By default, some Netscape web servers treat files with ".exe" extensions as CGI programs to run on the server, rather than files to download to the client.
Solution Edit your web server's mime.types file, to remove "exe" as an extension for the "magnus-internal/cgi" type, and add it as an extension for the "application/octet-stream" type.
Problem An EAPI warning message is displayed when starting the Apache webserver. [515326]
Cause We ship the Apache plugin (mod_readcookie.so) compiled without the EAPI switch. The warning message is displayed if your Apache webserver has been built with the EAPI switch.
Solution As far as we know, this is a benign problem. If it proves otherwise, contact Tarantella Support (http://www.tarantella.com/support) for an Apache plugin compiled with the EAPI switch.
Problem Unable to find matching tokens when connecting to the Netscape webserver. [515788]
Cause Webserver plug-ins are built by us against a particular version of the webserver API.
Solution If you encounter problems with a webserver plug-in, contact Tarantella Support for details of plug-ins built to other versions of the APIs.
Problem The Apache event log shows a "Premature end of script headers" error every time a user logs in to Tarantella. [601657]
Cause The error message is a standard Apache message which occurs when the CGI fails to execute a script. When you run Tarantella with the Security Pack and have a test certificate installed, the web browser tries to download a custom certificate. As the certificate doesn't exist, the Tarantella ttacustomca.cgi script fails, producing the error.
Solution If you do not have a custom certificate installed, the error is expected behavior and can be ignored. The error can be prevented by installing a custom certificate.
Problem Users are unable to download Tarantella Java™ archives. [601888]
Cause The web server's configuration is incorrect and so it does not download jar and cab file types.
Solution Edit your web server's mime.types file and add "jar" and "cab" as file extensions for the "application/octet-stream" type, for example: 
application/octet-stream        bin dms lha lzh exe class jar cab
Related topics
  • I can't find the solution to my problem
  • What operating system changes do I need to make?