When attempting to launch the desktop client GUI on Linux , by executing "pvcsvmux", an error similar to the following is shown: Exception in thread "main" java.lang.UnsatisfiedLinkError: /usr/pvcs/vm/common/java/linux/jre/lib/i386/xawt/libmawt.so: libXext.so.6: cannot open shared object file: No such file or directory
Unless you are running the VM GUI in debug mode (pvcsvmux -d), the stdout channel is closed because we are launching the GUI in background mode and want to reduce its chattiness. Unfortunately there are a number of critical error messages that are sent via stdout, all of which effectively fail to get displayed. Example:
The GUI desktop could lock up on Red Hat 6 EL w hile working with a File Server-based Project Database, especially after the GUI window loses and then regains focus.
use the PVCS VM File Server, and are accessed from a network mount point that is shared with Windows users. In this scenario the status bar at the bottom of the Desktop Client GUI shows "Updating ProjectName ...
Until this defect is resolved, the message can often safely be ignored without adverse effects. If areas of the GUI become unresponsive following this error (e.g. the Revisions pane that normally shows Revision, Version Labels and Promotion Groups is blank after selecting a file), the GUI will have to be restarted.
to re-enable setuid mode. While either method allows for a quick test to see if the desktop client GUI then launches correctly, please do not attempt to make changes to the repository if it does Doing so may result in file permission based problems if the repository was created for access in setuid mode.
to re-enable setuid mode. While either method allows for a quick test to see if the desktop client GUI then launches correctly, please do not attempt to make changes to the repository if it does Doing so may result in file permission based problems if the repository was created for access in setuid mode.
