Comment # 3 on bug 1118557 from Ulrich Windl

(In reply to Dr. Werner Fink from comment #1)
> No CM but
> 
>  > grep fontset -i /usr/share/X11/app-defaults/XDvi
>  *tipShell.fontSet: -*-helvetica-medium-r-*-*-12-*-*-*-*-*-*-*

I see the same output here, but xdvi still complains:
~> xdvi
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Error: Aborting: no fontset found

What are the roles of ~/.cache/texmf/fonts and ~/texmf/fonts?
I only have .cache/texmf/fonts/pk/ljfour/public/cm/cm*pk here, but xdvi seems
to look for "vf" instead of "pk"...

(In reply to Stefan Br�ns from comment #2)
> *only* mkfontdir and the xorg-x11-fonts-core are required. As soon as you
> install both packages, everything else is configured automatically.
> 
> You may need to relogin for the changes to take effect.
> 
> This is a packaging bug in texlive-xdvi.

I have both: mkfontdir-1.0.7-lp150.1.6.x86_64 (/usr/bin/mkfontdir) and
xorg-x11-fonts-core-7.6-lp150.2.1.noarch installed, but still no luck.
I tested a very old (1996) DVI file that definitely worked on previous
versions, as well as the version created with Leap 15.0: Both bring up the same
error messages.

When using "xdvi -notype1fonts" I see some fonts being created, but still xdvi
ends like this:

Font metrics written on cmr10.tfm.
Output written on cmr10.657gf (128 characters, 26100 bytes).
Transcript written on cmr10.log.
mktexpk: /home/user/.cache/texmf/fonts/pk/ljfour/public/cm/cmr10.657pk:
successfully generated.
Warning: Missing charsets in String to FontSet conversion
Warning: Unable to load any usable fontset
Error: Aborting: no fontset found