[Bug 41152] New: fontconfig 2.12.1 breaks wine for me on OS X 10.11.6
https://bugs.winehq.org/show_bug.cgi?id=41152 Bug ID: 41152 Summary: fontconfig 2.12.1 breaks wine for me on OS X 10.11.6 Product: Wine Version: 0.9.16. Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mf2k(a)macports.org Distribution: --- On OS X 10.11.6, I built wine 1.8.3 and 1.9.16 with fontconfig 2.12.1 and I see the following runtime errors: $ wine myapp.exe err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded. err:winediag:nulldrv_CreateWindow The explorer process failed to start. err:ole:apartment_createwindowifneeded CreateWindow failed with error 0 Going back to fontconfig 2.12.0 works just like normal. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 Frank Schima <mf2k(a)macports.org> changed: What |Removed |Added ---------------------------------------------------------------------------- OS|Linux |Mac OS X Hardware|x86 |x86-64 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #1 from Nikolay Sivov <bunglehead(a)gmail.com> --- That's weird. The only functionality change I see is commit 7a4a5bd7897d216f0794ca9dbce0a4a5c9d14940 (in fontfonfig git), could you try to revert it to see if it works? Also please attach +font,+tid log, and it makes sense to try of clean/update of fontconfig cache when switching to newer version. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #2 from Frank Schima <mf2k(a)macports.org> --- I'll try to figure it out. It may take me a few days. I'm using Macports, so I don't generally get into touching project source code directly. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #3 from Ken Thomases <ken(a)codeweavers.com> --- For what it's worth, Wine does not use FontConfig by default on macOS. It uses the native Mac font APIs, instead. MacPorts overrides this by specifying --with-fontconfig as a configure option. Should still work, of course. Also, which user/graphics driver is your prefix configured to use? Can't hurt to add +x11drv,+macdrv channels to the log that Nikolay requested. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #4 from Frank Schima <mf2k(a)macports.org> --- Thanks for the Macports specific feedback. I will look into it soon and get back to you. I'm not sure which graphics driver Macports is using. I will also try rebuilding the fontconfig cache. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #5 from Frank Schima <mf2k(a)macports.org> --- I ran some tests with wine 1.9.16. Macports builds the 32-bit version of wine and sets --with-x. Rebuilding the fontconfig cache did not help. I used: fc-cache -f -v Then I built wine using --without-fontconfig. That worked! But the windows were bigger. Maybe the resolution changed somehow? Finally, I tried building using both --without-fontconfig and --without-x. Based on my limited understanding, that means it will use the "mac" graphics driver, correct? It worked with the same result of the bigger windows. I would be curious if someone could try building on another platform using --with-fontconfig and fontconfig 2.12.1. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #6 from Frank Schima <mf2k(a)macports.org> --- Also, I do not know where to find the logs that Nikolay wants. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #7 from Ken Thomases <ken(a)codeweavers.com> --- (In reply to Frank Schima from comment #6)
Also, I do not know where to find the logs that Nikolay wants.
Read items 10.1.1 and 10.1.2 at <https://wiki.winehq.org/FAQ#get_log>. When you build --without-fontconfig, you may get a slightly different set of fonts. That might explain the bigger windows. You don't have to configure --without-x to use the Mac driver. Both the X11 and Mac drivers are built by default and the Mac driver is used in preference to X11. It's possible that the Mac driver fails to load when FontConfig is enabled and it was falling back to the X11 driver. If so, that might explain why things changed in appearance when you built --without-fontconfig. You should be able to tell the difference by whether XQuartz is launched when you run something in Wine and whether it is hosting Wine's windows or if they are in a separate app process. If FontConfig is somehow interfering with the ability of the Mac driver to load, it's possible that FontConfig 2.12.1 just adds to that problem by also interfering with the X11 driver. Both drivers would have to fail to produce the error messages you're seeing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #8 from Frank Schima <mf2k(a)macports.org> --- It must be using the mac driver then. x11 (I use xorg-server from Macports) does not launch when I use wine either in the past or now. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 Leonardo <leonardo.f.cardoso(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leonardo.f.cardoso(a)gmail.co | |m -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 Frank Schima <macsforever2000(a)macports.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |macsforever2000(a)macports.or | |g --- Comment #9 from Frank Schima <macsforever2000(a)macports.org> --- Created attachment 55536 --> https://bugs.winehq.org/attachment.cgi?id=55536 requested log Sorry for the delay. I have attached the +font +tid log output. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #10 from Ken Thomases <ken(a)codeweavers.com> --- (In reply to Frank Schima from comment #9)
Created attachment 55536 [details] requested log
Sorry for the delay. I have attached the +font +tid log output.
Thanks. Unfortunately, I'm not immediately seeing a smoking gun in there. Do you mind collecting a +tid,+macdrv,+x11drv,+user,+module,+loaddll,+explorer,+reg log? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 Martin Fuhrer <mfuhrer(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfuhrer(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 Rosanne DiMesio <dimesio(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrewsuicune(a)gmail.com --- Comment #11 from Rosanne DiMesio <dimesio(a)earthlink.net> --- *** Bug 41240 has been marked as a duplicate of this bug. *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #12 from Frank Schima <macsforever2000(a)macports.org> --- Created attachment 55641 --> https://bugs.winehq.org/attachment.cgi?id=55641 New log Here is the log with +tid,+macdrv,+x11drv,+user,+module,+loaddll,+explorer,+reg -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 Ken Thomases <ken(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ken(a)codeweavers.com --- Comment #13 from Ken Thomases <ken(a)codeweavers.com> --- (In reply to Frank Schima from comment #12)
Created attachment 55641 [details] New log
Here is the log with +tid,+macdrv,+x11drv,+user,+module,+loaddll,+explorer,+reg
Thanks for that. It narrowed it down somewhat, but still doesn't show the exact problem. If you don't mind, could you collect another log, this time with these channels: +tid,+macdrv,+user,+module,+loaddll,+explorer,+reg,+win,+relay,+user,+menu,+hook,+message,+font For what it's worth, I have tried installing wine-devel using MacPorts to try to reproduce the problem and debug it directly, but it doesn't happen for me. It may be sensitive to exactly which fonts you have installed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tobbi.bugs(a)googlemail.com --- Comment #14 from Bruno Jesus <00cpxxx(a)gmail.com> --- *** Bug 41235 has been marked as a duplicate of this bug. *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #15 from Frank Schima <macsforever2000(a)macports.org> --- fontconfig 2.12.1 resolves the problem for me. Apologies for not replying sooner about this. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #16 from Ken Thomases <ken(a)codeweavers.com> --- (In reply to Frank Schima from comment #15)
fontconfig 2.12.1 resolves the problem for me.
Hmm? I thought that was the version which introduced the problem. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #17 from winetest(a)luukku.com --- Maybe he just said wrong version? Anyway this bug can be marked as fixed/notourbug? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 --- Comment #18 from Frank Schima <macsforever2000(a)macports.org> --- Sorry for the confusion. In Macports, we have a patch for fontconfig that fixes the performance problem in revision 1 of the port. So it is a fontconfig problem, not wine. Feel free to close this ticket. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 Ken Thomases <ken(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #19 from Ken Thomases <ken(a)codeweavers.com> --- The issue seems to have been on the FontConfig side. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #20 from Austin English <austinenglish(a)gmail.com> --- Closing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41152 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED --- Comment #21 from Austin English <austinenglish(a)gmail.com> --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream. Setting back to RESOLVED NOTOURBUG. Sorry for the spam. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org