Ocean Color Forum - Not logged in
By daurin
Date 2011-09-14 19:23
Hi,
Trying to install seadas on the following:
Dell Precision 390 (4GB RAM, 4 GHz Intel dual-core, 1 TB)
Red Hat Enterprise 6.1 (Santiago, 2.6.32...) 64 bit
Gnome 2.28.2
Seadas6.2
IDL71
When I run ./config/seadas_setup, after accepting the usage agreement, it throws up the "SeaDAS Environment Setup" window, but the GUI has no functionality. For example, none of the buttons do anything (most notably "Okay"), and eventually it doesn't even refresh after a screen has moved across it. After a while, I can't kill the process in the terminal without closing the terminal. If I catch it early enough, I can still "X" out of the GUI and cntrl-c out of the process with the following feedback:
"% Compiled module: SDS_ENV.
% Compiled module: XMANAGER.
^C% Interrupted at: XMANAGER_EVLOOP_STANDARD 479 /usr/local/itt/idl71/lib/xmanager.pro"
Dirk
By @sean
Date 2011-09-16 14:44
Dirk,
We don't have RH6.1, so I can't see if I can replicate the error.
Sorry, but I don't think we can help with this one.
Have you tried the
runtime version?
Sean
By WhiteG
Date 2011-09-19 12:51
When a GUI goes "non responsive", there is often an error popup hidden behind some other window. There may useful hints in one of the system log files.
I'm using the SeaDAS runtime IDL in CentOS 6, 64-bit, running in a VMware VM hosted on Windows. I don't have any experience with IDL 7.1 on this platform, but you do need some compatibility libraries to run software build for RHEL 4 on a current RH platform, and you may need to experiment with the graphics drivers to find a combination that works with the RHEL 6.1 and IDL 7.1. It could be helpful to try the runtime IDL. Does IDL 7.1 work properly? If you can get some more detailed error messages (check /var/log/Xorg.0.log, dmesg, etc.) that might help locate the specific information you need on the ITTVIS support site or RH BugZilla.
By daurin
Date 2011-09-19 15:23
Thanks. I haven't found any clues in the logs yet, but I'm working on an IDL license issue that will hopefully resolve the issue. IDL runs, but currently only in demo mode, which may be causing the problem.
