Coreform 2020 Fedora Core 33

#1

Hi

The new Coreform Cb segfaults immediately after launch on FC33

[2021-02-07 11:24:47.287] [info] RLM session initialized
Supervisor::Impl::load_plugins: Loaded component: libcubitcomp.ccl
Supervisor::Impl::load_plugins: Loaded component: libcubitcompgui.ccg
Fontconfig warning: "/usr/share/fontconfig/conf.avail/05-reset-dirs-sample.conf", line 6: unknown element "reset-dirs"
Segmentation fault (core dumped)

I do get the Coreform Cubit splash screen if it helps.

Running through gdb on the core dump gives me this

#1  0x0000000034880228 in ?? () from /opt/Coreform-Cubit-2020.2/bin/libcubiti19.so
#2  0x0000000000000002 in ?? ()
#3  0x000000005322ef28 in ?? ()
#4  0x0000000052e80fd8 in ?? ()
#5  0x0000000052e9b068 in ?? ()
#6  0x0000000052e80f00 in ?? ()
#7  0x0000000006da95d8 in std::string::_Rep::_S_empty_rep_storage ()
   from /lib64/libstdc++.so.6
#8  0x0000000007258900 in vtable for CubitOperationEvent ()
   from /opt/Coreform-Cubit-2020.2/bin/libcubit_util.so
#9  0x000000000000001a in ?? ()
#10 0x00000000531b7e50 in ?? ()
#11 0x0000000033cbcbb0 in ?? ()
#12 0x000000005148a190 in ?? ()
#13 0x0000001ffeffe190 in ?? ()
#14 0x00000000511f8f50 in ?? ()
#15 0x00000000511cc160 in ?? ()
#16 0x00000000067b6f90 in ?? () from /opt/Coreform-Cubit-2020.2/bin/libvtkCommonCore-8.2.so.1
#17 <signal handler called>
#18 0x0000000000000000 in ?? ()
#19 0x000000003d45bfb6 in ?? ()
--Type <RET> for more, q to quit, c to continue without paging--
   from /opt/Coreform-Cubit-2020.2/bin/libvtkRenderingOpenGL2-8.2.so.1
#20 0x00000000511cc160 in ?? ()
#21 0x000000003d449e0c in ?? ()
   from /opt/Coreform-Cubit-2020.2/bin/libvtkRenderingOpenGL2-8.2.so.1
#22 0x00000000511cc160 in ?? ()
#23 0x000000005148a190 in ?? ()
#24 0x00000000511cc160 in ?? ()
#25 0x000000003d44794c in ?? ()
   from /opt/Coreform-Cubit-2020.2/bin/libvtkRenderingOpenGL2-8.2.so.1
#26 0x00000000511cc160 in ?? ()
#27 0x000000003d446da5 in ?? ()
   from /opt/Coreform-Cubit-2020.2/bin/libvtkRenderingOpenGL2-8.2.so.1
#28 0x0000000000000000 in ?? ()

Valgrind gives me more, but Im not sure how much help it will be, let me know if I can include it for you. Running with nographics seems to suggest that it maybe graphics related, there are driver arguments but I’ve no idea of what options are allowed

Thanks

Andy

#2

Can you verify the following packages are installed on your machine (these are RedHat packages, should be same for Fedora?)

libX11
mesa-libGL (If graphics driver is not already installed)
mesa-libGLU (If graphics driver is not already installed)
libXt
xcb-util-wm
xcb-util-image
xcb-util-keysyms
xcb-util-renderutil
libxkbcommon-x11

Also, for the Cubit GUI, a GUI group such as XFCE, LXDE, Mate, or Gnome is recommended – I presume that you meet this suggestion?

Our dev team is off for the weekend, but we’ll have them take a look at this tomorrow if the above suggestions don’t work!

#3

All those things were already instaled, i should point out Trelis 16.5 and 17.1 run without issue, if thats any help to you

#4

I am running Fedora 31 without issues. I have been considering upgrading to Fedora 33. I will try that and see what issues I run into.

#5

Further weirdness, my desktop running FC33 is grand, the laptop running FC33 crashes on the current release. Trelis & older versions of Cubit are fine.

#6

Any updates from your end on this one?

#7

We may have just uncovered the issue a few hours ago.

We believe the issue you’re seeing is that there are a few extraneous libraries that we packaged that are arguing with your system’s libraries. To test, could you please verify whether the following libraries exist with your /path/to/Coreform_Installation/bin/ directory:

libOpenGL.so
libGLX.so
libGLdispatch.so

If those files do exist there, please remove them (maybe move them to your ~/ directory for temporary safe-keeping) and then try running Coreform Cubit again. If this is, in fact, the issue we’ve resolved it in our latest development builds and our imminent release of Coreform Cubit 2021.1 will include this fix. Sorry for the inconvenience this has caused, if this fix doesn’t work, please let me know and we’ll continue digging!

– Greg

#8

Hi Greg

Can confirm, this fixes it!

Thanks

Andy