Seg fault when opening FC and FC-Daily

Having trouble installing or compiling FreeCAD? Get help here.
Shack
Posts: 34
Joined: Thu Jun 22, 2017 6:19 pm

Seg fault when opening FC and FC-Daily

Postby Shack » Mon Aug 13, 2018 9:30 pm

Hi Guys

When I try to open FC, it shows the loading screen and then crashes.
If I run it through the terminal I get the following:

Code: Select all

Program received signal SIGSEGV, Segmentation fault.
#0  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7f3060b73f20]
#1  /lib/x86_64-linux-gnu/libc.so.6(+0x18ad6a) [0x7f3060cbfd6a]
#2  0x7f301e6573db in QMetaType::registerNormalizedType(QByteArray const&, void (*)(void*), void* (*)(void*, void const*), int, QFlags<QMetaType::TypeFlag>, QMetaObject const*) from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xbb
#3  /usr/lib/python2.7/dist-packages/PySide2/QtCore.x86_64-linux-gnu.so(+0x21b98e) [0x7f301f1b598e]
#4  /usr/lib/python2.7/dist-packages/PySide2/QtCore.x86_64-linux-gnu.so(initQtCore+0x5e) [0x7f301f23f5ae]
#5  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(_PyImport_LoadDynamicModule+0x9b) [0x7f3062803cab]
#6  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x1d4afe) [0x7f3062887afe]
#7  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x151e91) [0x7f3062804e91]
#8  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x152176) [0x7f3062805176]
#9  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyImport_ImportModuleLevel+0x2f5) [0x7f3062805565]
#10  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0xb4de4) [0x7f3062767de4]
#11  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) [0x7f3062707333]
#12  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_CallObjectWithKeywords+0x47) [0x7f30628917a7]
#13  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x3909) [0x7f306275dac9]
#14  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8) [0x7f3062892278]
#15  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19) [0x7f306275a029]
#16  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyImport_ExecCodeModuleEx+0xac) [0x7f30628821cc]
#17  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x1d4462) [0x7f3062887462]
#18  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x1d4a3e) [0x7f3062887a3e]
#19  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x151e91) [0x7f3062804e91]
#20  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyImport_ImportModuleLevel+0x122) [0x7f3062805392]
#21  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0xb4de4) [0x7f3062767de4]
#22  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) [0x7f3062707333]
#23  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_CallObjectWithKeywords+0x47) [0x7f30628917a7]
#24  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x3909) [0x7f306275dac9]
#25  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8) [0x7f3062892278]
#26  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19) [0x7f306275a029]
#27  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76) [0x7f30627fd546]
#28  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x61c4) [0x7f3062760384]
#29  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8) [0x7f3062892278]
#30  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5bf6) [0x7f306275fdb6]
#31  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8) [0x7f3062892278]
#32  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19) [0x7f306275a029]
#33  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76) [0x7f30627fd546]
#34  0x7f3062cdcb46 in Base::InterpreterSingleton::runString[abi:cxx11](char const*) from /usr/lib/freecad/lib/libFreeCADBase.so+0x66
#35  0x7f306377276a in Gui::Application::runApplication() from /usr/lib/freecad/lib/libFreeCADGui.so+0xdfa
#36  freecad(main+0x6db) [0x556b103b34db]
#37  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f3060b56b97]
#38  freecad(_start+0x2a) [0x556b103b468a]
When I try to run Freecad Daily from the terminal I get this:

Code: Select all

