[daip] [!16769]: AIPS - AIPS causing issues in new Ubuntu 20.04 OS Upgrade

[Gregory Walsh]

Gregory Walsh updated #16769
----------------------------

AIPS causing issues in new Ubuntu 20.04 OS Upgrade
--------------------------------------------------

           Ticket ID: 16769
                 URL: https://help.nrao.edu/staff/index.php?/Tickets/Ticket/View/16769
                Name: Gregory Walsh
       Email address: gwalsh4758 at gmail.com
             Creator: User
          Department: AIPS Data Reduction
       Staff (Owner): -- Unassigned --
                Type: Issue
              Status: Open
            Priority: Default
                 SLA: NRAO E2E
      Template group: Default
             Created: 13 August 2020 08:11 PM
             Updated: 13 August 2020 08:11 PM
           Reply due: 17 August 2020 08:11 PM (4d 0h 0m)
      Resolution due: 10 May 2023 12:00 AM (999d 3h 49m)

Hello,
I just wanted to bring up an issue I had to fix after upgrading my Ubuntu OS to the new 20.04 version. I use AIPS version 31DEC19, so this might not be an issue in the 31DEC20 version, but nonetheless. 
If one sources the $AIPS_ROOT/LOGIN.SH script using bash, the unique $AIPS_PATH which is appended to one's PATH is placed before the PATH set globally (e.g., by /etc/environment, or some such), and individually per user (e.g., from ~/.bashrc, ~/.profile, etc.).  That is, one's PATH becomes: /my/aips/path:/my/user/path. After installing the new Ubuntu OS upgrade and sourcing the AIPS LOGIN script, I could not open .pdf files through evince (the default document viewer for Ubuntu) or System Settings (through gnome-control-center). This was because it was looking for the libgcc_s.so.1 library through my AIPS installation, which for me is in /my_aips_root/31DEC19/LNX64/LIB/INTELCMP/ and I'm assuming is too old of a version to handle these processes. To fix this, I had to add my $AIPS_PATH to my PATH directly, without sourcing the LOGIN.SH script, placing it after the PATH set globally by /etc/environment (export "PATH=$PATH:aips/stuff/). AIPS itself still works fine after doing this, and I am able to run the commands in terminal which before would throw errors or not load at all. 
I suppose one could jury-rig this by replacing the AIPS installation of libgcc_s.so.1 with the local installation of libgcc_s.so.1, but this just seems like a bad idea to me (though I am by no means a software expert). 
Again, this may not be an issue if I had the most up-to-date version of AIPS, but I thought it would be useful to bring this up.
Thanks,
Greg


------------------------------------------------------
Staff CP:  https://help.nrao.edu/staff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listmgr.nrao.edu/pipermail/daip/attachments/20200813/6f51957d/attachment.html>