Upgrading texlive-kpathsea to texlive-kpathsea-7:20170520-39.fc28.x86_64 leads to yes: standard output: Broken pipe on the terminal and a long wait (and least for several minutes). "ps fauwwwx" on another terminal shows /usr/bin/updmap running. I can reproduce the issue by downgrading texlive-kpathsea to texlive-kpathsea-7:20170520-37.fc28.x86_64 (which works perfectly without any delays or messages) and upgrading it again.

Snippet from "ps fauwwwx" output:

root     28599  0.0  0.0 355156  7592 pts/0    S+   09:18   0:00  |   |   \_ sudo dnf upgrade texlive-kpathsea
root     28608  1.5  0.5 661060 166336 pts/0   S+   09:18   0:02  |   |       \_ /usr/bin/python3 /usr/bin/dnf upgrade texlive-kpathsea
root     30867  0.0  0.0 214464  3220 pts/0    S+   09:19   0:00  |   |           \_ /bin/sh /var/tmp/rpm-tmp.ppqOnH 0 0
root      8898  4.0  0.0 244824 13936 pts/0    S+   09:21   0:00  |   |               \_ /usr/bin/perl /usr/bin/updmap --sys --force --enable Map=qcr-ec.map

dvipdfmx dies with this update:

$ dvipdfmx foo.dvi 
foo.dvi -> foo.pdf
[1
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+231/600 --dpi 831 gbm
mktexpk: Running gsftopk gbm 831
gsftopk(k) version 1.19.2
gs died due to signal 11

grep: gbm.log: そのようなファイルやディレクトリはありません
mktexpk: `gsftopk gbm 831' failed to make gbm.831pk.
kpathsea: Appending font creation commands to missfont.log.

dvipdfmx:warning: Could not locate a virtual/physical font for TFM "gbm".
dvipdfmx:warning: >> This font is mapped to a physical font "gbm".
dvipdfmx:warning: >> Please check if kpathsea library can find this font: gbm
dvipdfmx:fatal: Cannot proceed without .vf or "physical" font for PDF output...
dvipdfmx:fatal: Cannot proceed without .vf or "physical" font for PDF output...

Output file removed.

Reverting to the previous updates-pushed ones makes dvipdfmx work again.