Works great! LGTM! =)

Works for me.

Appears to work: I installed texlive-scheme-full and still have a working LaTeX.

Upgrading from a not working tex installation: All problems are gone.

Unfortunately still does not work for me. I get

!pdfTeX error: /usr/bin/pdflatex (file cmex9.t3): cannot open Type 1 font file for reading ==> Fatal error occurred, no output PDF file produced!

I've tried to isolate the problem and finally got to a strange thing I don't understand (maybe it is related to the amsmath package? or to me only?):

==========================

% mwe for reproducing the problem

%\pdfmapfile{-mpfonts.map}

\documentclass{article} \usepackage{amsmath}

\begin{document} The following decreasing of the font size always works in the tabular environment:
\begin{center} \begin{tabular}{c} \hline $\small \prod$ \ \small Something \ \hline
\end{tabular} \end{center}

However, the following only works without the amsmath-package (with the amsmath-package, we need to comment out the ''small'' command):
\begin{center} %\small % <-- THIS SEEMS TO CAUSE THE PROBLEM TOGETHER WITH amsmath and some math commands \begin{tabular}{c} \hline $\prod$ \ \hline
\end{tabular} \end{center}

The problem above only occurs, if we have a tabular entry in math mode. Without math mode it also works in the second way:
\begin{center} \small \begin{tabular}{c} \hline Something \ \hline
\end{tabular} \end{center} Other observations:\ (1) The problem only seems to occur, if I descrease the font size (from normalsize).\ (2) The pdfmapfile at the beginning seems to fix the problem entirely. \ (3) Somehow, the problem seems to be restricted to some particular math commands like $\backslash prod$, $\backslash bigcup$, $\backslash bigcap$ ... \end{document}

====================

So, either - disabling the amsmath package, or - putting pdfmapfile (of which I don't know what it does, apart of (re-)linking some font files !?), or - not using \small, \scriptsize, \footnotesize, \tiny together with the tabular environment and some math commands.

The only thing I can say is that the problem did not happen before upgrading to F35, several new installs of texlive did not fix it and updating to texlive-2021-48.fc35 didn't fix it either.

@axiomatic: I cannot verify your problem. No problem here. If your upgrade was correct fgrep .t3 /var/lib/texmf/fonts/map//updmap/map|wc -l should output 0.

@axiomatic: please make sure you update all of the texlive packages, especially texlive-kpathsea. If you still have an issue after all of the texlive packages in this update are updated, please open a new bugzilla report!

@axiomatic I can't reproduce it either, your document compiles just fine. Be sure to run

dnf --enablerepo=updates-testing update texlive*

If've updated to the entire updates-testing of F35 and also checked what jholm indicated (this was a key I guess, had a lot of thing in there). Now it works, too with me :-) Thanks!

Update seems to work for me.

Works

no regressions noted

Works as intended.

Works fine.

Fixed as mentioned in C22 of BZ#2025720

works for me

I have the same error, but I attributed it to biber and not texlive: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1e62fda204

Where not using biber, this texlive update seems to be working

@fuller: same here. @ankursinha: where did you get biber-2.17? I didn't see in update/35 nor in updates/testing/35

the biber 2.17 update is here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1e62fda204