Known OS specific Issues

Post here for help on using FreeCAD's graphical user interface (GUI).
Forum rules
and Helpful information
IMPORTANT: Please click here and read this first, before asking for help

Also, be nice to others! Read the FreeCAD code of conduct!
chrisb
Posts: 17489
Joined: Tue Mar 17, 2015 9:14 am

Known OS specific Issues

Postby chrisb » Wed Aug 29, 2018 6:38 am

This topic is locked. For comments go to https://forum.freecadweb.org/viewtopic.php?f=3&t=30574
  • For modeling issues please refer to the FAQ and the Troubleshooting models
  • Ubuntu does not show *.FCStd files and does not use the file extension on saving
    This is an issue with the system file selection dialog. From another topic:
    wmayer wrote:
    Sun Jan 27, 2019 11:23 am
    The problem is somehow with the native file dialog on some DEs. The easiest would be to upgrade to v0.18 where we have added an option to change at runtime between the native and Qt file dialog.

    Therefore open the Parameter editor from the Tools menu and navigate to BaseApp/Preferences/Dialog. Now create a boolean parameter DontUseNativeDialog and set it to true.
  • Startup fails on Debian based system like Ubuntu, Debian, Mint, ...
    FreeCAD startup may fail with the message

    Code: Select all

    failed to create drawable
    [xcb] Unknown sequence number while processing queue
    [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
    [xcb] Aborting, sorry about that.
    freecad: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
    Aborted
    gntech recommends
    gntech wrote:
    Thu Apr 12, 2018 6:04 pm
    A workaround is to disable DRI3 just for Freecad by launching freecad from the terminal with the following command.

    Code: Select all

    LIBGL_DRI3_DISABLE=true freecad
  • Crash on Debian based systems importing SVG
    Hint from NormandC: The current PPAs fix this by upgrading some dependencies. Users who previously implemented Chris_G's fix mentioned below should revert the change (unlock the expat/libexpat1 packages and update them to the version in the Ubuntu 18.04/18.10 repo) for the PPA update to succeed.

    Outdated message:
    FreeCAD can crash when importing SVG files with a message like
    jalar wrote:
    Wed Jan 10, 2018 1:19 pm

    Code: Select all

    openat(AT_FDCWD, "/path-to-file.svg", O_RDONLY) = 27
    fstat(27, {st_mode=S_IFREG|0644, st_size=2234752, ...}) = 0
    --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x3a9} ---
    write(2, "\33[1;31m", 7)                = 7
    write(2, "Program received signal SIGSEGV,"..., 53Program received signal SIGSEGV, Segmentation fault.
    ) = 53
    
    #0  /lib/x86_64-linux-gnu/libc.so.6(+0x37140) [0x7fd97f382140]
    #1  /lib/x86_64-linux-gnu/libexpat.so.1(XML_SetHashSalt+0x1b) [0x7fd976c411cb]
    #2  /usr/lib/python2.7/lib-dynload/pyexpat.x86_64-linux-gnu.so(+0x6968) [0x7fd90487a968]
    ...
    
    As a solution some libraries have to be installed manually:
    Chris_G wrote:
    Thu Apr 19, 2018 8:45 am
    The packages from Ubuntu xenial work fine :
    https://packages.ubuntu.com/xenial/expat
    https://packages.ubuntu.com/xenial/libexpat1
    I have also this one, but I don't know if it is really needed :
    https://packages.ubuntu.com/xenial/libexpat1-dev

    Then in the folder where you downloaded the packages :

    Code: Select all

    sudo dpkg -i ./expat_2.1.0-7ubuntu0.16.04.3_amd64.deb
    sudo echo expat hold | sudo dpkg --set-selections
    sudo dpkg -i ./libexpat1_2.1.0-7ubuntu0.16.04.3_amd64.deb
    sudo echo libexpat1 hold | sudo dpkg --set-selections
    sudo dpkg -i ./libexpat1-dev_2.1.0-7ubuntu0.16.04.3_amd64.deb
    sudo echo libexpat1-dev hold | sudo dpkg --set-selections
    
  • The change from Qt4 to Qt5 can cause issues on Windows and MacOS:
    wmayer wrote:
    Fri May 03, 2019 11:17 am
    The responsible change that could explain the behaviour is the move from Qt4 to Qt5. Qt5 has a module QtOpenGL kept for backward compatibility but it's recommended not to use it and instead to port old code to the new API. At the beginning when we moved to Qt5 we used this module but it caused several problems and we then ported our code using the recommended API.

    Under the hood the implementation of OpenGL support in Qt5 has changed a lot and it's hard to say what at the end is responsible if something doesn't work. But as said above in most cases it's the graphic driver that causes problems.
    For more information also have a look here: https://doc.qt.io/qt-5/windows-requirem ... cs-drivers Maybe you can get it to work by setting the variable QT_OPENGL
  • Windows display driver
    There are issues with Radeon graphic cards. If your objects show transparency where they should not, it may be caused by the Radeon driver.
    SirSpamalot wrote:
    Tue Aug 28, 2018 10:46 pm
    I have a Radeon RX 460 card. It appears that I updated the driver on July 23, 2018. The updated driver was version 24.20.12019.1010 (from Radeon Driver Package 18.7.1). I rolled it back to the version that was previously installed, 21.19.407.0, and that resolved the problem. I then rolled it forward to 24.20.11016.4 (from Radeon Driver Package 18.5.1) and I still don't have the problem. Yay!
    Here is another report of issues with a Radeon 5470 and a driver solving it: https://forum.freecadweb.org/viewtopic. ... 44#p264835

    A user from the german forum has successfully installed the current driver version 18.12.2 including. Relive für his Radeon R9 380.

    Radeon Vega 64 is said to be working with driver version 18.50.11.01-190109a-337968E-RadeonSoftwareAdrenalin2019. See https://forum.freecadweb.org/viewtopic. ... 40#p281540

  • MacOS: freezing for about a minute on MacOS Mojave (10.14)

    Opening a system dialog on these systems can take extremely long.
    Workaround: start FreeCAD from a console or batch file.

    See https://forum.freecadweb.org/viewtopic.php?f=4&t=31343 and https://forum.freecadweb.org/viewtopic. ... 05#p329405 for details.