https://bugs.winehq.org/show_bug.cgi?id=54993
--- Comment #15 from Ulrich Gemkow ulrich.gemkow@ikr.uni-stuttgart.de --- (In reply to Fabian Maurer from comment #14)
I found another thing, I still had cups disabled from years ago, apparently it crashes as well when there's no printers found.
Now it crashes directly on startup, same error message. Figured that out to be a divide my zero crash. I'll continue investigation, maybe I can soon see the regression you talked about.
May I ask what kind of printer you got configured? Because I got cups virtual pdf, and that seems to make issues.
The crash-dialog you see is shown when FrameMaker encounters something which it regards as an internal error or an unexpected condition it cannot handle. ("assertion"). The dialog is caused by many different circumstances, its a kind of exception handler to prevent more damage (FrameMaker is build for reliabilty). There are a few causes we know and can bypass.
So that you see the dialog box also in previous wine releases does not mean its the same error - it may very well be of different cause. Unfortunately FrameMake is a little bit sensitive but because of this a very good source to find regressions.
That is the reason why I mostly report Framemaker bugs as regressions after careful exclusion of other differences in the environment.
Regarding the printer/CUPS question: Yes, the printer configuration makes a difference. We use network connected printers which are described by a ppd-file (Postscript printer) which have the Postscript Fonts build in.
In the meantime I found why the named commit causes problems (please see my changed description of #54980 and my last comment) and the problem goes beyond FrameMaker, it also affects other word processing programs which rely on printer supplied fonts (cups sends a list of fonts which the printer supports, in our case the base postscript fonts and a few more).
Would you share how you found that the problem is a division by zero? I never managed to find a bug before the crash handler dialog appears. Thanks!