Program received signal SIGSEGV, Segmentation fault.
#0  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fc2df891f20]
#1  /lib/x86_64-linux-gnu/libc.so.6(+0x18ad6a) [0x7fc2df9ddd6a]
#2  0x7fc29d34f3db in QMetaType::registerNormalizedType(QByteArray const&, void (*)(void*), void* (*)(void*, void const*), int, QFlags<QMetaType::TypeFlag>, QMetaObject const*) from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0xbb
#3  /usr/lib/python2.7/dist-packages/PySide2/QtCore.x86_64-linux-gnu.so(+0x21b98e) [0x7fc29dead98e]
#4  /usr/lib/python2.7/dist-packages/PySide2/QtCore.x86_64-linux-gnu.so(initQtCore+0x5e) [0x7fc29df375ae]
#5  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(_PyImport_LoadDynamicModule+0x9b) [0x7fc2e1521cab]
#6  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x1d4afe) [0x7fc2e15a5afe]
#7  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x151e91) [0x7fc2e1522e91]
#8  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x152176) [0x7fc2e1523176]
#9  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyImport_ImportModuleLevel+0x2f5) [0x7fc2e1523565]
#10  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0xb4de4) [0x7fc2e1485de4]
#11  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) [0x7fc2e1425333]
#12  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_CallObjectWithKeywords+0x47) [0x7fc2e15af7a7]
#13  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x3909) [0x7fc2e147bac9]
#14  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8) [0x7fc2e15b0278]
#15  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19) [0x7fc2e1478029]
#16  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyImport_ExecCodeModuleEx+0xac) [0x7fc2e15a01cc]
#17  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x1d4462) [0x7fc2e15a5462]
#18  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x1d4a3e) [0x7fc2e15a5a3e]
#19  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x151e91) [0x7fc2e1522e91]
#20  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyImport_ImportModuleLevel+0x122) [0x7fc2e1523392]
#21  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0xb4de4) [0x7fc2e1485de4]
#22  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x43) [0x7fc2e1425333]
#23  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_CallObjectWithKeywords+0x47) [0x7fc2e15af7a7]
#24  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x3909) [0x7fc2e147bac9]
#25  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8) [0x7fc2e15b0278]
#26  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19) [0x7fc2e1478029]
#27  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76) [0x7fc2e151b546]
#28  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x61c4) [0x7fc2e147e384]
#29  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8) [0x7fc2e15b0278]
#30  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x5bf6) [0x7fc2e147ddb6]
#31  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x7d8) [0x7fc2e15b0278]
#32  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19) [0x7fc2e1478029]
#33  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76) [0x7fc2e151b546]
#34  0x7fc2e19fc356 in Base::InterpreterSingleton::runString[abi:cxx11](char const*) from /usr/lib/freecad-daily/lib/libFreeCADBase.so+0x66
#35  0x7fc2e249915b in Gui::Application::runApplication() from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x114b
#36  freecad-daily(main+0x6db) [0x558812cb54fb]
#37  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fc2df874b97]
#38  freecad-daily(_start+0x2a) [0x558812cb66aa]
I run Ubuntu 18.04, and have tried purge, autoremove and reinstall.
Same result.
Any ideas?
User avatar
kkremitzki
Posts: 2197
Joined: Thu Mar 03, 2016 9:52 pm
Location: Texas

Re: Seg fault when opening FC and FC-Daily

Postby kkremitzki » Mon Aug 13, 2018 10:04 pm

This looks like it was probably caused by me. I can take a further look shortly when I get home.
Like my FreeCAD work? I'd appreciate any level of support via Patreon, Liberapay, or PayPal! Read more about what I do at my blog.
Shack
Posts: 34
Joined: Thu Jun 22, 2017 6:19 pm

Re: Seg fault when opening FC and FC-Daily

Postby Shack » Wed Aug 15, 2018 11:47 am

That would be great! :)
Is there any info you would like me to provide?
Shack
Posts: 34
Joined: Thu Jun 22, 2017 6:19 pm

Re: Seg fault when opening FC and FC-Daily

Postby Shack » Sun Sep 16, 2018 9:40 pm

@kkremitzki
any news on this? the problem is still there :/
User avatar
NormandC
Posts: 18534
Joined: Sat Feb 06, 2010 9:52 pm
Location: Québec, Canada

Re: Seg fault when opening FC and FC-Daily

Postby NormandC » Sun Sep 16, 2018 9:44 pm

Hello Shack,

I have no such issue with both freecad and freecad-daily packages on Ubuntu 18.04.

It is very odd that there are calls to libQt5Core because the current packages are still based on Qt4.

