Corrupted local database may trigger crash on startup (downstream bug report) #450
Description
Describe the bug
A downstream distro user reported the following bug report:
On their machine, the following error message would occur:
$ font-manager
(font-manager:84688): Gtk-WARNING **: 14:48:38.294: GtkGizmo 0x56343141bfa0 (progress) reported min width -2, but sizes must be >= 0
(font-manager:84688): [font-manager]-WARNING **: 14:48:39.154: SQLite Result Code 0 : not an error
**
[font-manager]:ERROR:../lib/common/font-manager-database.c:631:update_available_fonts: assertion failed: (sqlite3_step_succeeded(db, SQLITE_DONE))
Bail out! [font-manager]:ERROR:../lib/common/font-manager-database.c:631:update_available_fonts: assertion failed: (sqlite3_step_succeeded(db, SQLITE_DONE))
Aborted
To Reproduce
Please refer to the original downstream bug report.
Expected behavior
The App does not crash on startup.
Screenshots
Please refer to the original downstream bug report.
System Information
- OS: Debian 13
- Desktop Environment XFCE 4
- Font Manager version: 0.9.4-2
- Font Manager installation method: Debian APT (official repo)
Additional context
The issue disappears in a newly-created user. As a result, it is suspected that a corrupted local
database in ~/.cache/ may have caused the issue. I believe the font-manager App itself
should not crash even if the sqlite database is broken.