Obsolete
Status Update
No update yet.
Comments
da...@gmail.com
Chrome's secure shell app lets you choose font installed on OS. But on ChromeOS you are limited to the fonts that come with it and there is not an option to install new ones that you may need. My ssh use case is probably one of many where users would like to install additional fonts.
an...@gmail.com
I use crosh/crouton to SSH to my linux box in a tab and it would be cool if it would support my powerline fonts for vim and zsh
ka...@chromium.org
[Empty comment from Monorail migration]
tr...@gmail.com
You can install fonts without modifying the system, as long as you have access to a shell.
Chromium/Chrome uses fontconfig, and searches for configuration files at ~/.fonts.conf or ~/.fonts.conf.d by default.
You can enable the standard ~/.fonts directory by saving the following as ~/.fonts.conf:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<dir>~/.fonts</dir>
</fontconfig>
(or download the attachment and cp ~/Downloads/fonts.conf ~/.fonts.conf)
You can test this with the Powerline symbols font:
# mkdir -p ~/.fonts
# wget -P ~/.fontshttps://raw.github.com/Lokaltog/powerline/develop/font/PowerlineSymbols.otf
# fc -list | grep PowerlineSymbols
The fc-list command should show:
PowerlineSymbols:style=Medium
Chromium/Chrome uses fontconfig, and searches for configuration files at ~/.fonts.conf or ~/.fonts.conf.d by default.
You can enable the standard ~/.fonts directory by saving the following as ~/.fonts.conf:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<dir>~/.fonts</dir>
</fontconfig>
(or download the attachment and cp ~/Downloads/fonts.conf ~/.fonts.conf)
You can test this with the Powerline symbols font:
# mkdir -p ~/.fonts
# wget -P ~/.fonts
# fc -list | grep PowerlineSymbols
The fc-list command should show:
PowerlineSymbols:style=Medium
mi...@gmail.com
@triskelios
This doesn't work. You can add your font into fontconfig's system but chrome doesn't seems to recognize that, and you cannot use that font anywhere.
This doesn't work. You can add your font into fontconfig's system but chrome doesn't seems to recognize that, and you cannot use that font anywhere.
tr...@gmail.com
The additional fonts are visible in the Chrome browser and apps as of a recent beta update.
I'm currently running:
Google Chrome 35.0.1916.27 (Official Build 262261) beta
Platform 5712.14.0 (Official Build) beta-channel daisy_spring
I'm currently running:
Google Chrome 35.0.1916.27 (Official Build 262261) beta
Platform 5712.14.0 (Official Build) beta-channel daisy_spring
tr...@gmail.com
... and ~/.fonts.conf has stopped working with the subsequent beta channel update. It's unclear what the intended behaviour is.
tr...@gmail.com
Turns out that the initial session doesn't see the fonts, but restarting the desktop loads the additional ~/.fonts.conf and makes them visible. (chrome://inducebrowsercrashforrealz is a quick way to test this :)
mi...@gmail.com
@triskelios
Thanks for the tip, the chrome://inducebrowsercrashforrealz works for me now. It's either the ChromeOS Stable channel by the time I first replied doesn't support custom fonts, or this inducebrowsercrashforrealz is necessary.
Anyway, I'm now able to use custom fonts in my crosh now. :)
Thanks for the tip, the chrome://inducebrowsercrashforrealz works for me now. It's either the ChromeOS Stable channel by the time I first replied doesn't support custom fonts, or this inducebrowsercrashforrealz is necessary.
Anyway, I'm now able to use custom fonts in my crosh now. :)
tr...@gmail.com
~/.fonts.conf works for me on the first Chrome session now without restarting: 36.0.1985.49 (Official Build 274672) beta
tr...@gmail.com
[Comment Deleted]
tr...@gmail.com
Verified that new fonts do actually work with the first login session. Yay!
mi...@gmail.com
@triskelios
Wait, this still doesn't work!
I just found that once I reboot my chromebook, all the fonts under ~/.fonts are ignored again! I have to do a chrome://inducebrowsercrashforrealz to force chrome reload.
I suspect that the ChromeOS will preload chrome on the login screen and at that time, the /home/chronos/user is not mounted yet! So, chrome will ignore the local fonts config and fonts, even after you login.
Wait, this still doesn't work!
I just found that once I reboot my chromebook, all the fonts under ~/.fonts are ignored again! I have to do a chrome://inducebrowsercrashforrealz to force chrome reload.
I suspect that the ChromeOS will preload chrome on the login screen and at that time, the /home/chronos/user is not mounted yet! So, chrome will ignore the local fonts config and fonts, even after you login.
mi...@gmail.com
@triskelios
OK, found a workaround for the issue above. I think this is the "real-fix" that could close this bug report now. :)
ChromeOS will not mount the /home/chronos/user before login, and will preload chrome process without our .fonts.conf. So, the right way to do this is:
1. Duplicate the ~/.fonts.conf under /home/chronos/user before mount.
2. Inside .fonts.conf, we should point to the fonts directory to /usr/local/share/fonts , which doesn't change across login/logout.
chronos@localhost ~ $ cat .fonts.conf
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<dir>/usr/local/share/fonts</dir>
</fontconfig>
mkdir -p /tmp/test/
sudo mount --bind /home/chronos/ /tmp/test/
cd /tmp/test/user
cp ~/.font.conf .
OK, found a workaround for the issue above. I think this is the "real-fix" that could close this bug report now. :)
ChromeOS will not mount the /home/chronos/user before login, and will preload chrome process without our .fonts.conf. So, the right way to do this is:
1. Duplicate the ~/.fonts.conf under /home/chronos/user before mount.
2. Inside .fonts.conf, we should point to the fonts directory to /usr/local/share/fonts , which doesn't change across login/logout.
chronos@localhost ~ $ cat .fonts.conf
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<dir>/usr/local/share/fonts</dir>
</fontconfig>
mkdir -p /tmp/test/
sudo mount --bind /home/chronos/ /tmp/test/
cd /tmp/test/user
cp ~/.font.conf .
la...@chromium.org
[Empty comment from Monorail migration]
[Deleted User] <[Deleted User]>
ab...@chromium.org
Please re-open if still see this issue.marking as WontFix now.
wb...@google.com
Just to be clear, the "as long as you have access to a shell" means that Chrome OS has to be running in Developer Mode, isn't it?
[Deleted User] <[Deleted User]>
bc...@google.com
> Please re-open if still see this issue.marking as WontFix now.
I cannot put my device in Developer Mode due to an enterprise policy.
As such I am still unable to install new fonts on it.
How do I re-open this bug?
I cannot put my device in Developer Mode due to an enterprise policy.
As such I am still unable to install new fonts on it.
How do I re-open this bug?
da...@gmail.com
My device *is* in developer mode, but these instructions no longer seem to work. In particular, it looks like fontconfig is no longer reading ~/.fonts.conf; looking in the /etc/fonts directory confirms it's only looking at the global config files.
I think I could fix this with `sudo ln -s /etc/fonts/conf.avail/50-user.conf /etc/fonts/conf.d/`q but I'd rather not turn off rootfs verification for this, especially when I'm not sure it would work.
Having a specific font is not something just power users want. This should not require developer mode and it certainly shouldn't require crazy hacks like this. But if it does, it should at least not require finding an obscure bug in the Chrome bug tracker and reading all the comments.
I think I could fix this with `sudo ln -s /etc/fonts/conf.avail/50-user.conf /etc/fonts/conf.d/`q but I'd rather not turn off rootfs verification for this, especially when I'm not sure it would work.
Having a specific font is not something just power users want. This should not require developer mode and it certainly shouldn't require crazy hacks like this. But if it does, it should at least not require finding an obscure bug in the Chrome bug tracker and reading all the comments.
dh...@google.com
Reopening as per https://crbug.com/chromium/320364#c17 because:
a) The work-around discussed in this thread doesn’t work for people like inhttps://crbug.com/chromium/320364#c20 who cannot or don’t want to able Developer Mode
b) The work-around doesn’t even work anymore since (I think) commithttps://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/670dec6538d3a1c13f4ad7701febb4c1d3c3f03a , which removed the use of user-specific fonts.
a) The work-around discussed in this thread doesn’t work for people like in
b) The work-around doesn’t even work anymore since (I think) commit
ea...@chromium.org
This has nothing to do with Blink, rerouting.
[Monorail components: -Blink>Fonts OS>Installer]
[Monorail components: -Blink>Fonts OS>Installer]
dh...@google.com
Has anybody not in Blink seen this yet?
Also, it looks like there are several font issues in OS>Installer (such ascrbug.com/899493 , which is a duplicate of this but mentions a broader use case than a handful of individual people) and it looks like most of them start in Blink>Fonts. Should there perhaps be an OS>Fonts component or something to keep Blink from having to redirect everything?
Also, it looks like there are several font issues in OS>Installer (such as
ma...@chromium.org
[Empty comment from Monorail migration]
[Monorail components: -OS>Installer OS>Systems>Settings]
[Monorail components: -OS>Installer OS>Systems>Settings]
ma...@chromium.org
[Empty comment from Monorail migration]
rw...@gmail.com
Can work around recent change with more bind mounts.
- copy local fonts to /usr/local/share/fonts
- copy /etc/fonts/local.conf to writable location
- add "<dir>/usr/local/share/fonts</dir>" to copy of local.conf
- bind mount modified local.conf over /etc/fonts/local.conf
- bind mount an empty, writable directory to /usr/share/cache/fontconfig
- run "fc-cache -f -v"
- trigger a crash/restart with chrome://inducebrowsercrashforrealz
Pretty ugly but it worked for me. I don't mind the Noto Sans Mono change but prefer Roboto Mono and DejaVu Sans Mono, both of which I believe were previously included by default. Was just caught a little off guard when I rebooted and got a new font in my terminal.
I will also note that Cousine is an alias for "monospace" and it doesn't appear that it is actually monospaced. Or rather, it appears that the Cousine .ttf file may actually not be Cousine Regular? Mysteries!
- copy local fonts to /usr/local/share/fonts
- copy /etc/fonts/local.conf to writable location
- add "<dir>/usr/local/share/fonts</dir>" to copy of local.conf
- bind mount modified local.conf over /etc/fonts/local.conf
- bind mount an empty, writable directory to /usr/share/cache/fontconfig
- run "fc-cache -f -v"
- trigger a crash/restart with chrome://inducebrowsercrashforrealz
Pretty ugly but it worked for me. I don't mind the Noto Sans Mono change but prefer Roboto Mono and DejaVu Sans Mono, both of which I believe were previously included by default. Was just caught a little off guard when I rebooted and got a new font in my terminal.
I will also note that Cousine is an alias for "monospace" and it doesn't appear that it is actually monospaced. Or rather, it appears that the Cousine .ttf file may actually not be Cousine Regular? Mysteries!
dh...@google.com
This still requires developer mode, and as I understand it will need to be redone each boot. I don’t consider it an adequate workaround although of course it’s better than nothing.
Another reason for allowing font installation: not all characters are actually included on Chromebooks. I found out today that I don’t have U+21B7 CLOCKWISE TOP SEMICIRCLE ARROW when something which was using that showed boxes instead on my Pixelbook. On any other system, I’d just install a font which had that; obviously I can’t here. People who regularly work with ancient scripts, or conlangs, or something else for which there’s a standardization effort outside of Unicode in a PUA (seehttps://en.wikipedia.org/wiki/Private_Use_Areas#Standardization_initiative_uses ) would probably also like to install scripts for those use cases.
Another reason for allowing font installation: not all characters are actually included on Chromebooks. I found out today that I don’t have U+21B7 CLOCKWISE TOP SEMICIRCLE ARROW when something which was using that showed boxes instead on my Pixelbook. On any other system, I’d just install a font which had that; obviously I can’t here. People who regularly work with ancient scripts, or conlangs, or something else for which there’s a standardization effort outside of Unicode in a PUA (see
da...@google.com
Re: boxes, that's https://crbug.com/chromium/950374 ; it sounds like that was an oversight and they're working on fixing it.
Agreed that developer mode isn't an option or a viable workaround for many users.
Agreed that developer mode isn't an option or a viable workaround for many users.
dh...@google.com
I’m glad to know that the Unicode coverage issue is being handled; I missed it when searching.
But that was still never my primary reason for wanting custom fonts, even if it’s what recently reminded me of the issue. Is there any update?
But that was still never my primary reason for wanting custom fonts, even if it’s what recently reminded me of the issue. Is there any update?
je...@chromium.org
We have submitted a UX research request to look into users' needs here, which will inform whether or not we ultimately support custom font management.
There is a UXR backlog, but as/when the findings of that research become available, I'll be sure to follow up here. Thanks for your patience with this.
There is a UXR backlog, but as/when the findings of that research become available, I'll be sure to follow up here. Thanks for your patience with this.
ze...@chromium.org
[Empty comment from Monorail migration]
ad...@chromium.org
[Empty comment from Monorail migration]
ad...@chromium.org
[Empty comment from Monorail migration]
[Deleted User] <[Deleted User]>
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit
pi...@google.com
I'd love to take a stab at this in my free time if someone can point me in the right direction. My kingdom for the ability to install NerdFonts on an enterprise-enrolled device.
Unfortunately, however, it seems like this might require some nontrivial UI changes.
Unfortunately, however, it seems like this might require some nontrivial UI changes.
kh...@chromium.org
> Unfortunately, however, it seems like this might require some nontrivial UI changes.
Thanks for the offer! However, I think you're right here - this feature would be a fairly large undertaking, and we'd need planning from PM/UX as well as a TDD before starting.
Leaving this as Available for tracking purposes, but it's unlikely we'll get to this in the short term.
Thanks for the offer! However, I think you're right here - this feature would be a fairly large undertaking, and we'd need planning from PM/UX as well as a TDD before starting.
Leaving this as Available for tracking purposes, but it's unlikely we'll get to this in the short term.
[Deleted User] <[Deleted User]>
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visithttps://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit
kh...@chromium.org
[Empty comment from Monorail migration]
rj...@gmail.com
> Unfortunately, however, it seems like this might require some nontrivial UI changes
What, installing fonts?
What would be easier than adding an install action for supported font files (i.e. user double-clicks on a .ttf file in the Files app)? Or making it possible to store a webfont in some location where it becomes available system-wide (meaning also for Android apps)?
Seems to me that the building blocks for the required UI must already be available; a (context) menu entry and a confirmation popup...
What, installing fonts?
What would be easier than adding an install action for supported font files (i.e. user double-clicks on a .ttf file in the Files app)? Or making it possible to store a webfont in some location where it becomes available system-wide (meaning also for Android apps)?
Seems to me that the building blocks for the required UI must already be available; a (context) menu entry and a confirmation popup...
xi...@google.com
[Empty comment from Monorail migration]
[Monorail components: -OS>Systems>Settings UI>Shell>SystemFonts]
[Monorail components: -OS>Systems>Settings UI>Shell>SystemFonts]
bi...@chromium.org
[PEL stale bug cleanup]
This bug is identified as affecting an enterprise customer, but the last modified date is over 3 months ago, has no owner, or a combination of the two. In some cases, the bug affects a milestone that has long passed.
If the issue is still affecting a customer with a support case, support teams can re-open the bug.
If the issue is in the backlog for engineering and still being planned, please remove the Hotlist = Enterprise and reopen the bug.
If the issue is actually resolved, please update the bug with the status for reference.
This bug is identified as affecting an enterprise customer, but the last modified date is over 3 months ago, has no owner, or a combination of the two. In some cases, the bug affects a milestone that has long passed.
If the issue is still affecting a customer with a support case, support teams can re-open the bug.
If the issue is in the backlog for engineering and still being planned, please remove the Hotlist = Enterprise and reopen the bug.
If the issue is actually resolved, please update the bug with the status for reference.
zz...@gmail.com
Please reopen it. Since chromeos consider a developer tool, it should have this simple feature, at least for a terminal.
aw...@gmail.com
please reopen this issue, I want powerline fonts to run fine on my chromeos
is...@google.com
te...@gmail.com
is this still broken ?
Description
Platform: 4537.147.0 (Official Build) stable-channel peppy
Steps to reproduce the problem:
ChromeOS comes with some good fonts, but they don't have certain characters defined that I require. There is no documented method (that is supported) to install new fonts.
What is the expected behavior?
User should be able to install new fonts and/or patched fonts.
What went wrong?
To install fonts, you need to remove rootfs verification, reboot, then copy *.ttf to /usr/share/fonts. This of course is not supported. I can do this... but would prefer a supported solution that I can use when using ssh app and connected to a machine that requires patched fonts to show useful symbols in terminal.
Did this work before? N/A
Chrome version: 30.0.1599.116 Channel: n/a
OS Version: 4537.147.0
Flash Version: Shockwave Flash 11.9 r900
I need to install patched fonts in order to see special characters when I ssh into remote machines. For example: