-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FSL GUI won't start #204
Comments
Dear @dkp, we can unfortunately not reproduce the problem: Could you describe in more detail how you are starting Neurodesk and how you start fsl? |
Dear @dkp, Could you please provide more details on how you got this error and which Neurodesk link you used exactly? Thank you |
Thank you so much for your responsiveness and patience! I went to play.neurodesk.org=>U.S.West. However, apparently if I select VNC (fixed resolution), then I get this error:
I hope that helps. I had not realized the interaction. |
Dear @dkp, That's extremely helpful - thank you so much for finding this issue. We are looking into it. @aswinnarayanan - any ideas? Thank you |
Dear @dkp, We found the problem and it's fixed now. There will be a new release soon which includes this fix. Thank you for finding and reporting it |
Cool! Thank you! |
Dear @dkp, Thank you again for reporting this problem. The new release is out now and the problem is fixed :) Thank you |
Environment: Started neurodesktop on Binder
From the terminal, I can run command line tools like fslinfo. I can also start fsleyes, but when I type
fsl
, the gui does not start, and instead complains:fsl-6.0.7.4:
$ pwd$ fsl/home/jovyan
fsl-6.0.7.4:
Error in startup script: no such variable
(read trace on "env(USER)")
invoked from within
"set USER $env(USER)"
(file "/opt/fsl-6.0.7.4/tcl/fslstart.tcl" line 6)
invoked from within
"source [ file dirname [ info script ] ]/fslstart.tcl"
(file "/opt/fsl-6.0.7.4/tcl/fsl.tcl" line 71)
invoked from within
"source ${FSLDIR}/tcl/${origname}.tcl"
(file "/opt/fsl-6.0.7.4/bin/fsl" line 20)
Thank you,
Dianne
The text was updated successfully, but these errors were encountered: