--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/18a63a21-7748-4e14-9201-b66c78b43b78n%40googlegroups.com.
Hi everyone,
Today we download the XNAT desktop client (version 2.0.4) and try to use it to transfer some images. This is an appimage file. We make it executable and run it directly. Our machine runs CentOS 7.4. It can start, but the interface is almost empty. There is no ‘Add new XNAT server’ button in the GUI. See below picture for details. Could anyone please tell us what’s wrong with this?
Thanks.
Zhongdong Sun
Department of Radiology and Biomedical Imaging
Yale University School of Medicine
It’s possible to fix part of this error: the first problem I ran into is that a JDK has to be installed on the VM and then linked to a particular location so that the application can find it.
sudo yum install java-1.8.0-openjdk-devel
sudo mkdir -p /opt/java/linux-x64/jre/lib/amd64
sudo ln -s /lib/jvm/java-1.8.0-openjdk-1.8.0.292.b10-1.el7_9.x86_64/jre/lib/amd64/server /opt/java/linux-x64/jre/lib/amd64/server
However, that just sets it up for another error:
/tmp/.mount_XNAT-DmKgpq2/resources/app.asar/renderer-process/index3.js:41 Uncaught Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_XNAT-DmKgpq2/resources/app.asar.unpacked/node_modules/java/build/Release/nodejavabridge_bindings.node)
Error: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_XNAT-DmKgpq2/resources/app.asar.unpacked/node_modules/java/build/Release/nodejavabridge_bindings.node)
at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:166:20)
It’s worth noting that this same error occurred on CentOS 7.4 and 7.9, which makes sense because the latest version of the ABI library available is 1.3.7 on both of them. I tried testing it on a CentOS 8 VM but the Vagrant box server appears to be down at the moment. It’s possible that CentOS 8 provides a newer version of that library, but I don’t see any easy way to get that working on CentOS 7.4.
--
Rick Herrick
XNAT Architect/Developer
Computational Imaging Laboratory
Washington University School of Medicine
From:
xnat_di...@googlegroups.com <xnat_di...@googlegroups.com> on behalf of Sun, Zhongdong <zhongd...@yale.edu>
Date: Thursday, June 24, 2021 at 10:02 AM
To: xnat_di...@googlegroups.com <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] XNAT desktop client
* External Email - Caution * |
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
xnat_discussi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/CH0PR08MB7372227D53D9EC08152322E381079%40CH0PR08MB7372.namprd08.prod.outlook.com.
The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.
I was able to start up a CentOS 8.4 VM this morning using the gbailey/centos8-mate Vagrant base box. I still needed to link the Java server JRE as described below, but libstdc++ on CentOS 8 supports up to 1.3.11 of the C++ ABI and XNAT desktop client ran with no issue.
Unfortunately the version of the C++ ABI that gets set for the application is a function of the build environment and we can’t really change that because the version on the build container is out of our control. Which means, basically, the desktop client can’t support CentOS 7.x without a migration of the overall build environment.
Hi Rick,
Thank you for your replies.
As you mentioned, the XNAT desktop client doesn’t support CentOS 7, only CentOS 8. Unfortunately, we’re still running CentOS 7. I wonder if you have an older version that supports CentOS 7.
If unavailable, I wonder if any versions of the desktop client can run in Ubuntu 18.04.
Does this desktop client only support JRE 1.8? Ubuntu seems to have a different of JRE.
I download the source code for XNAT desktop client and build it in CentOS 7. The building is ok, but the resulted program still has the same problem.
Also, I tried the desktop client in CentOS 8 virtual machine, and it works well in it. But we cannot run this in a virtual machine. This program will be used routinely for Dicom image exchange with other sites.
Thanks.
Zhongdong
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/SN6PR02MB5118BBF81CA17065F6AABD3DBD069%40SN6PR02MB5118.namprd02.prod.outlook.com.
The current version of the desktop client should work fine with Ubuntu 18.04, with a couple caveats:
sudo apt install openjdk-8-jre
sudo mkdir -p /opt/java/linux-x64/jre/lib/amd64
sudo ln -s /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server /opt/java/linux-x64/jre/lib/amd64/server
Note that this is installing the JRE rather than the JDK. That should be sufficient.
Re: “I download the source code for XNAT desktop client and build it in CentOS 7. The building is ok, but the resulted program still has the same problem.”
I took a look at the dependencies for the desktop client and I can’t be sure but it looks like the ABI version dependency may actually be in Electron itself, which is the framework that supports running node.js applications as stand-alone GUI applications. Which would indicate that no applications that use Electron after some version would run on CentOS 7.x. And we definitely can’t roll back the version of Electron because we already went through the process to migrate to newer versions of node.js and Electron because they were required by other dependencies we were integrating into the application.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/CH0PR08MB7372D2F11AD5C1217C49497281069%40CH0PR08MB7372.namprd08.prod.outlook.com.
Hi Rick,
I followed your instruction and setup JRE in one Ubuntu 18.04 machine. The XNAT desktop client worked well in it.
Thanks a lot for your helps in this issue. Maybe you can add your instruction into XNAT desktop client installation documentation so that more users can read them.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/SN6PR02MB51182C4C63D689D2E6A8F20BBD069%40SN6PR02MB5118.namprd02.prod.outlook.com.
Info added to XNAT desktop client docs Linux section.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/CH0PR08MB7372B932447C83DC91045CC981069%40CH0PR08MB7372.namprd08.prod.outlook.com.
Hi Rick,
It’s great. Thanks for updating the documentation. Now it’s more clear how to install the XNAT desktop client on a Linux system. I’m sure more users will find it helpful in future.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/SN6PR02MB5118791303E25DE694316FECBD039%40SN6PR02MB5118.namprd02.prod.outlook.com.