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


My desktop environment is X11/lightdm/Xfce4, but I can test others, should this
be helpful.

在 2025/6/17 2:19, David Fronczek 写道:

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

Thank you for the quick feedback.

I tried that, but without success:

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

Hi,

在 2025/6/17 8:52, David Fronczek 写道:

Just to rule out other possibilities, can you try to create
a *new* user and launch the font-manager tool right away
after the first new user login?

If you have time, you may also try to install a new Debian OS
with virtual machine and try again.

I cannot reproduce your issue anywhere, so we must rule
out the possibility of issues on your specific machine first.

Thanks,
Boyuan

Adjusting bug severity to minor as requested.
The bug seems to have been caused by a local cache file corruption instead of generic issues.

Thanks,
Boyuan Yang

在 2025/6/17 10:01, David Fronczek 写道:

Control: tags -1 +wontfix

As described in the upstream issue, the upstream developer is not convinced that
an elegant recovery from a broken database should be necessary. Instead, the program
should fail hard and fast when such unexpected condition occurs. Thus marking this bug
report as "wontfix".

Thanks,
Boyuan Yang
special circumstances and probably noone else is affected by it...