Fonts - Revision history

Blastboom Strice: Undo revision 31995 by Blastboom Strice (talk) - I decided to put it under the flatpak page instead

2026-05-21T12:35:26Z

Undo revision 31995 by Blastboom Strice (talk) - I decided to put it under the flatpak page instead

← Older revision		Revision as of 12:35, 21 May 2026
Line 353:		Line 353:

	If everything is mounted properly, but you still do not see fonts in flatpak app - force font cache recreation inside flatpak container: <code>flatpak run --command=fc-cache <application id> -f -v</code>		If everything is mounted properly, but you still do not see fonts in flatpak app - force font cache recreation inside flatpak container: <code>flatpak run --command=fc-cache <application id> -f -v</code>

	~~==== Solution 4: Uninstall the application having fonts issues and wipe its data ====~~
	~~{{Warning\|This involves deleting application data of flatpak applications, make sure to keep backed up any flatpak application data you want before proceeding.}}~~
	~~Sometimes, flatpak applications may glitch (like Flatseal<ref>https://github.com/tchx84/Flatseal/issues/501</ref>) and wiping their data may solve the issue. To do so, you have two options.~~

	~~===== Option 1: Delete application and its data in a single command =====~~
	This is useful if you have installed the flatpak application '''imperatively'''. Use the <code>--delete-data</code> flag when uninstalling the offending application, (like <code>flatpak uninstall <application> --delete-data</code> ). Then re-install the offending application (like <code>flatpak install <application></code> ).

	~~===== Option 2: Delete application and then delete its data =====~~
	This is useful if you have set up flatpak '''declaratively'''<ref>[[Flatpak#Declarative]]</ref>. First remove the application from your configuration and rebuild. Then run <code>flatpak uninstall --unused --delete-data</code> to both delete '''all''' leftover applications and wipe the data of anything previously deleted. This will ask you to delete the data of each application individually, delete only the data of the offending application. Then re-add the offending application in your configuration and rebuild.

	=== Noto Color Emoji doesn't render on Firefox ===		=== Noto Color Emoji doesn't render on Firefox ===

Blastboom Strice: Add /Solution 4: Uninstall the application having fonts issues and wipe its data/ section

2026-05-21T12:21:50Z

Add Solution 4: Uninstall the application having fonts issues and wipe its data: section

← Older revision		Revision as of 12:21, 21 May 2026
Line 353:		Line 353:

	If everything is mounted properly, but you still do not see fonts in flatpak app - force font cache recreation inside flatpak container: <code>flatpak run --command=fc-cache <application id> -f -v</code>		If everything is mounted properly, but you still do not see fonts in flatpak app - force font cache recreation inside flatpak container: <code>flatpak run --command=fc-cache <application id> -f -v</code>

			==== Solution 4: Uninstall the application having fonts issues and wipe its data ====
			{{Warning\|This involves deleting application data of flatpak applications, make sure to keep backed up any flatpak application data you want before proceeding.}}
			Sometimes, flatpak applications may glitch (like Flatseal<ref>https://github.com/tchx84/Flatseal/issues/501</ref>) and wiping their data may solve the issue. To do so, you have two options.

			===== Option 1: Delete application and its data in a single command =====
			This is useful if you have installed the flatpak application '''imperatively'''. Use the <code>--delete-data</code> flag when uninstalling the offending application, (like <code>flatpak uninstall <application> --delete-data</code> ). Then re-install the offending application (like <code>flatpak install <application></code> ).

			===== Option 2: Delete application and then delete its data =====
			This is useful if you have set up flatpak '''declaratively'''<ref>[[Flatpak#Declarative]]</ref>. First remove the application from your configuration and rebuild. Then run <code>flatpak uninstall --unused --delete-data</code> to both delete '''all''' leftover applications and wipe the data of anything previously deleted. This will ask you to delete the data of each application individually, delete only the data of the offending application. Then re-add the offending application in your configuration and rebuild.

	=== Noto Color Emoji doesn't render on Firefox ===		=== Noto Color Emoji doesn't render on Firefox ===

InOnesGraveDed: Fixed broken link.

2026-03-04T08:39:45Z

Fixed broken link.

← Older revision		Revision as of 08:39, 4 March 2026
Line 19:		Line 19:
	dina-font		dina-font
	proggyfonts		proggyfonts
	];\|name=/etc/nixos/configuration.nix\|lang=nix}}{{Note\|Be aware that sometimes font names and packages name differ and there is no universal convention in NixOS. </br>See: [https://discourse.nixos.org/t/guidelines-on-packaging-fonts/7683/2~~\|~~ Guidelines for font packaging]}}		];\|name=/etc/nixos/configuration.nix\|lang=nix}}{{Note\|Be aware that sometimes font names and packages name differ and there is no universal convention in NixOS. </br>See: [https://discourse.nixos.org/t/guidelines-on-packaging-fonts/7683/2 Guidelines for font packaging]}}

	=== Shorthands for fonts ===		=== Shorthands for fonts ===

Voidcoefficient: 'ubuntu_font_family' has been renamed to/replaced by 'ubuntu-classic'

2026-03-02T18:22:05Z

'ubuntu_font_family' has been renamed to/replaced by 'ubuntu-classic'

← Older revision		Revision as of 18:22, 2 March 2026
Line 160:		Line 160:
	enableDefaultPackages = true;		enableDefaultPackages = true;
	packages = with pkgs; [		packages = with pkgs; [
	~~ubuntu_font_family~~		ubuntu-classic
	liberation_ttf		liberation_ttf
	# Persian Font		# Persian Font

Zetsu: fix link

2026-02-02T11:53:20Z

fix link

← Older revision		Revision as of 11:53, 2 February 2026
Line 123:		Line 123:
	=== Install fonts in nix-shells ===		=== Install fonts in nix-shells ===

	<code>fonts</code> is not available as set-valued option in <code>mkshell</code> (gives you an error because it tries to coerce an attribute set into a string). Instead, insert the following:<ref>~~ihttps~~://programming.dev/post/32484220</ref>		<code>fonts</code> is not available as set-valued option in <code>mkshell</code> (gives you an error because it tries to coerce an attribute set into a string). Instead, insert the following:<ref>https://programming.dev/post/32484220</ref>

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">

Flukx: copy from nixos.wiki: how to in nix-shell

2026-01-24T19:36:15Z

copy from nixos.wiki: how to in nix-shell

@@ Line 119: / Line 119: @@
 fc-list -v | grep -i source
 </syntaxhighlight>
 == Configuring fonts ==

Geobomatic: Add instructions that would have helped me :)

2026-01-14T09:25:56Z

Add instructions that would have helped me :)

← Older revision		Revision as of 09:25, 14 January 2026
Line 67:		Line 67:
	{		{
	fonts.packages = builtins.filter lib.attrsets.isDerivation (builtins.attrValues pkgs.nerd-fonts);		fonts.packages = builtins.filter lib.attrsets.isDerivation (builtins.attrValues pkgs.nerd-fonts);
			}

			# or if you already have fonts.packages set

			{
			fonts.packages = [
			# ... some fonts
			]
			++ builtins.filter lib.attrsets.isDerivation (builtins.attrValues pkgs.nerd-fonts);
	}		}
	</nowiki>\|name=/etc/nixos/configuration.nix\|lang=nix}}		</nowiki>\|name=/etc/nixos/configuration.nix\|lang=nix}}

Alliumm: corrected the command for running fc-cache in a flatpak app

2025-12-19T23:00:28Z

corrected the command for running fc-cache in a flatpak app

← Older revision		Revision as of 23:00, 19 December 2025
Line 314:		Line 314:
	You can make sure that font directory is bind-mounted properly inside flatpak container by running <code>flatpak enter <instance> findmnt \| grep /run/host/fonts</code>, or by running <code>flatpak enter <instance> ls -alh /run/host/fonts</code> and compare it to <code>ls -alh /usr/share/fonts</code>.		You can make sure that font directory is bind-mounted properly inside flatpak container by running <code>flatpak enter <instance> findmnt \| grep /run/host/fonts</code>, or by running <code>flatpak enter <instance> ls -alh /run/host/fonts</code> and compare it to <code>ls -alh /usr/share/fonts</code>.

	If everything is mounted properly, but you still do not see fonts in flatpak app - force font cache recreation inside flatpak container: <code>flatpak ~~enter <instance>~~ fc-cache -f -v</code>		If everything is mounted properly, but you still do not see fonts in flatpak app - force font cache recreation inside flatpak container: <code>flatpak run --command=fc-cache <application id> -f -v</code>

	=== Noto Color Emoji doesn't render on Firefox ===		=== Noto Color Emoji doesn't render on Firefox ===

Sirphobos: minor formatting fix

2025-12-18T19:03:18Z

minor formatting fix

← Older revision		Revision as of 19:03, 18 December 2025
Line 314:		Line 314:
	You can make sure that font directory is bind-mounted properly inside flatpak container by running <code>flatpak enter <instance> findmnt \| grep /run/host/fonts</code>, or by running <code>flatpak enter <instance> ls -alh /run/host/fonts</code> and compare it to <code>ls -alh /usr/share/fonts</code>.		You can make sure that font directory is bind-mounted properly inside flatpak container by running <code>flatpak enter <instance> findmnt \| grep /run/host/fonts</code>, or by running <code>flatpak enter <instance> ls -alh /run/host/fonts</code> and compare it to <code>ls -alh /usr/share/fonts</code>.

	If everything is mounted properly, but you still do not see fonts in flatpak app - force font cache recreation inside flatpak container: <code>flatpak enter <instance> fc-cache -~~</code><code>~~f -v</code>		If everything is mounted properly, but you still do not see fonts in flatpak app - force font cache recreation inside flatpak container: <code>flatpak enter <instance> fc-cache -f -v</code>

	=== Noto Color Emoji doesn't render on Firefox ===		=== Noto Color Emoji doesn't render on Firefox ===

Sirphobos: /* Solution 3: Configure bindfs for fonts/cursors/icons support */ add info about font cache recreation inside flatpak container

2025-12-18T19:02:17Z

Solution 3: Configure bindfs for fonts/cursors/icons support: add info about font cache recreation inside flatpak container

← Older revision		Revision as of 19:02, 18 December 2025
Line 310:		Line 310:
	noto-fonts-cjk		noto-fonts-cjk
	];		];
	</syntaxhighlight>		</syntaxhighlight>Note that font cache inside flatpak container may not be recreated after changes to fonts in <code>/usr/share/fonts</code>, because font cache seem to be relying on file timestamps that are missing in <code>/nix/store</code>.

			You can make sure that font directory is bind-mounted properly inside flatpak container by running <code>flatpak enter <instance> findmnt \| grep /run/host/fonts</code>, or by running <code>flatpak enter <instance> ls -alh /run/host/fonts</code> and compare it to <code>ls -alh /usr/share/fonts</code>.

			If everything is mounted properly, but you still do not see fonts in flatpak app - force font cache recreation inside flatpak container: <code>flatpak enter <instance> fc-cache -</code><code>f -v</code>

	=== Noto Color Emoji doesn't render on Firefox ===		=== Noto Color Emoji doesn't render on Firefox ===