Собственно вот:
FreeCAD 0.19, Libs: 0.19RUnknown
© Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2021
FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
FreeCAD wouldn’t be possible without FreeCAD community.
.
.
.
.
connect failed: Нет такого файла или каталога (no file …)
Program received signal SIGSEGV, Segmentation fault.
#0 /lib64/libc.so.6(+0x4ad70) [0x7efdee92dd70]
Возникает при file->create
Full About info please.
Try with the latest dev version (about to be released) https://github.com/FreeCAD/FreeCAD-Bundle/releases/tag/weekly-builds or can use the Snap (edge) or the Flatpak (beta)
FreeCAD_weekly-builds-29045-2022-06-06-conda-Linux-x86_64-py39.AppImage - работает, не ругается
./FreeCAD_weekly-builds-29045-2022-06-06-conda-Linux-x86_64-py39.AppImage
FreeCAD 0.20, Libs: 0.20R29045 (Git)
© Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2022
FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
FreeCAD wouldn’t be possible without FreeCAD community.
User path has changed to /home/andreych/.local/share/FreeCAD/. Please move user modules and macros
Please post in english, at least using google translate (if doing this post original text too). Right now I don’t understand what problem you are having if any.
It all started after switching from OpenCuse 15.3 to 15.4
File->New
The application crashes.
If run from a terminal
Program received signal SIGSEGV, Segmentation fault.
#0 /lib64/libc.so.6(+0x4ad70) [0x7efdee92dd70]
File->Open
Works until you try to open the selected file.
Error opening work interface.
When running version 0.2 everything works fine. But I didn’t get far.
It is not clear what version you use, as in one there is a 0.19.something version, in another a 0.20 version.
If you are using an AppImage, it could be possible that there are version mismatch between the libc on your system and the libc on which FC AppImage is compiled.
There are some reports of mismatch especially on some version that use “rather old” libc or “too bleeding edge”.
I have had no problem even if I’m using an Arch Linux distribution that is “rather bleeding edge”.
Yuor mileage may vary, as some problem are generated also by the OpenGL framework that on some distribution is causing some problems.
But without a proper error report and version info these are only supposition.
Regards
Carlo D.
User has updated OpenSUSE distro and v0.19 has stopped working for them.
I’m guessing it’s the distro package that doesn’t work? Either I wouldn’t worry much since 0.20 is working and it’s becoming the stable version this friday.
From AppImage all versions work. Weird, but they work. They do not recognize their own figures from the workbench. Not always, but strange things happen.
All the time there are errors in the log (Python). But continues to work. This is both 0.19 and 0.20 versions. Worked under both OpenSuse and Debian 11.
AppImage is a perversion. It is necessary to collect more familiar rpm and deb packages. I’ll do it when the time comes. I’ll do it when the time comes. In any case, I’ll try.
I am having the same issue trying to run FreeCAD under openSUSE 15.4. Just finished upgrading from openSUSE 15.3 to 15.4 last week and am completing install of all the software I use. After a clean install of FreeCAD using the package in the distro, the application starts and looks like it is fine, but sits and does nothing when I try to open an existing file. All I get is the spinning blue and red arrows. This was working fine under 15.3 and many O/S versions prior.
I then ran FreeCAD from within a terminal window, and I see the following:
FreeCAD
FreeCAD 0.19, Libs: 0.19RUnknown
© Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2021
FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
FreeCAD wouldn’t be possible without FreeCAD community.
connect failed: No such file or directory
The message above happens before I try to do anything in the application. When I attempt to open any file, even one of the examples, I see:
Program received signal SIGSEGV, Segmentation fault.
#0 /lib64/libc.so.6(+0x4ad50) [0x7f7261fc5d50]
To close the application, I have to click the button to close the window, wait for the window to pop that says Application “freecad” is not responding, and click the button to Terminate the application.
TomIGo could you give full stack trace?
You are running an outdated version. Retry with current 0.20 AppImage and if it doesn’t work, try current 0.21.
Thanks chrisb, I tired installing .20, and received several repository errors during install, however, for some reason the one-click install said it was successful! SO I tried running FreeCAD again from terminal and received the same error as before. The application just sat and “clocked” (spinning red/blue arrows) as soon as I clicked on a file to open. So I killed that run and tried installing .21. The install went about the same as .20 and when I run FreeCAD I am seeing the following in the terminal window.
FreeCAD
FreeCAD 0.21, Libs: 0.21RUnknown
© Juergen Riegel, Werner Mayer, Yorik van Havre and others 2001-2022
FreeCAD is free and open-source software licensed under the terms of LGPL2+ license.
FreeCAD wouldn’t be possible without FreeCAD community.
connect failed: No such file or directory
Program received signal SIGSEGV, Segmentation fault.
#0 /lib64/libc.so.6(+0x4ad50) [0x7f24af171d50]
Killed
Thanks openBrian, I attempted to run a gdb session with v.21 installed. This desktop is not a development machine, so I am missing a TON of debug libraries. The gdb session can be found in the attachment gdb.txt. Unfortunately you may not see much of anything that will help.
gdb.txt (71.8 KB)
Sorry openBrian, I had forgotten to do the bt command within gdb. Here is an updated version of the gdb.txt file which includes that.
gdb2.txt (9.71 KB)
In this version I did not try to rung zypper to load all the debug data knowing that they would not load due to the repository issues previously noted.
OK, that’s a bit weird as an error. Won’t be easy to catch.
If you have specific steps you want me to perform that would provide additional information to help the analysis, let me know. I’ll do what I can.
From the web, it seems to be due to incompatibility of Qt5WebEngine with Nouveau driver (guess you have an Nvidia GFX card). Could you try installing proprietary Nvidia driver ?
Hello openBrian, I hesitate to install a native Nvidia driver, as the system that is having this issue is running a Mesa DRI Intel HD Graphics 2000!
Hello again,
I am hoping this helps a bit. I received an update to .21 today so I immediately tried FreeCAD hoping the issue was corrected. It is not fixed, but I am sending along a screen shot I am hoping might help you in the search. Notice that it seems to happen right at the start of trying to load a file (any file), as the progress indicator is stuck at 0% complete. I had literally just clicked the icon to load the example file “EngineBlock.FCStd” when it froze.
When I attempt to click “Add New” on the start screen, it immediately freezes when attempting to start LoadNew.py.
If I attempt to load one of my own drawings, It allows me to select a file, then freezes immediately after I click a filename to open.