Ticket #4083: A bug in the Coin3D library causing app to crash on RPi4

[Kunda1]

issue #4083: A bug in the Coin3D library causing app to crash on RPi4
Error:

Code: Select all

Coin warning in cc_glglue_instance(): Error when setting up the GL context. This can happen if there is no current context, or if the context has been set up incorrectly.
Program received signal SIGSEGV, Segmentation fault.
#0 /lib/arm-linux-gnueabihf/libc.so.6(__default_sa_restorer+0)

Relevant thread:
https://forum.freecadweb.org/viewtopic. ... 58#p318973

[Kunda1]

Looks like a bug was opened on Debian for the same reason: https://bugs.debian.org/cgi-bin/bugrepo ... bug=931458

Other relevant threads:
https://www.raspberrypi.org/forums/view ... p?t=244151 (FreeCAD on PI4 and Raspbian Buster)
https://www.raspberrypi.org/forums/view ... p?t=244757 (Bugreport: Where?)

[kkremitzki]

I tested this behavior inside a Debian 10 VM running the arm64 architecture, and wasn't able to reproduce it. (Using virt-manager/libvirt plus qemu-system-arm)

[vocx]

I tested this behavior inside a Debian 10 VM running the arm64 architecture, and wasn't able to reproduce it. (Using virt-manager/libvirt plus qemu-system-arm)

If I'm not mistaken, the Raspbian distribution used in Raspberry Pi is "armhf" (32-bit), not "arm64".

[kkremitzki]

Ah, oops, I thought they had updated already.

[Muniac]

Hi - I just completed a FreeCAD 0.19 build from source to attempt to run it on the pi4 Buster. No luck. Program starts but crashes when File-New is selected. Message below:

Coin warning in cc_glglue_instance(): Error when setting up the GL context. This can happen if there is no current context, or if the context has been set up incorrectly.
Program received signal SIGSEGV, Segmentation fault.
#0 /lib/arm-linux-gnueabihf/libc.so.6(__default_sa_restorer+0) [0xb1979120]

Same as what others are getting. I was hoping FreeCAD can run on the pi4. PrusaSlicer runs fine and FreeCAD would make a nice companion for the modeling. I do have a FreeCAD version running on the pi4 using the old default build. Just wondering if any progress has been made on correcting this problem for the new build. I'd be more than happy to do pi4 testing and building to help the cause along. Many thanks for the efforts.

[vocx]

Hi - I just completed a FreeCAD 0.19 build from source to attempt to run it on the pi4 Buster. No luck. Program starts but crashes when File-New is selected. Message below:
...

You can compile and run FreeCAD 0.19 in the Raspberry Pi 4, but it seems you have to use Py2 and Qt4, instead of Py3 and Qt5.

FreeCAD and Raspberry Pi 4

[Muniac]

Yes you are correct. I've done that with success. I like to keep software current when possible. It's that notion that led me to try a build with Python3 and QT5. Something else with the new build regarding the screen bordering.



You'll notice it's cutoff slightly at the top. And right top. Would be really nice to get this new build running. Many thanks.

[vocx]

I like to keep software current when possible. It's that notion that led me to try a build with Python3 and QT5.

Unfortunately, the situation is a bit tricky, as basically FreeCAD has already dropped support for Python 2 and Qt4. Most developers don't thoroughly test their software with these versions. Probably 0.19 will be the last version to support Py2/Qt4.

Maybe the problem is not with FreeCAD itself but rather with Coin and Qt5, so this has to be investigated by those developers together with Raspberry Pi maintainers.

[Muniac]

Thanks. FreeCAD is a nice modeling application. I have a Prusa 3D printer and FreeCAD is a perfect companion to their Slicer. The FreeCAD appimage runs on my Mint 19.1 system (old Dell Inspiron 1501). I'm just getting ready to build up a new workstation which is long overdue. Would like to keep that in the Linux family. Just not a big fan of Windows and the direction(s) its heading. The pi4 shows some promise if the glitches can be worked out. Which I know aren't easy or quick fixes. Tons of hobbyists out there could use the pi4 for tinkering and serious projects.

I did put a post out on the Raspberry pi forum about this. Perhaps something good can come of that. They know best all the details of that architecture. Lots of those boards out there so a fix of something broken makes a lot of folks happy.