Control: tags -1 +wontfix On Tue, 17 Jun 2025 15:20:59 -0400 Boyuan Yang <byang@debian.org> wrote: > Control: severity -1 minor > > Adjusting bug severity to minor as requested. > The bug seems to have been caused by a local cache file corruption instead of generic issues. 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 > 在 2025/6/17 10:01, David Fronczek 写道: > > Hi, > > > > it turns out, you were right. I tried that and can report the following: > > As a completely new user "test", font-manager works as expected. 👍 > > > > On a different machine (also Debian Trixie, similar set of applications installed), font-manager also works as expected. 👍 > > > > The warning "reported min width -2, but sizes must be >= 0" remains in both cases, so it's probably irrelevant regarding the crash. > > > > For the time being I can run font-manager with gksu as the "test" user as a workaround. Would you downgrade the bug to "minor", since the crash seems to occur only under special circumstances and probably noone else is affected by it... > > > > Regards, > > David > > > > > > On 17.06.2025 3:18 PM, Boyuan Yang wrote: > >> Hi, > >> > >> 在 2025/6/17 8:52, David Fronczek 写道: > >>> 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? > >> > >> 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 > >> > >> > >>> On 17.06.2025 2:02 PM, Boyuan Yang wrote: > >>>> X-Debbugs-CC: d.fronczek@posteo.de
Attachment:
signature.asc
Description: This is a digitally signed message part