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

Settings crash after setting custom system font #343

Closed
nathan-contino opened this issue Oct 31, 2023 · 1 comment · Fixed by #344
Closed

Settings crash after setting custom system font #343

nathan-contino opened this issue Oct 31, 2023 · 1 comment · Fixed by #344
Assignees
Labels
bug Something isn't working

Comments

@nathan-contino
Copy link
Contributor

nathan-contino commented Oct 31, 2023

Expected Behavior

Expected Hamburger menu > Settings to open the settings

Current Behavior

Settings crashes, so I can't change any settings any more! Doesn't work on reload, either.
Oddly, the custom font I picked (SF Mono) does load correctly.

Screenshot 2023-10-31 at 12 46 39

Steps to Reproduce

  1. Open the Settings menu.
  2. In General, pick System font
  3. Choose a font from the macOS Fonts folder.
  4. Observe the app crash.
  5. Try to open the settings menu again. Observe the app crash.
  6. Try to reload the settings menu. Still an app crash.

Context

I like a monospace font for my music player, so I tried picking SF Mono. It does look pretty nice, but I think I'd prefer being able to use my settings menu.

Your Environment

  • Application version (e.g. v0.1.0) : 0.5.0
  • Operating System and version (e.g. Windows 10) : macOS Sonoma
  • Server and version (e.g. Navidrome v0.48.0) : Jellyfin 10.8.9
  • Node version (if developing locally) : not developing locally
@nathan-contino nathan-contino added the bug Something isn't working label Oct 31, 2023
@nathan-contino nathan-contino changed the title Settings crash after setting custom font Settings crash after setting custom system font Oct 31, 2023
@jeffvli jeffvli self-assigned this Oct 31, 2023
@jeffvli
Copy link
Owner

jeffvli commented Oct 31, 2023

Can you open the console from the Open browser devtools in the app menu and check to see if it says exactly where the error is coming from?

I can't reproduce this on my side (I only use Windows).

Also, resetting the settings to default (or deleting the store_settings key from local storage and restarting) may fix it temporarily until a permanent fix can be put in place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants