Question

3

How to configure X11 to find a font as requested by a proprietary binary

rated 0 times [ 3] [ 0] / answers: 1 / hits: 9706 / 1 Year ago, fri, november 18, 2022, 2:03:00

Starting a proprietary binary I get the following error message:

FATAL ERROR from X-windows: font not found: -*-*helvetica-bold-r-normal-*-11-*-*-*-*-*-*-*

I'm not quite experienced in handling with fonts, but as far as I understand that string -*-*helvetica-bold-r-normal-*-11-*-*-*-*-*-*-* should match a helvetica font, bold, in size 11, which should be quite a normal font.

After googling I tried the following things without result:

$ sudo xlsfonts -fn -*-*helvetica-bold-r-normal-*-11-*-*-*-*-*-*-*

xlsfonts: pattern "-*-*helvetica-bold-r-normal-*-11-*-*-*-*-*-*-*" unmatched

# in case the `*` is a problem:

$ sudo xlsfonts -fn -*-helvetica-bold-r-normal-*-11-*-*-*-*-*-*-*

xlsfonts: pattern "-*-helvetica-bold-r-normal-*-11-*-*-*-*-*-*-*" unmatched

also

$ sudo mkfontdir

$ sudo xset fp rehash

didn't help.

How can I find the problem? And how to solve it?

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

ightrushi

Add To Favorites

Follow

Total Points: 129

Total Questions: 125

Total Answers: 127

Location: French Southern and Antarctic Lands

Member since Fri, Jan 6, 2023

1 Year ago

ightrushi questions

1 22.04 Input devices freeze when docking station connects

Fri, May 19, 23, 16:32, 1 Year ago

1 Virtual desktop scroll with mouse not working since upgrade to Kubuntu 21.04

Mon, Jul 4, 22, 06:21, 2 Years ago

1 Alt-Tab and Workspace Switcher shortcuts aren't working on Xubuntu 21.10

Fri, Oct 8, 21, 23:24, 3 Years ago

1 Screen Brightness Issues on Lenovo Legion 5 pro 2021 (ubuntu 20.04)

Sun, Sep 4, 22, 16:13, 2 Years ago

1 Installing R and RStudio in Lubuntu 20.04

Tue, Feb 28, 23, 10:29, 1 Year ago

View All

answered 1 Year ago kilusy · Accepted Answer

I couldn't find a better solution then changing the strings in a fonts.dir file to match the strings.

Assuming that the normal Courier font should be at least readable if used incorrectly, I copied all the files from the vanilla Type1 folder into a local font folder and also the lines from the Type1/fonts.dir which contained the name courier. Then I added at the end of the names string just helvetica and rehashed the font cache. Then the program could start without an error.

$ cp /usr/share/fonts/X11/Type1/c0* ~/fonthack/

$ cp /usr/share/fonts/X11/Type1/fonts.dir ~/fonthack/

$ vim ~/fonthack/fonts.dir

# editing the lines. e.g.:

# from: c0419bt_.pfb -bitstream-courier 10 pitch-medium-r-normal-0-0-0-0-m-0-adobe-standard

# to: c0419bt_.pfb -bitstream-courier 10 pitchhelvetica-medium-r-normal-0-0-0-0-m-0-adobe-standard

# removed all lines without ``courier'' in their names

$ xset fp rehash

$ ~/the_tool_i_want_to_use