Rudolf is reporting a segfault on 2020.3 during startup, and the backtrace:
0 0x0000000000a93d05 in osg::ref_ptr<osg::graphicscontext>::operator->() const (this=<optimized out="">) at /usr/local/include/osg/ref_ptr:91</optimized></osg::graphicscontext>
1 guiInit() () at /home/domokos/FlightGear/src/flightgear/src/GUI/gui.cxx:186
2 0x0000000001031d75 in fgIdleFunction() () at /home/domokos/FlightGear/src/flightgear/src/Main/main.cxx:305
3 0x0000000000f91329 in fgOSMainLoop() () at /home/domokos/FlightGear/src/flightgear/src/Viewer/fg_os_osgviewer.cxx:312
4 0x0000000001030e36 in fgMainInit(int, char**) (argc=<optimized out="">, argv=<optimized out="">) at /home/domokos/FlightGear/src/flightgear/src/Main/main.cxx:758</optimized></optimized>
5 0x00000000008d5b58 in main(int, char**) (argc=2, argv=0x7fff1e10f578) at /home/domokos/FlightGear/src/flightgear/src/Main/bootstrap.cxx:314
Apparently this only happens with anti aliasing, right after the main FG window opens up. Without anti-aliasing, FlightGear runs fine.
Can you ask the graphics card/driver in use? If it doesn't happen for everybody, my guess is we are asking for an AA setting his GPU/driver does not support.
It's a AMD Rv620 card.
Driver: kernel-firmware-amdgpu version: 20201005-3.1
Last edit: legoboyvdlp 2020-10-20
This seems to be a driver issue. Some AMD drivers are known to crash with MSAA. Does this happen with other apps as well? Is this the 1st time you used AA with FG? If not, did it work before?
Last edit: Fernando García Liñán 2020-10-22
@legoboyvdlp, got any more info from Rudolf, or can we close this one?