wxGTK:


/var/tmp/paludis/build/x11-libs-wxGTK-3.2.4/work/wxWidgets-3.2.4/configure --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --prefix=/usr/x86_64-pc-linux-gnu --bindir=/usr/x86_64-pc-linux-gnu/bin --sbindir=/usr/x86_64-pc-linux-gnu/bin --libdir=/usr/x86_64-pc-linux-gnu/lib --datadir=/usr/share --datarootdir=/usr/share --infodir=/usr/share/info --mandir=/usr/share/man --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking PKG_CONFIG=/usr/x86_64-pc-linux-gnu/bin/x86_64-pc-linux-gnu-pkg-config --disable-gtktest --enable-compat28 --enable-controls --enable-graphics_ctx --enable-gui --enable-intl --enable-ipv6 --enable-shared --enable-threads --enable-unicode --enable-precomp-headers --disable-spellcheck --disable-webviewedge --with-expat --with-gtk=3 --with-gtkprint --with-libjpeg=sys --with-liblzma --with-libpng=sys --with-libxpm=sys --with-libiconv --with-nanosvg --with-opengl --with-regex=sys --with-zlib=sys --without-gnomevfs --enable-webrequest --enable-mediactrl --disable-joystick --disable-secretstore --enable-webview --enable-webviewwebkit --disable-glcanvasegl --without-libnotify --with-sdl --with-libtiff=sys


Configured wxWidgets 3.2.4 for `x86_64-pc-linux-gnu'

  Which GUI toolkit should wxWidgets use?                 GTK+ 3 with support for GTK+ printing
  Should wxWidgets be compiled into single library?       no
  Should wxWidgets be linked as a shared library?         yes
  Should wxWidgets support Unicode?                       yes (using wchar_t)
  What level of wxWidgets compatibility should be enabled?
                                       wxWidgets 2.8      yes
                                       wxWidgets 3.0      yes
  Which libraries should wxWidgets use?
                                       STL                no
                                       jpeg               sys
                                       png                sys
                                       regex              sys
                                       tiff               sys
                                       lzma               sys
                                       zlib               sys
                                       expat              sys
                                       libmspack          no
                                       sdl                yes

Hugin:

cmake -DCMAKE_BUILD_TYPE:STRING=None -DCMAKE_C_FLAGS:STRING=-march=native -O2 -pipe -DCMAKE_CXX_FLAGS:STRING=-march=native -O2 -pipe -DCMAKE_AR:PATH=x86_64-pc-linux-gnu-ar -DCMAKE_RANLIB:PATH=x86_64-pc-linux-gnu-ranlib -DCMAKE_NM:PATH=x86_64-pc-linux-gnu-nm -DCMAKE_C_COMPILER:PATH=x86_64-pc-linux-gnu-cc -DCMAKE_CXX_COMPILER:PATH=x86_64-pc-linux-gnu-c++ -DCMAKE_INSTALL_PREFIX:PATH=/usr/x86_64-pc-linux-gnu -DCMAKE_FIND_ROOT_PATH:PATH=/usr/x86_64-pc-linux-gnu -DCMAKE_FIND_ROOT_PATH_MODE_PROGRAM:STRING=NEVER -DCMAKE_SYSTEM_PREFIX_PATH:PATH=/usr/x86_64-pc-linux-gnu -DCMAKE_INSTALL_LIBDIR:STRING=lib -DCMAKE_INSTALL_DATAROOTDIR:PATH=/usr/share/ -DBUILD_WITH_EPOXY:BOOL=TRUE -DCMAKE_EXE_LINKER_FLAGS:STRING=-lpthread -DDISABLE_DPKG:BOOL=TRUE -DHUGIN_SHARED:BOOL=TRUE -DOPENEXR_INCLUDE_DIR:PATH=/usr/x86_64-pc-linux-gnu/include/OpenEXR -DUNIX_SELF_CONTAINED_BUNDLE:BOOL=FALSE -DUSE_GDKBACKEND_X11:BOOL=FALSE -DBUILD_HSI:BOOL=FALSE -DCMAKE_DISABLE_FIND_PACKAGE_OpenMP:BOOL=FALSE -DENABLE_LAPACK:BOOL=FALSE /var/tmp/paludis/build/media-gfx-hugin-2023.0.0/work/hugin-2023.0.0

I also had a look at the Fedora spec files, we're pretty close here already and I played around with some options  without any difference.

What however did make a difference is downgrading to wxGTK 3.2.1 compiled with the exact same options with which hugin doesn't hit the problems on start. Any other of our packages using wxGTK 3.2.4 however do not run into any problems. The problem starts in combination with wxGTK >= 3.2.2 for me.

After some further things tried I could now nail it down to -DCMAKE_BUILD_TYPE, by default we pass -DCMAKE_BUILD_TYPE:STRING=None which works fine for hugin with wxGTK 3.2.1 but with >= 3.2.2 hugin appears to have problems with it and needs to be compiled with -DCMAKE_BUILD_TYPE:STRING=Release instead to not run into this issue, which may probably also be the reason why you didn't run into / coudln't reproduce it.