font-manager crashed with signal 5

[Alex Murray]

font-manager uses old gsettings schema location for antialiasing settings etc which do not exist in impish anymore and so crashes at startup:

(font-manager:227159): GLib-GIO-ERROR **: 16:12:07.589: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: font-manager 0.8.4-1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 26 16:12:07 2021
ExecutablePath: /usr/bin/font-manager
InstallationDate: Installed on 2020-10-11 (287 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
ProcCmdline: font-manager
Signal: 5
SourcePackage: font-manager
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_enum () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
 font_manager_desktop_preferences_construct ()
 font_manager_initialize_preference_pane ()
 font_manager_main_window_construct ()
Title: font-manager crashed with signal 5
UpgradeStatus: Upgraded to impish on 2021-07-24 (1 days ago)
UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sbuild sudo
separator:

[Alex Murray (alexmurray)]

This was tracked upstream in https://github.com/FontManager/font-manager/issues/212

[Jerry Casiano (jerrycasiano)]

@alexmurray

You can sidestep this issue by using the PPA, which is always up to date.

[Alex Murray (alexmurray)]

@jerrycasiano Which PPA would that be?

[Jerry Casiano (jerrycasiano)]

https://code.launchpad.net/~font-manager/+archive/ubuntu/staging

https://github.com/FontManager/font-manager#ubuntu-personal-package-archive

Not meant to discourage anyone from reporting bugs which affect all Ubuntu users, that's definitely a good thing to do. Just wanted to make sure you were aware of the option.

Also make sure to purge any existing packages, manager, viewer, common, extensions, etc. before switching between the two. Though I think they're compatible at this point, better to be safe.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

I've synced the new version from Debian that fixes the issue

[Sebastien Bacher (seb128)]

https://launchpad.net/ubuntu/+source/font-manager/0.8.7-1