http://bugs.winehq.org/show_bug.cgi?id=2622
joe@eshu.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |
------- Additional Comments From joe@eshu.net 2006-12-09 18:12 ------- James Hawkins' theory would be a nice one, if it fit the facts, but it doesn't. I _do_ have freetype-devel and fontforge installed, and the fact that I uninstalled all traces of wine and then reinstalled _all_ the wine*-0.9.20-1.fc5 rpms, means that if I am missing files, then the rpm packaging is broken.
Just because the installer behaves strangely (double dialogs, etc.) and the app crashes wine immediatley certainly doesn't mean that the bug is _fixed_! What sort of reasoning could possibly make one believe that the behavior I see is in any sense acceptable?
Moreover,
pequod(~) wine --configure verbose
crashed just like winecfg, etc.
wine: creating configuration directory '/home/joe/.wine'... fixme:ole:ITypeInfo_fnRelease destroy child objects wine: Unhandled page fault on read access to 0x003c002f at address 0x7eea41a7 (thread 0009), starting debugger...
but no debugger.
If this is "fixed", then I might as well be helping to debug Windows XP for all the concern this shows about quality!
-
Wine Bugs