Server Platforms

• Solaris 8 and 9 for SPARC
• Solaris 10 for SPARC and x86_64
• HP-UX 11.x for PA-RISC
• HP-UX 11.23 and 11.31 for ia64
• AIX 5.x for PPC
• Red Hat Enterprise Linux v3, v4, and v5 for x86 and x86_64
• SUSE Linux Enterprise Server 9.x, 10.x, and 11.x for x86, x86_64, and ia64

Client Platforms

• Native X11 client and Netscape 6.0+/Mozilla 1.0+ plugin for Solaris 8, 9, and 10 for SPARC
• Native X11 client and Netscape 6.0+/Mozilla 1.0+ plugin for Solaris 10 for x86-64
• Native X11 client and Netscape 6.0+/Mozilla 1.0+ plugin for HP-UX 11.x for PA-RISC
• Native X11 client and Netscape 6.0+/Mozilla 1.0+ plugin for HP-UX 11.23 and 11.31 for ia64
• Native X11 client and Netscape 6.0+/Mozilla 1.0+ plugin for Red Hat Enterprise Linux v3, v4, and v5 for x86 and x86_64
• Native X11 client and Netscape 6.0+/Mozilla 1.0+ plugin for SUSE Linux Enterprise 9.x, 10.x, and 11.x for x86, x86_64, and ia64
• Native Windows client and Netscape 6.0+/Mozilla 1.0+ plugin for Windows XP, Windows 2000, Windows Vista, Windows Server 2003, Windows 7, and Windows Server 2008
• Native X11 client and Netscape 6.0+/Mozilla 1.0+ plug-in for AIX 5.x for PPC
• ActiveX Control for Internet Explorer 5.0 or later

3.1 Support for third-party load balancers

Previously, when using a third-party load balancer with a set of GO-Global servers, users with suspended sessions on one server could be connected to a different server leaving them no way to resume their session. Version 2.2.7 added the ability for users to resume their sessions even when they are connected to a different server. A typical setup would have all of the load-balanced GO-Global servers on a fast network which would enable TCP traffic between gold connection leaders and Xgo sessions. The setup would also require the user databases to be shared among the servers, typically via NFS. To support this feature, the following item defaults have changed:

• The master database has been renamed from $(HOSTNAME).db to goglobal.db
• The pid_path in gold.conf now represents a file rather than a directory
• Active leaders in the user database now include a hostname parameter
• The hostname has been removed from the user database filenames
• Published (configured) items now contain a xgo_host parameter
• The service name of a session now includes a hostname

These defaults are appropriate for both a stand-alone server and a load-balanced cluster with shared NFS home directories. As such no additional configuration of GO-Global is required to use this new feature. When a user connects to a GO-Global host, his or her gold connection leader inspects the user database, $(HOME)/.graphon/$(USER).db by default, for any suspended sessions. The user is then prompted to resume these sessions one at a time. Once the user chooses to resume a session, the gold connection leader will contact their suspended Xgo process and resume it. This gold connection leader will continue to pass data such as input and display events between the client and the Xgo process. As of 2.2.7, these gold and resumed Xgo processes can be running on two different hosts.

3.2 Authentication

GO-Global for UNIX now uses PAM for its default authentication mechanism. Consult the Administrator Guide for instructions relating to PAM and its configuration. The use of PAM means that the "authentication" between GraphOn's desktop and host software will involve a "conversation". The details of the "conversation" are controlled by the PAM modules (provided by your OS or perhaps a third party), but follow the form of

