FreeCAD on PI4 and Raspbian Buster.

[plugwash]

I didn't try to actually do anything, I just loaded the GUI, I thought that was what at least some people were having trouble with.

[Gavinmc42]

I didn't try to actually do anything, I just loaded the GUI, I thought that was what at least some people were having trouble with.

Nope the GUI is fine now, we can sit and stare at it for ages
It is just when you create a new file it crashes and vanishes.

[framboise_314]

hello
same trouble here
GUI launch ok Click New and oups GUI is gone away
regards
framboise314

[thrustpork]

Any news on this? FreeCAD is the last piece of the puzzle for me after switching my desktop out for a Pi4. I managed to get slic3r working, just need my handy CAD program to get back to 3D printing useless stuff.

[jamesh]

Has this been reported to Freecad? They are probably best placed to figure out what the problem is.

[fruitoftheloom]

Has this been reported to Freecad? They are probably best placed to figure out what the problem is.

https://forum.freecadweb.org/viewtopic.php?f=42&t=37458


https://forum.freecadweb.org/viewtopic.php?f=12&t=37314

[jamesh]

Has this been reported to Freecad? They are probably best placed to figure out what the problem is.

https://forum.freecadweb.org/viewtopic.php?f=42&t=37458

https://forum.freecadweb.org/viewtopic.php?f=12&t=37314

Those threads are about as much use as chocolate teapot.

[jbeale]

Is this relevant to the issue?
FreeCAD crashes on creating a new document or opening a file
https://www.freecadweb.org/wiki/FAQ#Fre ... ing_a_file

[plugwash]

Is this relevant to the issue?
FreeCAD crashes on creating a new document or opening a file
https://www.freecadweb.org/wiki/FAQ#Fre ... ing_a_file

Doesn't look like it, everything seems to be built against the same version of libCoin.

[thrustpork]

That looks promising

[Gavinmc42]

Anyone tried building from source?

I had to do a dist-upgrade to fix the Buster release/stable issue and just installed freecad again.
Same issue starts up and then disappears when "creating new"

Got this message, looks like a OpenGL error?

Code: Select all

freecad
FreeCAD 0.18, Libs: 0.18R
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2019
  #####                 ####  ###   ####  
  #                    #      # #   #   # 
  #     ##  #### ####  #     #   #  #   # 
  ####  # # #  # #  #  #     #####  #   # 
  #     #   #### ####  #    #     # #   # 
  #     #   #    #     #    #     # #   #  ##  ##  ##
  #     #   #### ####   ### #     # ####   ##  ##  ##

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) [0xb344d120]

That link had the freecad --write -log info and this is the end of the log file.

Code: Select all

Log: Init: Loading FreeCAD GUI
Log: D-Bus global menu: no
Log: Init: Running FreeCADGuiInit.py start script... done
Log: Init: Activating default workbench StartWorkbench
Log: Loading GUI of Web module... done
Log: Loading GUI of Start module... done
Log: Loading Start module... done
Log: D-Bus system tray: no
Log: Init: Showing main window
Log: Main window restored
Log: Show main window
Log: Toolbars restored
Log: Couldn't connect to spacenav daemon
Log: Init: Entering event loop
Log: Init: Processing command line files
Err: Program received signal SIGSEGV, Segmentation fault.
Err: #0  /lib/arm-linux-gnueabihf/libc.so.6(__default_sa_restorer+0) [0xb344e120]

[thrustpork]

This seems to still be an issue after the most recent update. Does anyone more technically inclined know who I could poke to get this headed towards a fix? I'm not sure if the problem is with the compile, rpi, opengl, etc.

[Gavinmc42]

Spent most of the day trying to compile the newer versions .18.3 and .19
Dependency hell.
Maybe one day we will get an appimages for arm/arm64.

No big deal yet as I will be moving to Gentoo64 on Pi4 as my development desktop and that could be a month or more away.
Plus I still need to wait for next batch of the 4B4's to make it down under.

There is an alternative 3D modeler.
These tuts I have done in Gentoo64 on a 3B+, they should be doable now on a Pi4 and Buster.
https://projects.raspberrypi.org/en/pro ... 5D=blender

These big 3D modelers have the bells and whistles.
Is there a nice small simple one?
An offline one?

[Gavinmc42]

Wings3D just installed and worked
Very basic, but probably enough to keep me busy.

It does obj and UV which is enough to make some simple 3D models for OpenGL games.
Not as intuitive as Blender for Artists. It is way smaller

Need more time to see if it can replace FreeCAD.
I use FreeCAD for STEP imports into Altium and cnc stuff for machining.

[kkremitzki]

Hi all, I'm the maintainer of FreeCAD on Debian. The issue in the first post was likely caused by having freecad-doc installed; the old version of freecad-doc is no longer co-installable with the new package, because it installs files on a path that is now a symlink managed by the alternatives system. (see update-alternatives manpage.) There is a way to prevent this bad apt behavior but I removed it too early (Breaks+Replaces for freecad-doc in the debian/control file.)

The problem with the UI crashing is coming from our dependency Coin3D, which is a scene graph library and baked in pretty deeply into FreeCAD. If, for example, you wanted to try to compile things natively to see if it's a packaging bug or a bug in either the FreeCAD or Coin3D, you'd have to build Coin3D, then SoQt, then Pivy, then FreeCAD.

The other problem is that the Debian 10 freeze and FreeCAD's 0.18 release didn't line up well (see my latest post at kwk.systems/blog) and so the version in Raspbian is a pre-release, while we're already on 0.18.3. Thus, for narrowing down this bug, it would be ideal for someone to test via a Debian Testing arm64 image which has this 0.18.3 package available. I don't have a RPi4 yet or I'd do it myself.

[Gavinmc42]

I don't have a RPi4 yet or I'd do it myself.

Please get one, then we can ask really tricky questions
But in a few months it will probably just work.

The Python3 and QT5 issues has caused me problems, now I know why.

I am waiting for some 4B4's to be available here.
My 4B1 is not the best compiler box.
When I get a 4B4 I will probably be running Gentoo64 on it.
Maybe I should get 2?

I have yet to try Sakaki's new Debian 64bit build, the previous one worked really well.

FreeCAD on Pi will be very interesting, since I have used it since version 12? on PC's.
No other CAD program was as easy to learn, I know I tried them ALL.

The new G-code stuff for CAM got my attention since I have used LinuxCNC and TurboCNC before.
Getting serious CAD tools onto Pi's enables the maker revolution quite a bit.

[ShiftPlusOne]

Hi all, I'm the maintainer of FreeCAD on Debian. The issue in the first post was likely caused by having freecad-doc installed; the old version of freecad-doc is no longer co-installable with the new package, because it installs files on a path that is now a symlink managed by the alternatives system. (see update-alternatives manpage.) There is a way to prevent this bad apt behavior but I removed it too early (Breaks+Replaces for freecad-doc in the debian/control file.)

The problem with the UI crashing is coming from our dependency Coin3D, which is a scene graph library and baked in pretty deeply into FreeCAD. If, for example, you wanted to try to compile things natively to see if it's a packaging bug or a bug in either the FreeCAD or Coin3D, you'd have to build Coin3D, then SoQt, then Pivy, then FreeCAD.

The other problem is that the Debian 10 freeze and FreeCAD's 0.18 release didn't line up well (see my latest post at kwk.systems/blog) and so the version in Raspbian is a pre-release, while we're already on 0.18.3. Thus, for narrowing down this bug, it would be ideal for someone to test via a Debian Testing arm64 image which has this 0.18.3 package available. I don't have a RPi4 yet or I'd do it myself.

Thank you very much for joining and providing the insights.

Would backporting 0.18.3 to stretch without rebuilding the dependencies be a sensible thing to try or would you expect the issue to still be there? The archive.raspberrypi.org repo is fairly flexible, so if there's anything we can do to fix the issue, I'm happy to try it.

[kkremitzki]

Thank you very much for joining and providing the insights.

Would backporting 0.18.3 to stretch without rebuilding the dependencies be a sensible thing to try or would you expect the issue to still be there? The archive.raspberrypi.org repo is fairly flexible, so if there's anything we can do to fix the issue, I'm happy to try it.

Did you mean to buster? I suspect the Coin3D issue will still be there, but the issue in the first post should be fairly easily resolvable, though it would be nice to have confirmation that it was what I think it was and not something else. Backporting 0.18.3 in general should be pretty much trivial and unlikely to cause issues. The version currently in the repos had been under feature freeze for about 2 months and is missing about a month of bugfixes between it and 0.18 proper, plus the other bugfix releases leading up to 0.18.3.

Do you have any links handy about what the process for doing this backport & fix would be on my end?

[Gavinmc42]

I am compiling and get these message, tried 3 versions of FreeCAD even going back to 16.
QT is too new?

Code: Select all

-- Found unsuitable Qt version "5.11.3" from /usr/bin/qmake
Qt QTOPENGL library not found.
Qt QTSVG library not found.
Qt QTUITOOLS library not found.
Qt QTWEBKIT library not found.
Qt QTGUI library not found.
Qt QTXML library not found.
Qt QTNETWORK library not found.
Qt QTCORE library not found.
CMake Error at CMakeLists.txt:703 (MESSAGE):
  =======================

  Qt libraries not found.

  =======================



-- Configuring incomplete, errors occurred!
See also "/home/pi/FreeCAD-0.16/CMakeFiles/CMakeOutput.log".
See also "/home/pi/FreeCAD-0.16/CMakeFiles/CMakeError.log".

Just tried the staging version, same error except Qt4 not found

Code: Select all

CMake Error at CMakeLists.txt:888 (message):
  ========================

  Qt4 libraries not found.

  ========================

Need to revert QT?

[kkremitzki]

The default source build config is Qt 4 + Python 2, but the package is built with Qt 5 and Python 2 + 3, so if you did for example

Code: Select all

sudo apt build-dep freecad

you have the Qt 5 dependencies.

In order to build with Qt 5 you need to include

Code: Select all

-DBUILD_QT5=ON

when you call cmake. For Python 3, you need

Code: Select all

-DPYTHON_EXECUTABLE=/usr/bin/python3

. Currently there is no Qt 4 + Python 3 build support in terms of packages, but it has been requested so it's on my list.

For reference you can also take a look at the debian/rules file which specifies some of the build information about the package, including CMake flags.

https://salsa.debian.org/science-team/f ... bian/rules

[ShiftPlusOne]

I had a build running for a while, but obviously it's a large package, so it won't be done any time soon. Will report back once I get a chance to test it tomorrow.

[Gavinmc42]

Thanks Kurt,

Will try tonight, but I think you might have solved my OpenSCAD compile QT issue too.
QT5 and Python 3, is my preferred option, I have no need for legacy code

[benbunk]

I ran the build on my raspberry pi 4 based on the tag on github for 0.18.3 but I didn't have any luck. As soon as I selected an STL file to open it crashed.

Output:
pi@raspberrypi:~/freecad-source $ bin/FreeCAD
FreeCAD 0.18, Libs: 0.18R16093 +38 (Git)
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2019
##### #### ### ####
# # # # # #
# ## #### #### # # # # #
#### # # # # # # # ##### # #
# # #### #### # # # # #
# # # # # # # # # ## ## ##
# # #### #### ### # # #### ## ## ##

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) [0xb21f0120]


Build Steps:
#1 Get the Repo
pi@raspberrypi:~/freecad-source $ git fetch --all --tags --prune
Fetching origin
pi@raspberrypi:~/freecad-source $ git checkout tags/0.18.3 -b 0.18.3
Checking out files: 100% (2633/2633), done.
Switched to a new branch '0.18.3'

#2 Compile
sudo apt install cmake cmake-gui libboost-date-time-dev libboost-dev libboost-filesystem-dev libboost-graph-dev libboost-iostreams-dev libboost-program-options-dev libboost-python-dev libboost-regex-dev libboost-serialization-dev libboost-signals-dev libboost-thread-dev libcoin-dev libeigen3-dev libgts-bin libgts-dev libkdtree++-dev libmedc-dev libocct-data-exchange-dev libocct-ocaf-dev libocct-visualization-dev libopencv-dev libproj-dev libpyside2-dev libqt5opengl5-dev libqt5svg5-dev libqt5webkit5-dev libqt5x11extras5-dev libqt5xmlpatterns5-dev libshiboken2-dev libspnav-dev libvtk7-dev libx11-dev libxerces-c-dev libzipios++-dev occt-draw pyside2-tools python3-dev python3-matplotlib python3-pivy python3-ply python3-pyside2.qtcore python3-pyside2.qtgui python3-pyside2.qtsvg python3-pyside2.qtwidgets python3-pyside2uic qtbase5-dev qttools5-dev swig

mkdir freecad-build
cd freecad-build
cmake -DBUILD_QT5=ON -DPYTHON_EXECUTABLE=/usr/bin/python3 ../freecad-source
cd ../freecad-source
make -j4

[ShiftPlusOne]

No luck either. I tried a pivy example without using freecad directly and get a segfault as well.

[ShiftPlusOne]

No luck with the latest version of coin3d and soqt using these instructions either - https://bitbucket.org/Coin3D/coin/wiki/BuildWithCMake

I've tried a few examples that try to use them, but I get the context setup error from cc_glglue_instance and then the segfault.

Edit: Just noticed somebody has already opened the appropriate issue - https://freecadweb.org/tracker/view.php?id=4083 .