Print

Print
Hi,

Sorry, bad advice - LIBGL_ALWAYS_SOFTWARE was never going to work, as you are using nvidia drivers.

As I said eariler I think your only real option is to try virtualgl. One other way I can think of which might work is to manually copy a version of libGL.so from the libgl1-mesa-glx package into the FSLeyes installation directory, so it uses that version rather than the nvidia one. I can't guarantee that this will work though.

Cheers,

Paul

On 23 August 2018 at 16:16, Exp. 2086 <[log in to unmask]> wrote:
Hi Paul,
Thanks for your reply.

I tried to run "LIBGL_ALWAYS_SOFTWARE=1 fsleyes" in VNC, it still show the same error.
I also tried run fsleyes using ssh -X, it showed a similar message:
Gtk-Message: Failed to load module "canberra-gtk-module"
The program 'real_fsleyes' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 383 error_code 2 request_code 154 minor_code 24)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

We installed this Graphic card on server in order to use bedpostx_gpu and probtrackx2_gpu, this main purpose has been achieved.  
I usually use fsleyse on my local Ubuntu 16.04, just occasionally on server.
But there is also a small problem, when I run fsl render under xvfb on my local Ubuntu, it show the same error as in VNC of Ubuntu server.
So it will be good to solve this problem, but if not it doesn't matter much.

Thank you!

2086


On Thu, Aug 23, 2018 at 10:27 PM paul mccarthy <[log in to unmask]> wrote:
Hi,

If you want to use the graphics hardware on your remote machine for visualisation in FSLeyes (or any other OpenGL application), virtualgl is the way to go.

Otherwise, within a VNC session, your only option for running FSLeyes (or any other OpenGL-based application) is to use a software renderer. You can try and force FSLeyes to use a software renderer via the LIBGL_ALWAYS_SOFTWARE environment variable, e.g.:

LIBGL_ALWAYS_SOFTWARE=1 fsleyes

Another option is to use ssh -X, rather than VNC, to connect to the remote machine. In this case the graphics card on your local machine will be used for rendering.

Cheers,

Paul 

On 23 August 2018 at 14:47, SUBSCRIBE FSL Zuo Zuo <[log in to unmask]> wrote:
Hi Pual,

I encountered the same problem. Fsleyes worked well in VNC at Ubuntu server 16.04 until I installed NVIDIA-396 driver & CUDA with this code: "apt-get -y install nvidia-cuda-toolkit lightdm- "(https://askubuntu.com/questions/830983/how-to-winstall-nvidia-drivers-to-use-cuda-without-also-installing-x11/831129). It showed the same error. It worked again when I removed CUDA & NVIDIA drive. But how to make it work with CUDA and NVIDIA drriver installed?

Thank you,
2086




Hi Matthew,

Are you running FSLeyes over a remote connection (e.g. ssh/VNC) or locally?

Cheers,

Paul

On 12 April 2018 at 16:14, Matthew Hoptman <[log in to unmask]> wrote:

    Hi all,
    I am getting an error that is noted in the troubleshooting guide for fsleyes, but it is occurring in Ubuntu 16.04, rather than XQuartz, and I'm not sure how to convert the suggestion you have into Ubuntu syntax. Any suggestion would be helpful.

    Thanks in advance,
    Matt

    The error message is:
    matt@gamera:~/software/FSLeyes$ fsleyes
    10:57:26: Debug: Adding duplicate image handler for 'Windows bitmap file'
    The program 'fsleyes' received an X Window System error.
    This probably reflects a bug in the program.
    The error was 'BadWindow (invalid Window parameter)'.
      (Details: serial 11 error_code 3 request_code 20 minor_code 0)
      (Note to programmers: normally, X errors are reported asynchronously;
       that is, you will receive the error a while after causing it.
       To debug your program, run it with the --sync command line
       option to change this behavior. You can then get a meaningful
       backtrace from your debugger if you break on the gdk_x_error() function.)

########################################################################

To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1


To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1


To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1



To unsubscribe from the FSL list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=FSL&A=1