[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AWIPS #KHE-708122]: CAVE Client version and Problems

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [AWIPS #KHE-708122]: CAVE Client version and Problems
  • Date: Wed, 18 Jan 2017 10:06:58 -0700
I was not able to release a stable 16.2.2 client for Windows, so the version 
you downloaded is the most recent, 16.1.4.  The next attempt will be with 
16.4.1.

WINDOWS

* The error message "could not load SWT / no swt-wgl-win32" shows a path of 
C:\Users\benites\.swt\lib\win32 - does this folder exist and if so, created by 
what package?  The Windows client comes with a bundled JRE which should run 
without a separate JRE installed, but that's always worth a shot. Do you have 
Java installed elsewhere? 

* Did you install the latest graphics driver on the Windows virtual machine?  


MAC

10.12 (Sierra) appears to prevent the start of applications not installed via 
the App Store, and I only have a workaround for now, which is to manually run 

/Applications/CAVE/cave.app/Contents/MacOS/cave

from the command line.


LINUX

I have confirmed the 16.2.2 client installs and runs on CentOS 6 and 7.  

Is this an upgrade on an existing CAVE workstation, or a clean installation on 
a VM?

Are you certain there were no error messages during yum groupinstall?

What awips2 packages are installed on this workstation? (rpm -qa |grep 
awips2|sort)

Is /awips2 owned by awips:fxalpha ??



Ticket Details
===================
Ticket ID: KHE-708122
Department: Support AWIPS
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.