[SOLVED] FreeCAD not starting

however · 02-05-2024, 01:39 PM

Hi again,

maybe not the right forum to ask this but every once-in-a-while, after a 'slackpkg-upgrade-all', a few other packages stops working.

I know, i am using the 'current' version which is under continuous development and libraries change with certain risks.

This time it's the turn of FreeCAD. When launched from application menu,the splash screen starts, it seems to lad but then it disappear and nothing else happens.

When I launch the appimage from console, i get this error:

Code:

FreeCAD 0.21.2, Libs: 0.21.2R33771 (Git)
© Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2023
FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
FreeCAD wouldn't be possible without FreeCAD community.
  #####                 ####  ###   ####  
  #                    #      # #   #   # 
  #     ##  #### ####  #     #   #  #   # 
  ####  # # #  # #  #  #     #####  #   # 
  #     #   #### ####  #    #     # #   # 
  #     #   #    #     #    #     # #   #  ##  ##  ##
  #     #   #### ####   ### #     # ####   ##  ##  ##

MESA-LOADER: failed to open nouveau: /usr/lib64/dri/nouveau_dri.so: undefined symbol: amdgpu_va_get_start_addr (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: nouveau
MESA-LOADER: failed to open nouveau: /usr/lib64/dri/nouveau_dri.so: undefined symbol: amdgpu_va_get_start_addr (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: nouveau
MESA-LOADER: failed to open swrast: /usr/lib64/dri/swrast_dri.so: undefined symbol: amdgpu_va_get_start_addr (search paths /usr/lib64/dri, suffix _dri)
failed to load driver: swrast
QGLXContext: Failed to create dummy context
Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile) 
/tmp/.mount_FreeCAGKHK1G/AppRun: line 43: 22852 Aborted                 ${MAIN} "$@"
bash-5.2$

I know that slackware doesn't support appimages however, it has always worked so far (similarly to other appimage packages that I use regularly, and still do).

Can anyone help?

Thanks

however · 02-05-2024, 02:28 PM

Searching the net I learned that a slackware 15 user solved a similar issue switching from 'wayland' to 'X11'.

This captured my attention, as I don't even know what X-system my slackware-current is running so, I run 'echo $XDG_SESSION_TYPE and it returned:

Code:

bash-5.2$ echo $XDG_SESSION_TYPE
tty
bash-5.2$

TeleTYpewriter? wasn't that a thing of the past? What do I actually start by launching 'startx'?

henca · 02-06-2024, 01:02 AM

Those error messages seem really messy...

To run FreeCAD you will need working hardware accelerated OpenGL.

The error messages seem to indicate that you are using the nouveau driver which is the opensource driver for nVidia cards. However, it complains about missing symbols which seem to be for an AMD GPU.

What kind of GPU do you have? Which driver are you trying to use with that GPU?

regards Henrik

pan64 · 02-06-2024, 01:07 AM

probably it is similar:
https://community.clearlinux.org/t/m...nitialize/9386

however · 02-06-2024, 04:00 AM

Quote:

Originally Posted by henca

Those error messages seem really messy...

To run FreeCAD you will need working hardware accelerated OpenGL.

The error messages seem to indicate that you are using the nouveau driver which is the opensource driver for nVidia cards. However, it complains about missing symbols which seem to be for an AMD GPU.

What kind of GPU do you have? Which driver are you trying to use with that GPU?

regards Henrik

Thank you for your input.
Sadly, I have been blessed with those nouveau driver for decades (since installing the native NVIDIA drivers it's literally impossible on my system) however, to be honest, it has never been a major issues in fact, as I said in the OP, FreeCAD (and almost any other heavy-graphic demanding packages I have used, including Blender up until the last 'slackpkg upgrade-all') had been working fine for years.

Quote:

Originally Posted by pan64

probably it is similar:
https://community.clearlinux.org/t/m...nitialize/9386

This gets my suspicions semi-confirmed as I remember MESA being one of the packages being upgraded during the last 'slackpkg upgrade-all'. (since the last MESA upgrade, coincidentally, i 'lost' blender too)

So, I suppose the solution to this is to wait until they (MESA developers) receive enough bug-reports and fix the issue at the (somehow) next upgrade.

Thanks

nobodino · 02-08-2024, 12:20 AM

I had the same problem with the same FreeCAD AppImage, downgrading to mesa-23.3.4-x86_64-1.txz solved the problem.

however · 02-08-2024, 04:35 AM

Quote:

Originally Posted by nobodino

I had the same problem with the same FreeCAD AppImage, downgrading to mesa-23.3.4-x86_64-1.txz solved the problem.

Thank you.

Would you be so kind to share the mesa-23.3.4-x86_64-1.txz file?

I have found the source code on mesa website but I can't find the slackbuild anywhere; and, of course, couldn't find it on the web either.

Thanks

p.s.: I tried to do it the old way <unpack && make && make install> but it seems that the old conventional way of compiling && installing a package is disappearing on linux.

Petri Kaukasoina · 02-08-2024, 05:20 AM

https://slackware.uk/cumulative/slac...4-x86_64-1.txz

however · 02-08-2024, 05:33 AM

Quote:

Originally Posted by Petri Kaukasoina

https://slackware.uk/cumulative/slac...4-x86_64-1.txz

Thanks a million.

I confirm that downgrading to 'mesa-23.3.4-x86_64-1.txz' has solved the issue.

Quote:

Originally Posted by nobodino

I had the same problem with the same FreeCAD AppImage, downgrading to mesa-23.3.4-x86_64-1.txz solved the problem.

Thank you for the tip and,

thanks everyone.

igorv · 02-16-2024, 03:08 AM

I've faced the same problem. Found another way without downgrading mesa:
LD_PRELOAD=/usr/lib64/libdrm_amdgpu.so.1 ./FreeCAD-0.21.2-Linux-x86_64.AppImage

however · 02-16-2024, 05:36 AM

Quote:

Originally Posted by igorv

I've faced the same problem. Found another way without downgrading mesa:

HI and thank you for the input.

Quote:

LD_PRELOAD=/usr/lib64/libdrm_amdgpu.so.1 ./FreeCAD-0.21.2-Linux-x86_64.AppImage

Would you be so kind to explain what to do with such fairy complex command line?

If I run it on konsole it starts FreeCAD so,I guess it should be the permanent Application Menu command to start FreeCAD? What will happen at the next upgrade of either MESA or FreeCAD?

Thanks

igorv · 02-16-2024, 08:16 AM

Quote:

Originally Posted by however

Would you be so kind to explain what to do with such fairy complex command line?

If I run it on konsole it starts FreeCAD so,I guess it should be the permanent Application Menu command to start FreeCAD?

Sure, some steps must be done to fill yourself comfortable. (i) make a symlink to the AppImage. It shortens you input and makes it independent from future FreeCAD updates. (ii) If you prefer console, make a bash alias in your .profile/.bashrc file, i.e. alias freecad="LD_PRELOAD=/usr/lib64/libdrm_amdgpu.so /usr/bin/FreeCAD" (Here /usr/bin/FreeCAD is my symlink to the current FreeCAD image). If you use come XWindow Desktop Environment, you may edit the proper .desktop file, namely, the Exec line, i.e. change "Exec=freecad %F" to "Exec=env LD_PRELOAD=/usr/lib64/libdrm_amdgpu.so freecad %F".

Quote:

Originally Posted by however

What will happen at the next upgrade of either MESA or FreeCAD?

On either upgrade you have to check (i) if you still need this workaround, (ii) keep symlinks consistent with new filenames.

nobodino · 02-17-2024, 12:39 AM

I followed your piece of advice, my FreeCAD script is:

Code:

#!/bin/sh
export LD_LIBRARY_PATH=/opt/OpenCASCADE/lib64:$LD_LIBRARY_PATH
export QTWEBENGINE_DISABLE_SANDBOX=1
export LD_PRELOAD=/usr/lib64/libdrm_amdgpu.so.1 
exec /opt/FreeCAD/FreeCAD.AppImage "$@"

Thanks.

however · 05-21-2024, 02:21 PM

Quote:

Originally Posted by nobodino

I followed your piece of advice, my FreeCAD script is:

Code:

#!/bin/sh
export LD_LIBRARY_PATH=/opt/OpenCASCADE/lib64:$LD_LIBRARY_PATH
export QTWEBENGINE_DISABLE_SANDBOX=1
export LD_PRELOAD=/usr/lib64/libdrm_amdgpu.so.1 
exec /opt/FreeCAD/FreeCAD.AppImage "$@"

Thanks.

Is it the issue with 'current' that justifies all these broken 'pipes'? or just me/my anomalous system?

after solving/overcoming the MESA issues with the script and, after a random 'slackpkg update/upgrade-all', FreeCAD won't launch again, even through the script

Quote:

execvp:Exec format error

(neither on my desktop nor on my laptop)

pan64 · 05-22-2024, 02:08 AM

exec format error means it is not an executable on that platform.
what will file /opt/FreeCAD/FreeCAD.AppImage respond?