Segfault when Inkscape is called with -o from command line

Summary:

If you call Inkscape in the command line with -o followed by a filename, it crashes

Steps to reproduce:

• inkscape -o a.svg

What happened?

Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at https://inkscape.org/report
with a detailed description of the steps leading to the crash, so we can fix it.
** Message: 03:15:12.932: Error: Inkscape encountered an internal error and will close now.

My shell then informs me:

fish: Job 1, 'inkscape -o a.svg' terminated by signal SIGSEGV (Address boundary error)

What should have happened?

Either an error about incorrect usage or performing the output.

Version info

Inkscape 1.2.2 (b0a8486541, 2022-12-01)