search

flathub / io.github.dweymouth.supersonic

https://flathub.org/apps/details/io.github.dweymouth.supersonic
1 stars 2 forks source link

OS Font lookup does not work in Flatpak (at least on some distros) #104

Open dweymouth opened 4 days ago

dweymouth commented 4 days ago

See https://github.com/dweymouth/supersonic/issues/500#issuecomment-2501575545 for more info.

Flatpak sandboxing is preventing Supersonic from being able to lookup fonts from the OS to display Japanese characters or other characters that are not in the bundled font that comes with the app. It may be as simple as adding an additional permission to the Flatpak manifest but I have no idea.

anarcat commented 4 days ago

that's strange: i don't have that problem and also often have weird characters in my filenames (my native language is french) so I'm pretty sure i would have noticed.

@thecivilizedgamer could you expand on your desktop environment here? do you have xdg-desktop-portal-gtk installed?

similar issues https://github.com/flatpak/flatpak/issues/5389 https://github.com/flatpak/flatpak/issues/4571

the TLDR is that this should work, your system fonts should be available inside the flatpak.

thecivilizedgamer commented 4 days ago

that's strange: i don't have that problem and also often have weird characters in my filenames (my native language is french) so I'm pretty sure i would have noticed.

@thecivilizedgamer could you expand on your desktop environment here? do you have xdg-desktop-portal-gtk installed?

similar issues flatpak/flatpak#5389 flatpak/flatpak#4571

the TLDR is that this should work, your system fonts should be available inside the flatpak.

Yep, I do have xdg-desktop-portal-gtk installed. I'm running Xubuntu 24.04.1 LTS, and it's a pretty fresh install - I've only installed a few applications, and haven't really done anything to the OS. I can provide additional details if you want.

As a side note, I noticed that the Flatpak version was prompting me for the password for my Nextcloud Music server on every launch, but the natively installed version does not seem to have that problem. Maybe that's tangentially related, I can file a separate issue for it if you want.