Environment
- Albert version: 34.0.10
- Qt version: 6.10.1
- OS: Manjaro Linux (kernel 5.10.248-1-MANJARO)
- DE/WM: AwesomeWM
- Session: X11
- Package source: Official repo (
home:manuelschneid3r/Arch)
Bug
Albert segfaults immediately on launch. Clean config (no ~/.config/albert) still crashes.
Log output
[crit:albert] Albert has not been terminated properly. Please check your logs and report an issue.
[info:albert] Searching native plugins in /usr/lib/albert
[warn:qt.core.qobject.connect] QObject::connect(albert::PluginInstance, QEventLoop): invalid nullptr parameter
fish: Job 1, 'albert' terminated by signal SIGSEGV (Address boundary error)
Debugging
Narrowed down the crash to widgetsboxmodel.so:
- No plugins (
-p /empty/dir) → no crash, exits with "Could not load any frontend"
- Only
widgetsboxmodel.so → segfault with the same QObject::connect nullptr error
- Only
application.so → no crash, exits with "no frontend"
So the crash is triggered specifically when loading widgetsboxmodel.so on Qt 6.10.1.
Steps to reproduce
- Install Albert 34.0.10 on Arch/Manjaro with Qt 6.10.1
- Remove
~/.config/albert for clean state
- Run
albert
- Immediate SIGSEGV
Expected behavior
Albert should launch normally.
Environment
home:manuelschneid3r/Arch)Bug
Albert segfaults immediately on launch. Clean config (no
~/.config/albert) still crashes.Log output
Debugging
Narrowed down the crash to
widgetsboxmodel.so:-p /empty/dir) → no crash, exits with "Could not load any frontend"widgetsboxmodel.so→ segfault with the sameQObject::connect nullptrerrorapplication.so→ no crash, exits with "no frontend"So the crash is triggered specifically when loading
widgetsboxmodel.soon Qt 6.10.1.Steps to reproduce
~/.config/albertfor clean statealbertExpected behavior
Albert should launch normally.