https://bugs.winehq.org/show_bug.cgi?id=54993
--- Comment #12 from Ulrich Gemkow ulrich.gemkow@ikr.uni-stuttgart.de --- Thanks again! Unfortunately its a little bit difficult: The bug happens always (also in old wine releases) when FrameMaker cannot open a file (in this case 0_1_Inhalt.fm) which is needed for its operations. The described search operation in only one of these operations. This is an old problem and we know how to handle it and it shows in different ways (memory corruption, maybe also be a race).
One reason for FrameMaker not being able to open a file is the existence of a .lck-File. This tells FrameMaker that the file is already open for reading and FrameMaker refuses to open it. Such .lck-Files remain when FrameMaker crashes, normally they are deleted when FrameMaker closes regulary. The solution is simple - delete the .lck file and all is fine.
But starting with the given commit, FrameMaker _always_ cannot open a file in book operations because of the missing Postscript base font. So there is no way around this anymore (like deleting the .lck file) and so IMHO this is a regression caused by this commit (or something around, the commit itself looks good). This is what i meant in comment #8 last paragraph regarding bug #54980.
Is this a regression in the wine-sense? For the user of the program it is - its no longer usable because many operations fail.