Overview

Starting KeePasXC on an M2 MacBook Air works, it's also possible to create a database. However, loading any database after restarting KeePassXC results in a crash (segmentation fault), even for databases that work with KeePassXC on Intel (same OS version, same KeePassXC version).

Steps to Reproduce

1. Open KeePassXC 2.7.3
2. Create a new database (use default values, enter a password).
3. Save the database.
4. Quit KeePassXC.
5. Open KeePassXC.
6. Open the newly created database.

Expected Behavior

KeePassXC should load the Database.

Actual Behavior

KeePassXC crashes with a segfault. This only happens on the M2 machine. It works fine on an Intel machine.

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [5183]

Please let me know if you need further debugging info. I'd need a pointer how to collect it, though.

Context

(Sorry for the German locale, I hope this is ok.)

KeePassXC - Version 2.7.3
Revision: d8483d3

Qt 5.15.6
Diagnosemodus ist deaktiviert.

Betriebssystem: macOS 12.6
CPU-Architektur: arm64
Kernel: darwin 21.6.0

Aktivierte Erweiterungen:

• Auto-Type
• Browser-Integration
• SSH-Agent
• KeeShare
• YubiKey
• Schnelle Entsperrung

Kryptographische Bibliotheken:

• Botan 2.19.2

Operating System: macOS
Desktop Env:
Windowing System: