Control: tags -1 upstream confirmed Control: tags -1 forwarded https://github.com/FreeCAD/FreeCAD/issues/8206
On Thu, 02 Feb 2023 14:17:01 +0100 Corcier <corc...@laposte.net> wrote: > Dear all, > > I have had the same issue after the last update. > I managed to corner the problem finding that the *.desktop file call > freecad with the --single-instance option and freecad does not > recognise it. This option is added by the run_single-instance patch > (see 1:). The issue arises because the new 0.20.2 does not seem to > recognise the option anymore. > The snap install of the same version does recognise the option so I > should now compare the two sources (debianised sources and upstream) > but run out of time. Anybody interested in investigating about this > issue is welcome :) Thanks for the pointer! I think I've got more information: freecad --help tells me that --single-instance should still be supported… Might be a red herring: running freecad --single-instance from a console, gives me a SEGV: ~/workspace/deb/packages/freecad/freecad$ freecad --single-instance unknown option --single-instance usage: freecad [option] ... [-c cmd | -m mod | file | -] [arg] ... Try `python -h' for more information. Program received signal SIGSEGV, Segmentation fault. #0 /lib/x86_64-linux-gnu/libc.so.6(+0x3bf90) [0x7f500485af90] #1 /lib/x86_64-linux-gnu/libc.so.6(+0x159139) [0x7f5004978139] #2 /lib/x86_64-linux-gnu/libpython3.11.so.1.0(+0x2d0223) [0x7f50062d0223] #3 /lib/x86_64-linux-gnu/libpython3.11.so.1.0(Py_EncodeLocale+0x4e) [0x7f50062d090e] #4 freecad(+0x5034) [0x55c166ed1034] #5 /lib/x86_64-linux-gnu/libc.so.6(+0x2718a) [0x7f500484618a] #6 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f5004846245] #7 freecad(+0x5ad1) [0x55c166ed1ad1] This lead me to: https://github.com/FreeCAD/FreeCAD/issues/8206 And it seems that there is a workaround: > fwiw, both seem to work when an extra - is used, i.e. freecad - --dump-config > and freecad - --single-instance -- tobi