• Get the response to "login: " prompt from the user (displaying the user's entry)
• Get the response to the "password: " prompt from the user (hiding the user's entry)

In some cases, the PAM module may then respond with additional queries or display strings. For example:

• Display the text "Your password has expired"
• Get the response to the "new password: " prompt from the user (hiding the user's entry)
• Get the response to the "reenter password: " prompt from the user (hiding the user's entry)

The configuration of PAM and its behavior are platform dependent. There is typically an identifier that controls the behavior of services that use PAM for authentication. For example, the "login" identifier is used to control "console", telnet, or ssh access. GO-Global for UNIX's identifier is "goglobal". Most services use a specific identifier (like "goglobal" or "ssh"). A fallback is used if the specific identifier is not present. GO-Global for UNIX uses the "other" service as its fallback if "goglobal" does not exist.

If you are using non-standard PAM modules for "login" (e.g., you use LDAP or AFS), and use that configuration with "goglobal" also, we would be very interested in hearing details of your OS, PAM configuration, and results.

Note that GO-Global is installed with PAM support by default. If you wish to use password authentication, you must edit the value of auth in $(GOGLOBAL_ROOT)/etc/gold.conf.

3.3 Database

GO-Global for UNIX has discontinued use of PostgreSQL as a storage mechanism for published items, suspended sessions, etc. The new implementation will use XML formatted text files to store this information. This should eliminate many of the problems that have been encountered using PostgreSQL.

There are 2 database files that are referenced. One is the "master" and is available to all users. The other is a "personal" db for each individual user. The $(GOGLOBAL_ROOT)/etc/xmldb.conf will control where these databases are located.

The new implementation will allow the database to be shared among multiple machines. Being a file, the sharing would be done via NFS or some other file system sharing between multiple hosts.

To import your GO-Global for UNIX v2.1 database into GO-Global for UNIX v2.2, you should use the v2.1 uninstaller to create a backup of the database while uninstalling v2.1. Then, once v2.2 is installed, use the "pg2xml" tool to import the database backup into the new XML-formatted database.

You can also manually create a dump of your old database by using pg_dump. Here is an example of how you would do this with a working GO-Global for UNIX v2.1 installation:

$(GOGLOBAL_ROOT)/postgresql/bin/pg_dump -p 4491 -u goglobalux > dump

The pg2xml command takes the following arguments:

pg2xml [database-dump] [goglobal-root] [database-user]

where:

• [database-dump] is the path to the "goglobal-database-dump" file created by you or the uninstaller.
• [goglobal-root] is the installation path of the GO-Global for UNIX v2.2 product.
• [database-user] is the owner of the old database, usually "goglobal". The new database owner is "root".

The pg2xml program will parse the information in the database backup file, and import the published items into the new XML-based database.

3.4 Logging

A number of changes have been made to the location and names of various log files created with this latest version.

The files $GOGLOBAL_ROOT/etc/masterlog.conf, $GOGLOBAL_ROOT/etc/leaderlog.conf, and $GOGLOBAL_ROOT/etc/sessionlog.conf will be used to determine the location and names of the various log files. Also, these files contain directives to increase (or reduce) the messages output to the log files.

3.5 go-configure

Several image formats in addition to XPM are now supported when associating an icon with a published item. Supported formats include PNG, JPG, and possibly others depending on your platform.

Users now only see items that they are allowed to run.When a user attempts to edit an item that they do not own, a copy of the item is automatically created, and the user is allowed to edit that instead. Users cannot edit a copy of any arbitrary item. The database owner cannot grant ownership of an item to another user.

3.6 gold

GO-Global for UNIX has a master daemon ("gold") to manage connections to the host. The implementation of this daemon has been completely rewritten to improve performance and stability. Many of the command-line options that can be passed to the process have been changed so consult the Administrator Guide for the options that are used in the new implementation.

3.7 Xgo

The Xgo process (the X server) has been migrated to use the XFree86 base code (instead of the older X.org base). We only use the portions of the code that are under the MIT license, but the XFree86 base has more recent updates and is more actively developed. This allows us to take advantage of fixes for core bugs and new features. The GO-Global specific implementation has had some changes that should improve efficiency, but most of the options and capabilities of the Xserver itself have remained unchanged.

Mouse wheel support has been updated to report Button 4/5, or can be configured to use the previous translation to up/down arrow key presses.

3.8 File Transfer

The implementation of gofile has been completely rewritten to significantly improve throughput. Furthermore, the host user interface has been eliminated so that the utility is better suited to work with scripts that may want to automate multiple file transfers, perform file translations, etc.

The primary change to note is that gofile has been split into two separate utilities; goput and goget. These utilities read/write (when sending/receiving) the file data from/to stdin/stdout. goget is used for transferring files from the client to the host, while goput is used for transferring files from the host to the client. Here are some usage examples for the new utilities:

1. Transfer the file readme.txt from the current directory on the GO-Global Server to the client.
   1. Open an X terminal window.
   2. cd to the directory containing the file to be transferred.
   3. Enter the command to copy the file:
      

             goput readme.txt

   4. The Save As dialog box appears with readme.txt in the File name field. Browse to the directory where you want to write the file. Provide a new name for the file if desired.
   5. Click Save to transfer the file.


2. Transfer the file readme.txt from the directory C:\Program Files\Star Office to the GO-Global Server.
   1. Open an X terminal window.
   2. Enter the command to copy the file:
      

             goget c:\\program\ files\\star\ office\\readme.txt > readme.txt

   3. The file is transferred.
   or
   1. Open an X terminal window.
   2. Enter the command to copy the file:
      

             goget > readme.txt

   3. The Open dialog box appears. Browse to and select the file to be copied. Click Open.
   4. Click Save to transfer the file.

3.9 goprint (formerly golpr)

The implementation of the GO-Global printing utility has been rewritten to improve performance. The name has changed from golpr to goprint with the intention of a more robust golpr script (that uses the goprint utility) to come at a later date. For most uses, goprint can be used in place of where golpr may have been used previously. For example:

# goprint <foo.ps

3.10 goclip

The goclip utility has been changed significantly in order to improve performance and robustness. The primary change is that goclip will be stopped when a session is suspended and then restarted after the session is resumed. The communication between the goclip utility and the Xgo Xserver has also been improved.

3.11 X11 client

In order to support PAM, the Logon dialog of the X11 client has been modified. Other changes to the user interface have been made to accommodate many of the special preferences that previously were only available in the Windows client. Changes have been made to support the new goput/goget/goprint/goclip implementations. Performance improvements regarding protocol transfer have also been made.

One new aspect of the X11 client is the inclusion of .kx files to enhance the keyboard handling. This will allow for better international keyboard support (as kx files are developed) and also reduce some of the problems with "special" keys on some keyboards (e.g., the "Sun" keys).

If an issue occurs while end-users are using the software, they can use the "Help->Report a Problem ..." wizard to help collect logs.

Launching of items via the command line is now done by name rather than ID. For example:

$(GOGLOBAL_CLIENT_ROOT)/goglobalux launch="Xterm"

3.12 Windows client

In order to support PAM, the Logon dialog of the Windows client has been modified. Changes have been made to support the new goput/goget/goprint/goclip implementations. Performance improvements regarding protocol transfer have also been made.

If an issue occurs while end-users are using the software, they can use the "Help->Report a Problem ..." wizard to help collect logs.

Launching of items via the command line is now done by name rather than ID. For example:

"C:\Program Files\GO-Global for UNIX v2.2\goglobal_ux.exe" launch="Xterm"

3.13 Java client

Java is no longer a supported client platform. Presently there are no plans to provide a Java client compatible with GO-Global for UNIX v2.2 or later.

3.14 Mozilla plugins

Our Windows Netscape 4.x based plugin has been replaced with a Gecko-based plugin, and now requires Netscape 6 or above, or any Mozilla-based browser.

3.15 Licensing

The FlexLM v9.2 licensing has been replaced with FlexNet Publisher v10.8.0.1.

3.16 Keyboards

Keyboard support has been consolidated and expanded. All platforms support the following list of keyboard languages:

• be_BE - Belgian
• da_DK - Danish
• de_CH - German Swiss
• de_DE - German
• en_IE - English Eire
• en_UK - English UK
• en_US - English US
• es_ES - Spanish
• et_EE - Estonian
• fr_BE - French Belgian
• fr_CH - French Swiss
• fr_FR - French
• it_IT - Italian
• ja_JP - Japanese
• nl_NL - Dutch
• no_NO - Norwegian
• pt_BR - Portuguese Brazil
• sv_SE - Swedish

3.17 Signal handling and init script changes

The master gold process now handles these signals in the follow way:

SIGTERM (15) - terminates all golds, as well as all running and suspended sessions.
SIGINT (2) - terminates all golds, running sessions become suspended.
SIGQUIT (3) - terminates master gold ONLY. This signal is NOT sent to other (leader/connection) golds. Useful for reloading gold.conf without affecting existing connections or sessions.

goglobalux stop sends SIGTERM to the master gold
goglobalux restart sends SIGQUIT, then restarts the master
No variant of the goglobalux init script sends SIGINT

3.18 Software-based GLX

The GO-Global for UNIX X server (Xgo) now has support for the GLX X extension. This adds the ability to display 3-D graphics from within a GO-Global session.

3.19 DISPLAY allocation

DISPLAYs can now be allocated to sessions by using the lowest available DISPLAY value, or the next DISPLAY value that hasn't been previously allocated in a round-robin fashion. The minimum and maximum display values can also be configured. See the comments regarding min_display, max_display, use_first_display, and display_store_path in $(GOGLOBAL_ROOT)/etc/gold.conf for more information.

3.20 Silent Installer

The silent installer requires setting up the GRAPHON_INSTALLER_OPTIONS environment variable as demonstrated below. There are no default options. License retrieval is not supported. All options should be verified manually. When using the silent installer, consider the following:

• Automatic license retrieval is not available when in batch mode.
• Run-time error checking (ports not in use, install run as root, etc) are disabled in batch mode.
• Upgrades over an existing version are not supported.

The following options are supported (batch, target, user, port and sslport are required):

• batch (boolean) - determines if batch mode is active or not
• port (string) - sets TCP port for server to listen on
• sslport (string) - sets SSL port for server to listen on
• target (string) - location to install GO-Global
• user (string) - user for the license manager to run under


• dbport (string) - obsolete, formerly psql port
• dbhost (string) - obsolete, formerly psql host
• uninstall (string) - obsolete, formerly used to uninstall product

Example:

GRAPHON_INSTALLER_OPTIONS="batch=y,target=/usr/local/ggxsilent,port=10491,sslport=10791,user=flexlm" ./GO-Global_for_UNIX-RedHat_Linux_EL-5.0-x86_64.bin

4.1 Resolved in 2.2.14 -> 2.2.15

• Input focus and window resize issues on Windows 7 clients.
• Sessions suspended instead of stopped when done quickly.
• Support for Japanese keys Hankaku_Zenkaku, Hiragana_Katakana, Muhenkan and Hiragana_katakana.
• Session crashes when two sessions receive same session number or DISPLAY.
• Buildup of a number of leader gold processes when suspending and resuming quickly.
• Session display not being closed on the client when a number of sessions are closed rapidly.
• Timezone support for British Summer Time.
• Fix for Danish keybord 'n' character - da_DK.kt.
• Improved license manager disconnect handling.
• Xgo crashes Ocean Batch Tool without the nograf option.
• Xgo crashes when goclip is killed or crashes.
• GO-Global for UNIX no longer supports using 2.1 licenses.
• Support for X client Ubuntu 10 kx keyboard file.
• Support for X client Spanish kx keyboard file.
• Maintenance proceess cleans up suspended sessions when no_explicit_suspend=true and the leader process has exited.
• Support for SUSE 11.2 and fix for lost sockets - requires package lsb and libstdc++.so.5.
• Mozilla plug-in parameters passed incorrectly.
• Support for silent install.

4.2 Resolved in 2.2.13 -> 2.2.14

• Increase connection time between gold and xgo.
• Update the Administrator Guide to include two-way redundancy.
• Pop-up menus displaying incorrectly; obscuring the top-level pop-up menu selection.
• Update license agreements.
• In certain cases, when suspending a session, Xgo may crash..
• When attempting to connect to a host that is offline, the client crashes.
• Suspend/resume on Linux is creating zombie processes.
• Start immediately followed by a suspend hangs sessions.
• Screen artifacts and painting issues after moving the mouse.
• Syntax error in line 20 of startXgo.sh.
• When resuming a large number of sessions simultaneously, the client could become unresponsive. The client's process must be ended with the Task Manager.
• Xgo crashes when running a Linux x86-64 OpenGL application in a Solaris session.
• Bitmap error message when the client is older than the server.
• On the Solaris Client (Sun 5c Client keyboard), the Numpad keys don't work.

4.3 Resolved in 2.2.12 -> 2.2.13

• Keys in the number pad no longer send both the number and the positional variation of the key when running Java applications.
• Added IndiaStandardTime timezone.
• Keys in the number pad now work in CDE's calculator applet.
• Launching configured items will now correctly be launched into an existing session if there is a compatible one running.
• gold no longer crashes when gowm exits.
• The clipboard no longer stops working when running multiple copies of the same application.
• Added example licensing failover settings to init scripts.
• The client no longer crashes when suspending several sessions at once.
• Xgo no longer crashes due to HP-UX thread stack size requirements for HP patch PHCO_38658.
• Improved handling of improper user-set DISPLAY variable.
• Added a browser-embedded mode to the ActiveX control.

4.4 Resolved in 2.2.11 -> 2.2.12

• Copying and pasting between certain Windows applications and GO-Global sessions no longer stops working.
• Applications can now be launched via command-line arguments regardless of the other arguments used.
• XKB support has been added. This allows applications and desktop environments, such as Gnome, to work properly with client-side keyboard events.
• Using multi-depth without 8-bit visuals and server back buffer will no longer cause Xgo to crash.
• The Swiss German keytable for Solaris now has the 'y' and 'z' keys positioned correctly.
• The Report A Problem Wizard now sorts log files by date.
• Transferring a file via goput without a destination file no longer hangs the GO-Global session.

4.5 Resolved in 2.2.10 -> 2.2.11

• The Windows client will fallback to system RAM for images once video RAM is exhausted. Previously, images would appear as solid white rectangles in this case.
• Canceling a print job initiated via goprint no longer causes Xgo to consume excessive CPU resources indefinitely.
• Sessions now suspend much faster when a client has been disconnected from the network.
• Xgo is now tolerant of data cache size values above 32768 KB, or 32 MB.
• Clients in the CET timezone are no longer improperly mapped to the WET timezone.
• Leader golds are now more tolerant of delays caused by automoutned HOME directories when making a connection to Xgo.
• US-International keyboards are now supported.
• Many problems seen when compression is enabled have been resolved.

4.6 Resolved in 2.2.9 -> 2.2.10

• Performing a large clipboard operation while suspending a session no longer crashes Xgo.
• When receiving more than one mouse motion event in the same millisecond, Xgo no longer avoids the time collision which resulted in some window managers losing focus.
• Documentation has been added to the Administrator Guide detailing how to run in an NFS environment.
• The Mozilla plugin is now compatible with Firefox 3.

4.7 Resolved in 2.2.8 -> 2.2.9

• Improvements have been made to the clipboard functionality regarding interaction with 3rd party clipboard managers such as klipper.
• The Solaris registration screen once again paints correctly.
• The performance of several graphical operations has been improved.
• The CPU usage of Xgo has been reduced.
• The client backbuffer option is no longer forced to be enabled.
• Foreign language keyboards are now supported on the Solaris client. Contact support@graphon.
• Input focus no longer gets locked to a non-existent window.
• Maintenance processes in a load-balanced configuration no longer mistakenly remove items from a users list of suspended sessions.
• goclip no longer crashes when communicating between ill-behaved X applications and the Go-Global X11 client.
• Xgo no longer crashes when using Xdm with the indirect option.
• The goglobalux init script was mistakenly trying to remove a lock file from the wrong directory.
• The Y and Z keys were swapped for Swiss-French keyboards.

4.8 Resolved in 2.2.7 -> 2.2.8

• Colors now appear correctly when using 16-bit clients.
• Hosts no longer treat the inability to check out a license on startup as fatal.
• Activation and focus no longer get lost when a window is being destroyed.
• When using stored usernames and passwords, the authentication dialog is no longer displayed to users when using the ui=hide option.
• xinit no longer provides a new, clean environment.
• When treating the mouse wheel like arrow keys, the right mouse button is now available to all applications.
• Locking the client workstation using Ctrl-Alt-Delete no longer causes one of the modifier keys to behave as if it is still being pressed.

4.9 Resolved in 2.2.6.989 -> 2.2.7

• The X11 client no longer hangs when its clipboard state gets out of sync with the server's.
• Running two clients in succession that both launch applications no longer causes the second client's application to launch in the context of the first connection.
• Simulataneous mouse events are now reported to applications as if they occured separately.
• CAPS lock no longer gets out of sync when using the Windows client.
• We now treat hostnames beginning with a digit as valid.
• Several issues with licensing on Linux IA64 and HP-UX IA64 have been addressed.
• Sessions no longer hang when transferring files via goget and goput simultaneously.
• User databases no longer include $(HOSTNAME) by default, facilitating load- balanced configurations using NFS mounted HOME directories.

4.10 Resolved in 2.2.6.971 -> 2.2.6.989

• gold session leader no longer crashes at login if timezone cannot be mapped.
• The connection between gold and Xgo is no longer marked as closed by Solaris hosts, causing the session to suspend.
• The connection between a client and gold is no longer marked as closed by Solaris hosts, causing the session to suspend.
• CAPS lock no longer gets out of sync when using an X11 client.

4.11 Resolved in 2.2.5 -> 2.2.6

• User databases now include $(HOSTNAME) by default in order to avoid conflicts on NFS mounted HOME directories.
• Transient windows, such as menus, would leave black rectangles in their place when using a multi-monitor client. In some cases, this could be corrected by disabling backing store.
• The X11 gecko plugin now runs on Linux x86.
• SSL connections and operations in GO-Configure would crash on Linux ia64.
• Suspending a session no longer causes it to hang in certain situations.
• Xgo now supports XInputExtension, enabling Konqueror to run on SUSE 9.
• Certain applications now recognize double-clicks coming from the X11 clients.
• Init scripts are now installed correctly on SUSE Linux.
• The client no longer hangs when cancelling the Authentication dialog.

4.12 Resolved in 2.2.4 -> 2.2.5

• Log file permissions can now be set via LOGPERMS in *log.conf.
• The system menu is now available for minimizing, maximizing and closing borderless sessions.
• Suspended sessions can now be stopped in addition to resumed.
• Support for the Extended-Visual-Information, TOG-CUP, and XTEST extensions has been added.
• A case of suspended sessions terminating on their own has been fixed.
• Log configuration files in $(HOME)/.graphon override system-wide configuration files.
• Fixed a problem where small images or portions of text would get used in place of a differen.
• Authentication no longer deadlocks with GO-Global licensing when using PAM modules found in FC5 and SLES 9.3.
• xinit no longer leaves 'defunct' processes for each session terminated with an active connection.
• The master log file now correctly rotates and only expected messages (leader exits) are logged to already-rotated files.
• A case of unresumable suspended sessions has been fixed.
• Startup failures are now noted when running the init script.
• After failing to authenticate because of an invalid username, the user is now prompted for a new username.
• Double-clicks and Triple-clicks are no longer "lost".
• Single window sessions in the Vista theme are now properly sized.
• Errors in a users .profile no longer prevent the starting of sessions.
• The clipboard chain is now properly restored on session exit.
• Errors when running the "Report a problem" wizard no longer crashes the client.
• Switching an item to XDM no longer loses the previous commandline.
• Checks are made in GO-Configure to prevent publishing invalid items.
• Double-clicks and Triple-clicks are no longer "lost".
• Single window sessions in the Vista theme are now properly sized.
• Errors in a user's .profile no longer prevent the starting of sessions.
• The clipboard chain is now properly restored on session exit.
• Errors when running the "Report a problem" wizard no longer crashes the client.
• Switching an item to XDM no longer loses the previous command-line.
• Checks are made in GO-Configure to prevent publishing invalid items.

4.13 Resolved in 2.2.3 -> 2.2.4

• The Windows client no longer writes empty cache files.
• Xgo no longer crashes on Solaris 8 running firefox.
• 'who' command now shows users connected to the GO-Global host.
• gold updates utmp/wtmp/lastlog files.
• Checking for connectivity timeouts has been improved.
• Linux startup script no longer removes /var/subsys/ files, which was preventing proper shutdown of product.
• The Windows client installer now creates start menu icons for all users if possible.
• Client no longer deadlocks while receiving a specific sequence of display data.
• The Authentication dialog's display large prompts has been improved.
• Hosts configured to automount directories under /home will no longer attempt to mount /home/toor.
• Canceling the Authentication dialog no longer leaves orphaned gold processes.
• The 'Report a Problem' wizard no longer generates invalid .zip files.
• Sessions now start properly on Fedora Core hosts.
• Xgo CPU Usage has been reduced.
• Empty user databases no longer prevent users from successfully logging on.
• User databases no longer end up empty.
• OpenWindows is no longer mistakenly published on Solaris 10.
• Suspended sessions are now stoppable with all platforms and shell combinations.
• Repainting of windows with client back buffer disabled no longer repaints the entire session.
• Resuming while suspending no longer results in an unresumable session.
• Protocol corruption no longer occurs when compression is enabled.
• Re-authenticating to a given host immediately after closing a connection to that host no longer hangs the client.
• Issuing a 'stop' command to the goglobalux init script no longer puts running Xgos into a CPU-consuming state.
• The font paths for OpenSUSE 10.2 were added to the starting of sessions.
• All mouse wheel options now work, display, and save correctly.
• The pid_path option in gold.conf is now properly used.
• The /tmp/.gg-unix directory is now created with the correct permissions.
• Locale values are now properly parsed and should be set correctly on the server.
• Connection Unresponsive dialog removed. Messages about the responsiveness of the connection will now appear on the status bar of the main window.
• Several PAM bugs have been resolved, particularly for HP-UX hosts.
• Several clipboard bugs have been resolved.
• gold will now wait longer for Xgo to become ready when starting a session. This fixes a bug in which on some systems sessions could fail to launch because Xgo took too long to start.
• User and global database ownership is now retained and used to determine edit permissions.
• Several bugs in how sessions respond to connectivity problems have been addressed.
• A new protocol optimization was added to better utilize available bandwidth without saturating it.
• Xgo now respects the session logging levels, and logging in general has been improved.
• Images are now properly cached on the client, resulting in greatly reduced bandwidth as compared to earlier 2.2 releases.
• Bitmap drawing and text rendering bugs that would cause Xgo to crash have been fixed.
• A couple of deadlock scenarios related to the 'database' XML files have been addressed.
• The client now paints more efficiently on non-primary monitors.
• goput and goget now properly handle stdin and stdout.
• Some operations, such as dragging an icon in CDE, no longer cause unpredictable behavior, including aborting the session.

4.14 Resolved in 2.2.2 -> 2.2.3

• User-targeted and group-targeted application publishing is now possible.
• The invalid user ("Group:") can no longer be granted an allow or deny permission.
• Suspending a session no longer causes Xgo to crash in certain circumstances.
• The AIX port is no longer dependent on libstdc++.
• A permissions issue that hindered session launches on AIX has been fixed.
• Permissions are now intuitive and unambiguous.
• Scrolling no longer consumes extreme amounts of CPU resources.
• Time stamps are now correct when auto-generating report.zip.
• Resuming a desktop environment session now paints correctly and no longer crashes the client.
• Improved performance of the host.
• We now list users in all of the supplementary groups when editing permissions.
• Improved performance and feel of scrolling.
• Made changes to allow host (with configuration changes) to be run on a read-only share.
• Xgo no longer crashes if localhost is not resolvable.
• The way the Windows client stores the default connection type has been modified not to conflict with older (v2.0 and v2.1) clients.
• Fixed a bug where a session would silently exit while relaying a portion of the screen from the client to the server.
• Display no longer becomes corrupted when scrolling in a Sun JVM.

4.15 Resolved in 2.2.1 -> 2.2.2

• Licenses are no longer mistakenly and automatically checked in after 2 hours.
• The client window no longer appears behind the browser when the plugin is loaded.
• The host can now log to syslog.
• The host initialization script now properly reports any errors that may occur.
• Suspending or resuming a session with a running goget no longer ends the connection.
• Keytables have been updated.
• An idle timeout feature was added.
• SSL connections no longer leak temporary files.
• Closing SSL connections no longer results in an error.
• The Windows client thread creation has been stabilized.
• The host initialization script no longer uses the deprecated initlog mechanism.
• The DISPLAY environment variable is now always in the form of host:#.
• XDM sessions now properly launch.
• FlexNet licensing properly handles heartbeat and re-connecting.
• The gold process now properly handles the case of suspend_age=0.
• PAM_TTY is now set to be gold: so that each user will have a unique TTY value.
• The backing store no longer has an improper offset.
• The SSL Security Alert dialog now works properly in the X11 clients.
• Client preferences now take effect when launching new sessions.

4.16 Resolved in 2.2.0 -> 2.2.1

• Multiple users logging in with identical credentials will now work properly.
• Client menus now accurately reflect the state of various UI options.
• Log file names no longer contain a colon by default.
• Connection error dialogs are now clear as to what the error was.
• Installing on a Windows client that has or had a previous installation will now get a new directory with the "2.2" version.
• The X11 clients 'recent connection' menu properly updates while it is running.
• The maintenance interval will not respawn if one is currently in progress.
• Saved passwords are properly respected now.
• "suspend_age=0" now properly works for disabling session suspension.
• NumLock is no longer disabled when the Windows client starts.
• The "no_explicit_suspend" option is now supported.
• goput no longer truncates large files.
• Fixed a problem where the Xgo process could consume 100% CPU when being stopped.
• The maintenance interval no longer processes all users' home directories looking for suspended sessions.
• Keytables are loaded from $HOME/.graphon/keytables if they exist.
• Keymapping is reloaded if a session is resumed with a different keyboard.
• Solaris hosts now handle where PAM modules may pass bogus data.
• Fixed a window stacking bug where transient dialogs would not get focused properly.
• Fix to gowm to keep windows from "shifting down" when a session resumes or the screen depth is changed.
• Improved error handling of the pg2xml utility.

• The Windows client help file has not yet been updated to describe the latest features of the product.
• The X11 clients have no help file or manual page.
• There is currently no easy way to transfer several files at once or entire directories using goput and goget.
• User databases are not backed up during unistallation.
• The X11 clients do not allow resizing of the Authentication dialog.
• The X11 client does not display a print dialog when printing.
• goput does not properly handle Ctrl-D when reading from a TTY on HP.
• The X11 gecko plugins do not run on all platforms.
• Foreign language keyboards are supported to varying degrees on the X11 clients.
• The X11 client will not run on 8-bit clients.
• go-configure may end up temporarily behind the client window.
• The X11 clients do not display a warning dialog when the connection becomes unresponsive.
• X11 clients do not offer an HTTPS Proxy Transport.
• The host installer does not list other versions or locations of previously installed copies of GO-Global for UNIX.
• Launching the client with an improper transport command-line option yields a misleading error dialog.
• Launching the Windows client with an invalid transport command-line option while there is already an instance of the client running will crash the client.
• Connecting the client to an improper port yields a misleading error dialog.
• The X11 client may hang or crash unexpectedly.
• The host installer does not support automated installs.
• Gecko plugin fails to "autolaunch" sessions when loaded.
• Timestamps in the logs are inconsistent when timezones differ on the client and host.
• The 'Connection | Close' menu item may sometimes be disabled incorrectly.
• ALT-ESC handling appears to be incorrect.
• Installer does not use the specified Start Menu Shortcut Folder when installing shortcuts.
• Resuming while suspending may result in an unresumable session.
• Protocol corruption may occur when compression is enabled.
• SSL transport does not work for AIX hosts.
• System keys (such as ALT-TAB) are not redirected to sessions.
• X11 clients fail to create logfiles if the USER environment variable isn't set.
• The X11 clients may suspend (rather than stop) some sessions when stopping multiple sessions while closing the client.
• Installing over existing client installation adds 'Add or Remove Programs' entries.
• CAPS lock can get out of sync when using a Windows client.
• Client may hang when transferring large log files while reporting a problem.
• There is no option available to limit the number of sessions.
• Database lockfiles can cause a busy-spin loop if removed while being read on other servers.
• Sessions cannot start on SUSE with localhost set to 127.0.0.2 in the hosts file.
• Client appears to hang when transfering large log files while reporting a problem.
• Some keys do not work on SUSE x86_64.
• The 'finger' command fails when fingering a user logged on through GO-Global.
• Xgo leaks file descriptors to exec'd processes such as goclip.
• Sessions have a maximum display size of 4096x4096.
• The 'Snap Window to Edges' feature of nVidia's Desktop Manager is incompatible with GO-Global.
• GO-Global is incompatible with certain desktop utilities that implement a 'focus follows mouse' policy.
• Icons within applications may paint incorrectly.
• Connections do not successfully complete when authenticating using LDAP via PAM with SSL/TLS enabled.
• The client or Xgo may crash when suspending a lot of sessions running over the same connection.
• The RENDER X extension is not function in Xgo.
• xwd does not always correctly capture a graphical image of the session.
• When the GO-Global License Manager Daemon (lmgrd) is unreachable, GO-Global Login Daemon (gold) exits and users' sessions close.
• When using GO-Configure on a Windows 7 machine with dual monitors, the mouse and keyboard do not allow input on the edit item window.