[Bug 59686] New: Popotan Po!: No text/fonts when using new WoW64 mode (but works using win32)
http://bugs.winehq.org/show_bug.cgi?id=59686 Bug ID: 59686 Summary: Popotan Po!: No text/fonts when using new WoW64 mode (but works using win32) Product: Wine Version: 11.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@list.winehq.org Reporter: ms_313b11f8dd030fbf515e3a6beac6ba2243b23eae@lambsauce. de Distribution: --- Created attachment 80788 --> http://bugs.winehq.org/attachment.cgi?id=80788 Wine log files of the configurations tested Running "Popotan Po!" (ぽぽたん Po!) in a new wow64 mode prefix results in no in-game text. Instead, whenever text is supposed to be rendered, wine has 100 % CPU load according to htop for about 40 to 110 seconds, depending on the situation. Text on normal widgets (e.g. menu bar or window title bar) works fine. Host architecture: x86_64 (Arch running Linux 6.19.13) Guest architecture: i386 Tested with the following Wine packages/versions used on Arch (logs attached): - BAD: wow64 prefix with wine 11.7-1 (https://archlinux.org/packages/extra/x86_64/wine/) - BAD: wow64 prefix with wine-staging 11.7-1 (https://archlinux.org/packages/extra/x86_64/wine-staging/) - GOOD: win32 prefix with wine32 11.7-1 (https://aur.archlinux.org/packages/wine32) Further observations: - The problem does not appear in a win32 prefix (and it never did for the last 10 years or so). - Whether you use wine or wine-staging makes no apparent difference. Steps to reproduce: 1. Create a new wine prefix using winecfg and make wine emulate an 800x600 desktop. 2. Use the appropriate locale (otherwise, all dialogs only show mojibake): export LANG="ja_JP.eucjp" export LC_ALL="ja_JP.eucjp" 3. Install the game using the defaults suggested by the installer. 4. Launch the game. For this issue, there seems to be no difference between "tsuujouban" (通常版) and "koukinouban" (高機能版). Choose "tsuujouban". 5. At that point, if the problem occurs, you might get the 100 % CPU load mentioned above. Also, the whole wine dektop window freezes. Be patient. 6. The intro video starts. (In my case, playback only works in the wow64 prefixes but not in the win32 prefix. Instead, the screen appears all-black or all-white. Ignore that issue.) Use ESC to skip the intro. 7. In the main menu, choose "Config" (コンフィグ). 8. In the top-right corner, you can choose a "Font" (フォント). The name of the font is rendered between the two arrows using itself for demonstration purposes. Due to the issue at hand, the space between the two arrows appears empty as if no font is available. 9. Go back (ゲームへ戻る). 10. Now, back in the main menu, choose "tsuzuki kara" (つづきから). 11. Again, if the problem occurs, you might get 100 % CPU load and a frozen window. Be patient. 12. If everything works normally, saved game states should be listed. Even unused slots show some text like "----/--/-- --:--" (without quotes). However, due to the issue at hand, all lines appear empty (except for the numbers to the left which are, apparently, rendered using bitmaps, just like everything else so far). 13. Go back (タイトルへ). 14. Now, again back in the main menu, choose "hajime kara" (はじめから). The actual game starts. 15. Normally, a text box at the lower bottom appears, along with text in it as the story progresses. However, if the problem occurs, you might get 100 % CPU load and freezes along the way. Be patient whenever that happens. 16. A star symbol appears at the end of the text in the text box. The exact position of the star seems to be fixed. That is, the position seems to be independent of the glyphs used to render the text. As a result, if the problem occurs, the star seems to appear at various positions within the box, with no actually visible text ahead of it but close to where the text *should* have ended. Attempted workarounds: - Using "winetricks corefonts" or "winetricks allfonts" did not help. - Running "fc-cache -fv" also did not help. - Assuming it might be an encoding or locale problem, I tried *really hard* to make the whole thing run with locale ja_JP.UTF-8, with the result that it actually *did* run with that locale somehow. However, the issue persisted. - Using that same experimental prefix, I tried running it with locale ja_JP.UTF-8 again, but this time with "Windows Version" set to "Windows XP" in winecfg, to no avail. - When I tried to make it run with locale en_US.UTF-8, it crashed before I got to the intro. (This is not too surprising.) Further investigation and speculation: - The game seems to only list fonts it considers usable, so probably only fonts that are compatible enough for Japanese. - The config is stored in the registry, and by default (at least in my case), the installation in the win32 prefix as well as the installation in the wow64 prefix both use "FontFace"="ＭＳ ゴシック" according to regedit. Thus, despite already knowing the name of a font face to use, only the win32 prefix can make sense of it while the wow64 prefix cannot. - Even copying a working non-default value like "さざなみゴシック" from the registry of the win32 prefix and then pasting it as the new value into the wow64 registry did not help. - You can actually switch between different fonts using the arrows in the config screen mentioned above, even if you do not see it happening in the wow64 prefix. For example, after switching randomly and then closing the game, the corresponding value in the registry now reads "AR PL UMing TW MBE", for example. The very same font can be chosen normally in the win32 prefix as well. This indicates that the game in the wow64 version knows of the available fonts it considers usable, it just fails to render text properly using them. - For some unknown reason, though, the config screen opens quickly while everything else that normally has some text in it just burns CPU and displays no text at all. - Maybe it has something to do with Unicode stuff? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59686 --- Comment #1 from Rafał Mużyło <galtgendo@o2.pl> --- ...a serious question: why ja_JP.eucjp, instead of ja_JP.utf8 ? Unless in 2026 you still run your linux distro in a non-utf8 locale... Also, a link to a demo would be helpful, though check if it's one accessible outside Japan, cause due to certain pedophile parties (i.e. ones using 'think of the children' cover to press their censorious and totalitarian views on those who don't care about them) some aren't without a Japanese proxy. (also, for some reason I can't download your logs..., though it might just be my local problem; given that it seems to be a font problem, are you getting 'font' channel into that log ?) Then again, given it works in the old style wine, the problem might be somewhat trickier... -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59686 --- Comment #2 from Rafał Mużyło <galtgendo@o2.pl> --- Created attachment 80795 --> http://bugs.winehq.org/attachment.cgi?id=80795 my old font regkey set Also, I'm not quite sure which font reg setting you are referring to. For reference this is an old one of mine (now I'm just using a different font). -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59686 --- Comment #3 from nanashi3 <ms_313b11f8dd030fbf515e3a6beac6ba2243b23eae@lambsauce.de> --- Created attachment 80798 --> http://bugs.winehq.org/attachment.cgi?id=80798 Game config in registry -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59686 --- Comment #4 from nanashi3 <ms_313b11f8dd030fbf515e3a6beac6ba2243b23eae@lambsauce.de> ---
why ja_JP.eucjp, instead of ja_JP.utf8 ?
ja_JP.eucjp seems to be the only way to run it without additional issues like mojibake, as explained above.
Also, a link to a demo would be helpful
Indeed, that would be helpful. But sorry, I cannot provide a demo.
(also, for some reason I can't download your logs..., though it might just be my local problem; given that it seems to be a font problem, are you getting 'font' channel into that log ?)
I can download the tar file I attached just fine, and it's identical to the upload.
Also, I'm not quite sure which font reg setting you are referring to.
I just attached the entire config of the game as exported by regedit and, additionally, as UTF-8. (Don't worry, no spoilers in there.) Note the "FontFace" key. That is what I am referring to.
For reference this is an old one of mine
That's interesting. Neither HKEY_CURRENT_USER\Software\Wine\Fonts\Replacements nor HKEY_CURRENT_USER\Wow6432Node exist in the prefixes (win32, wow64) I created for testing. Is this still a thing or just some remnant of previous Wine versions? Because, again, everything (except video playback) seems to run just fine in win32 without it. Also, is there a way to auto-generate those registry entries? I don't think that having them will help, but I don't want to mess them up, either. Could it be some wine compilation settings issue? I am not well-versed when it comes to that. You can obtain the PKGBUILD files that describe how the different wine versions are compiled like this: - wine: git clone https://gitlab.archlinux.org/archlinux/packaging/packages/wine.git - wine32: git clone https://aur.archlinux.org/wine32.git Are there any noticeable problems or differences? By the way, is there a way to make the playback of the (partially rather famous) intro work in win32? There are some error messages related to it in the logs, but I still could not figure it out. Just installing lib32-gstreamer + plugins didn't help. (This is a side issue probably unrelated to the issue at hand.) -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59686 --- Comment #5 from Rafał Mużyło <galtgendo@o2.pl> --- Well, wrt. these keys: some of the games have MS Gothic/Mincho pretty much hard-coded and if the a font file providing them isn't present, fail to accept any of the valid substitutes without such keys. Might not be an issue here, given that the game allows changing the font (and actually gets the list from the system). As for locale, anything that runs in ja_JP.eucjp should work *at least* just as well in ja_JP.utf8, as long as that (or another utf8 locale) is the locale your main system is set up to work with. In such cases using utf8 actually skips quite a few problems that mixing encoding incompatible locales causes on Linux systems. As for your logs, seems to be a browser problem - wget fetches them correctly, but they don't seem to show anything of relevance. Fetch them again with WINEDEBUG=font . As for the win32 gstreamer question: you seem to be missing relevant 32bit gstreamer plugins, likely either gst-plugin-libav or the group around mpegpsdemux. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59686 --- Comment #6 from nanashi3 <ms_313b11f8dd030fbf515e3a6beac6ba2243b23eae@lambsauce.de> ---
Fetch them again with WINEDEBUG=font .
The output is HUGE! Also, about the first third of it contains paths with obvious privacy-relevant details (aside from indirect ones) like username. Is it possible to cut that part somewhere (where?) without losing relevant data? And/or maybe reduce the log level? Or automatically redact the content of the log file? Depending on that, I might need to prepare a privacy-preserving environment first. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59686 --- Comment #7 from nanashi3 <ms_313b11f8dd030fbf515e3a6beac6ba2243b23eae@lambsauce.de> --- Created attachment 80801 --> http://bugs.winehq.org/attachment.cgi?id=80801 Wine logs with WINEDEBUG=font I noticed that I cannot use the "normal" (new WoW) wine to use the win32 prefix if WINEARCH="win32" is set. However, I can use both the "normal" wine and the "wine32" wine to use the prefix I originally created with the normal wine and WINEARCH unset. Whenever I switch between the two, wine updates the prefix and then continues normally. As it turns out, the game shows all the buggy behavior (but video playback works) IF AND ONLY IF I use the "normal" wine. Thus, IF AND ONLY IF I use the "wine32" wine, everything works as expected (except for video playback). I created logs in such a way that I cut the initial part just before I clicked "tsuujouban". With that, I deem them sufficiently privacy-preserving, so I attached them. There are three logs: - wine32-win32-winedebugfont-tail.log : "wine32" wine with WINEARCH="win32" (GOOD). - wine32-wow64-winedebugfont-tail.log : "wine32" wine with WINEARCH unset (GOOD). - wine-wow64-winedebugfont-tail.log : "normal" wine with WINEARCH unset (BAD). I tried to apply the same sequence of actions in all cases: 1. click "tsuujouban" 2. press ESC to skip the intro 3. click "config" 4. go back 5. click "tsuzuki kara" 6. go back 7. click "shuuryou" (終了) 8. confirm - Note that the prefixes might not use the exact same in-game config, especially not the same font face. - Remember that text on normal widgets (e.g. menu bar or window title bar) works fine. (The menu bar appears if you move the mouse cursor to the top of the fullscreen window.) -- 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.
http://bugs.winehq.org/show_bug.cgi?id=59686 --- Comment #8 from nanashi3 <ms_313b11f8dd030fbf515e3a6beac6ba2243b23eae@lambsauce.de> --- I am not sure whether this is relevant, but the game applies some non-trivial effects (some outline and color gradient stuff) to the text. Maybe there are some limitations in wine (new wow64) that prevent it from applying those effects correctly, given how the game tries to accomplish that. (I do not know how the game implements the effect.) On the other hand, I would have expected some warnings even in the normal wine output if that were the case, especially because the issue seems to be specific to the "normal" wine while the wine32 wine does not have this issue. Also, that would not yet explain why most screens freeze when text should appear while the config screen appears instantly. I can provide screenshots if needed. -- 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)
-
WineHQ Bugzilla