FSL GUI won't start

[dkp]

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 /home/jovyan fsl-6.0.7.4:~$ fsl 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

[stebo85]

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?

[stebo85]

Dear @dkp,

Could you please provide more details on how you got this error and which Neurodesk link you used exactly?

Thank you Steffen

[dkp]

Thank you so much for your responsiveness and patience!

I went to play.neurodesk.org=>U.S.West. If I select Neurodesktop=>RDP (dynamic resolution), then everything works fine.

However, apparently if I select VNC (fixed resolution), then I get this error:

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)

I hope that helps. I had not realized the interaction.

[stebo85]

Dear @dkp,

That's extremely helpful - thank you so much for finding this issue. We are looking into it.

@aswinnarayanan - any ideas?

Thank you Steffen

[stebo85]

RDP:

VNC:

[stebo85]

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 Steffen

[dkp]

Cool! Thank you!

[stebo85]

Dear @dkp,

Thank you again for reporting this problem. The new release is out now and the problem is fixed :)

Thank you Steffen