Thank you for the quick feedback.
I tried that, but without success:
$ mv .cache/font-manager .tmp-font-manager
$ 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
I never started font-manager successfully on that machine. The error occurred even immediately after installing font-manager.
Should I send the font-manager cache directory anyway?
Kind regards,
David
On 17.06.2025 2:02 PM, Boyuan Yang wrote:
X-Debbugs-CC: d.fronczek@posteo.de
在 2025/6/17 2:19, David Fronczek 写道:
Package: font-manager
Version: 0.9.4-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: d.fronczek@posteo.de
Dear Maintainer,
font-manager crashes immediately after startup. Two windows are visible for a
split-second before the crash, one of them showing a font in varios sizes. >>
Whenn executing font-manager from a terminal emulator, I can see these error >> messages:
$ font-manager
(font-manager:54421): Gtk-WARNING **: 08:09:00.992: GtkGizmo 0x55daccdb4510 >> (progress) reported min width -2, but sizes must be >= 0
(font-manager:54421): [font-manager]-WARNING **: 08:09:01.891: 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
Can you try the following steps:
1. Backup your ~/.cache/font-manager/ directory.
2. Remove your ~/.cache/font-manager/ directory completely.
3. Reboot and restart font-manager tool to see if anything changes.
If font-manager could be launched successfully with the 3 steps above,
that means your cached database has been damaged. It could be due to unsafe system reboots while the font-manager is opened, or that your hard disk is failing.
In that case, could you send me your old ~/.cache/font-manager/ directory?
I can hand that to font-manager upstream and let them know that a broken sqlite database could prevent font-manager from launching without failsafe. Or you could make the bug report upstream by yourself.
Thanks,
Boyuan Yang
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)