Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash with GNOME 40 #212

Closed
raphielscape opened this issue Apr 8, 2021 · 4 comments
Closed

Crash with GNOME 40 #212

raphielscape opened this issue Apr 8, 2021 · 4 comments

Comments

@raphielscape
Copy link

Describe the bug
font-manager crash with GNOME 40

To Reproduce
Steps to reproduce the behavior:

  1. Upgrade to GNOME 40
  2. Try opening font-manager
  3. font-manager terminated with SIGTRAP

Stacktrace

(font-manager:54301): [font-manager]-CRITICAL **: 15:15:29.390: ArchiveManager.vala:61: 1 : Error spawning command line “dbus-launch --autolaunch=3898d9a3b94940fd91df780fef71956e --binary-syntax --close-stderr”: Child process exited with code 1

(font-manager:54301): GLib-GIO-ERROR **: 15:15:29.437: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

System Information

  • OS: Arch Linux
  • Desktop Environment: GNOME 40.0.0
  • Font Manager version: 0.8.5
  • Font Manager installation method: AUR
@PF4Public
Copy link
Contributor

Did it produce any interesting output in dmesg?

@JerryCasiano
Copy link
Contributor

@raphielscape

I think I'm going to need your help on this one, I don't plan on updating my system just yet...

If you could build from the latest commit and verify it fixes the crash I can tag a new release.

@raphielscape
Copy link
Author

@raphielscape

I think I'm going to need your help on this one, I don't plan on updating my system just yet...

If you could build from the latest commit and verify it fixes the crash I can tag a new release.

Can confirm that latest commit fixed the crash

@JerryCasiano
Copy link
Contributor

I've tagged a new release. If possible, please flag the package as out of date so the maintainer gets notified.

Thanks for reporting this and verifying the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants