How do I open visIt ? (ubuntu24 - visIt 3.4.2)

[Luizhzz]

567425 blocos
81823 blocos
visit-install done

eng@eng-desktop:/programas/vis_it/3-4-2$ cd
eng@eng-desktop:$ echo "set path = ($path /usr/local/visit/bin)" >> .cshrc
eng@eng-desktop:~$ visit
Running: gui3.4.2

eng@eng-desktop:~$ visit -cli
Running: cli3.4.2
Running: viewer3.4.2 -noint -host 127.0.0.1 -port 5600

And it doesn't open the program.

---

Is it the problem ?
usr/local/visit/bin$ frontendlauncher
Version 3.4.2 of frontendlauncher does not exist for the architecture linux-x86_64.

[JustinPrivitera]

What are the contents of your /path/to/visit/3.4.2 directory? Is there a linux-x86_64 directory there? What platform did you select when running visit_install? For linux x86_64 you'd do the following:

1. Download visit_install.
2. Download the ubuntu 24 tarball.
3. Run the following commands in the directory where you downloaded the files. These commands are mostly from here.

# make the install script executable
chmod +x visit-install3_4_2
# remove `-ubuntu24` from the tarball name
mv visit3_4_2.linux-x86_64-ubuntu24.tar.gz visit3_4_2.linux-x86_64.tar.gz
#      visit_install     version  platform   install_location
sudo ./visit-install3_4_2 3.4.2 linux-x86_64 /usr/local/visit

Once complete, run /usr/local/visit/bin/visit to run VisIt.

If you followed those instructions or something similar, then I would make sure that /path/to/visit/3.4.2 contains a subdirectory called linux-x86_64. If it does, then please /path/to/visit/bin/visit -debug 5 and see if it produces and log files (*.vlog). Please zip them and attach them here so we can take a look.

[Luizhzz]

I reinstalled, but I had the same problem.

1. and 2. Downloaded from these links.

subdirectory found at : /usr/local/visit/3.4.2/linux-x86_64

ng@eng-desktop:~/programas/vis_it$ /usr/local/visit/bin/visit
Running: gui3.4.2

But it doesn't open.

A process called "apport" open and closes quickly.

steps.zip

[markcmiller86]

@Luizhzz apologies but I pasted the incorrect command for you to run, above. Please try...

sudo strace -ff -s 256 -o visit-trace /usr/local/visit/bin/visit

That should create one or more files named like visit-trace.<PID>. Zip all of those and attach them.

[Luizhzz]

@markcmiller86

visit-trace.zip

[markcmiller86]

@Luizhzz thanks for the newest strace logs. There are telltale signs there indicating a possible mismatch in CPU architecture or the use of instructions in our executable that your CPU does not have enabled. Can you provide information about the hardware architecture of your ubuntu system?

[markcmiller86]

Maybe the command lscpu might shed some light?

[markcmiller86]

We've been examining your strace files and those of another Ubuntu user having same issue. We are seeing SIGILL (illegal instruction) errors in both yours and his strace logs. How old is the CPU on your system? In the other case we are aware of, the CPU is ~10 years old Intel i7. So, we are thinking when we build the Unbuntu binaries with Docker, we're building with a newer instruction set than these older CPUs can handle. We are going to try building on Docker but using some compiler flags that force it to use older CPU instruction sets. ChatGPT has recommended...-march=x86-64 -mtune=generic -mno-avx -mno-avx2 -mno-sse4.2 -mno-sse4.1 -mno-fma -mno-bmi -mno-bmi2