Please give us more info on your desktop environment. Do you use default GNOME desktop? What is your graphics card and driver? Did FreeCAD use to work properly, or you never succeeded opening it?

Is your Ubuntu a fresh install, or did you upgrade from a prior version?
User avatar
sgrogan
Posts: 6211
Joined: Wed Oct 22, 2014 5:02 pm

Re: Seg fault when opening FC and FC-Daily

Postby sgrogan » Wed Sep 19, 2018 10:09 pm

Shack wrote:
Wed Aug 15, 2018 11:47 am
Is there any info you would like me to provide?
Any chance that at some point you tried the freecad-python3 package from the daily PPA?
"fight the good fight"
R-INYURU
Posts: 11
Joined: Sat Jun 09, 2018 4:23 pm

Re: Seg fault when opening FC and FC-Daily

Postby R-INYURU » Fri Sep 21, 2018 2:34 pm

NormandC wrote:
Sun Sep 16, 2018 9:44 pm

I have no such issue with both freecad and freecad-daily packages on Ubuntu 18.04.
How did you get to install FC-daily on Ubuntu 18.04? For me I am having trouble to install it.
Trying to learn more about FreeCAD, any idea I will appreciate.
User avatar
NormandC
Posts: 18534
Joined: Sat Feb 06, 2010 9:52 pm
Location: Québec, Canada

Re: Seg fault when opening FC and FC-Daily

Postby NormandC » Fri Sep 21, 2018 2:56 pm

R-INYURU wrote:
Fri Sep 21, 2018 2:34 pm
How did you get to install FC-daily on Ubuntu 18.04?
The simplest way there is: by Synaptic Package Manager. I very rarely enter a single line of code in a terminal. I prefer to use GUI tools when they are available.

If it's not working for you, then as explained by triplus in your other topic, the problem lies deeper and the freecad/freecad-daily packaging has no relevance to it.

triplus wrote:
Fri Sep 21, 2018 12:16 am
Too bad. Therefore likely more in-depth investigation will be needed on what got borked during the upgrade procedure. And to sort out the dependencies first. Some old package causing the problems or something like that is likely at play.
In 10 years of Ubuntu usage I have never used the upgrade process to go from a version to another. I don't trust it. I always do a fresh install. Because I install /home in a separate partition it is not difficult.
Shack
Posts: 34
Joined: Thu Jun 22, 2017 6:19 pm

Re: Seg fault when opening FC and FC-Daily

Postby Shack » Wed Oct 03, 2018 1:17 pm

NormandC wrote:
Sun Sep 16, 2018 9:44 pm
Hello Shack,

I have no such issue with both freecad and freecad-daily packages on Ubuntu 18.04.

It is very odd that there are calls to libQt5Core because the current packages are still based on Qt4.

Please give us more info on your desktop environment. Do you use default GNOME desktop? What is your graphics card and driver? Did FreeCAD use to work properly, or you never succeeded opening it?

Is your Ubuntu a fresh install, or did you upgrade from a prior version?
Im using the default gnome desktop, My graphic card is Intel HD Graphics 520, driver is i915
filename: /lib/modules/4.15.0-36-generic/kernel/drivers/gpu/drm/i915/i915.ko
license: GPL and additional rights
description: Intel Graphics
author: Intel Corporation
author: Tungsten Graphics, Inc.


Freecad used to work perfectly, but stopped for some reason, possibly because I did an autoremove or similar.
I have tried reinstalling it, but I have the same issue.

If I use the appimages it works fine (but I do prefer the PPA)
sgrogan wrote:
Wed Sep 19, 2018 10:09 pm
Shack wrote:
Wed Aug 15, 2018 11:47 am
Is there any info you would like me to provide?
Any chance that at some point you tried the freecad-python3 package from the daily PPA?
I might have, but I dont think so
Shack
Posts: 34
Joined: Thu Jun 22, 2017 6:19 pm

Re: Seg fault when opening FC and FC-Daily

Postby Shack » Thu Oct 04, 2018 8:23 am

Compiled FC from source and I'm getting the exact same segfault :S