September 2022 - Wine-Bugs - list.winehq.org

[Bug 53735] Battle.net does not log in, shows error log, in Bottles

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53735 --- Comment #5 from richardjecooke(a)pm.me --- Thank you Peter, I tried `sudo apt install lib32-libpulse lib32-alsa-libs` but they aren't found. Do you know where I could get them? -- 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.

Sept. 30, 2022

[Bug 53735] Battle.net does not log in, shows error log, in Bottles

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53735 PeterG <peter.g.anderson(a)live.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter.g.anderson(a)live.co.uk --- Comment #4 from PeterG <peter.g.anderson(a)live.co.uk> --- I had a similar problem on Arch linux using standard wine from the main repo. I found that by installing lib32-libpulse and lib32-alsa-libs that battle.net would successfully log in again. -- 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.

Sept. 30, 2022

[Bug 52950] JavaEditor shows grayed out menu items in black

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52950 --- Comment #9 from Joerg Schiermeier <mywine(a)schiermeier-it.de> --- This bug is still part of wine v7.18 from 23. September 2022. -- 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.

Sept. 30, 2022

[Bug 53739] New: [font cannot show in QQ ]When using the font replacement function in the registry, some fonts cannot be displayed, which affects normal use, and even makes the response speed of some functions of the application slow.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53739 Bug ID: 53739 Summary: [font cannot show in QQ ]When using the font replacement function in the registry, some fonts cannot be displayed, which affects normal use, and even makes the response speed of some functions of the application slow. Product: Wine Version: 7.16 Hardware: x86 OS: other Status: UNCONFIRMED Severity: major Priority: P2 Component: dwrite Assignee: wine-bugs(a)winehq.org Reporter: 399989567(a)qq.com Created attachment 73181 --> https://bugs.winehq.org/attachment.cgi?id=73181 replacement.reg -> the registry file I modified fontwrong.log -> log of errors that occurred My English is not good, so I hope to be forgiven if there are any poor wordings. First of all, I appreciate your help and I will describe my problem in three aspects. [ Background of the problem ] By using wine,I know that most of the font problems can be solved by installing “allfonts” ect through winetricks,but I noticed that most of the fonts are not open source. So I want to use all open source fonts to display text in wine by my own effort, such as NotoSans. My ability does not support me to modify the source code directly, so I mainly used the “Fonts\Replacements” function in the registry provided by wine to do the replacement of missing\not open source fonts. Most of the fonts displayed well after I made the replacements, but some fonts had rendering problems, and these problems even affected the use of the application. Through my own research I found that all the changes I made to the registry did not cause problems in wine 7.12, but in wine 7.18 they did. By dichotomy, I found that the cause of the problem is the modification of the file "dwrite", but I don't know where the problem occurs, so I'm asking for advice. [My actions] The changes I made to the registry are in the file "replacement.reg", which you can import directly from "./wine regedit." I also deleted the fonts in . /wine/fonts file, because I want to display all text in open source fonts. In addition to changing the Fonts\Replacements in the registry and . /wine/fonts file, I did not do any other things. And I found that in my above operation, QQ can display all the text normally in 7.12, but not in 7.18. [File description] replacement.reg -> the registry file I modified fontwrong.log -> log of errors that occurred My model: ThinkPad-X1-Debian-11.4.0-amd64-KDE I sincerely hope to get a reply, if you don't have time, you can simply point me in the right direction, I'm also working on it now, hopefully we can make wine better together Yours: SvenL QQ downloardURL:https://im.qq.com/download QQ Version:9.6.7 -- 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.

Sept. 30, 2022

[Bug 50779] thread changes in winegstreamer lead to increased virtual address space consumption which may lead to permanent freezes

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50779 --- Comment #21 from Rafał Mużyło <galtgendo(a)o2.pl> --- SHA1 of the regression would require a bisect, which (for reasons) I haven't done. What I did do (at least AFAIR - it's been over 1.5 years since already), was establish it happened at 6.1 exactly, then comb it for sound changes (as the bug was triggered upon sound effects playing), then with your help notice it was virtual mapping space exhaustion triggered by spawning multiple threads for each sound effect. That pretty much pointed towards the changeset containing 'winegstreamer: Manage our own streaming thread'. As that changeset was too complex to revert bit by bit (at least at my skill level), I've pretty much stopped there. Well, not so much stopped as that anything I've tried with adding debug lines and tinkering with little pieces afterwards didn't affect the bug. As the content of this bug is a bit confusing, to summarize in the game I could trigger the problem in the easiest way, all I needed to do was repeatedly press down in the title screen menu; on each press a sound effect from an mp3 file was being played; address exhaustion always managed to hit before engine's internal caching limit; changing that file to an ogg stopped the bug from triggering, as the engine embeds some ogg handling library, bypassing winegstreamer. Given that patching wine to make pulseaudio *not* use shm makes a difference, it's likely cause something like each effect having its own stream, instead of putting them all into one (...OK, that's extremely badly phrased, but you should get the gist of it). -- 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.

Sept. 30, 2022

[Bug 53711] Final Fantasy XI crashes randomly at multiple points

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53711 --- Comment #18 from pandora.xero(a)gmail.com --- I have a couple scripts ready to go over the weekend The first records the WINEDEBUG options and a timestamp to a file, then launches wine, with &> to another file. The second records a timestamp to one file, memory maps to another, waits for user input, then records a timestamp to a third file and memory maps to a fourth. I intend to start the game with the first script, launch the second script when I've selected my first character, and then when the game crashes, let the second script finish. This should provide a baseline memory map, a memory map at the crash, a log with all the specified channels, and a timestamp for each. I think the maps will be more useful than the logs, mostly because I'm predicting the logs will be anywhere from 200MB to 1GB. I predict the maps will also show the memory expansion much more clearly than what I have right 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.

Sept. 30, 2022

[Bug 53738] New: Cherry MIDI sequencer cannot read files with a path including CJK characters

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53738 Bug ID: 53738 Summary: Cherry MIDI sequencer cannot read files with a path including CJK characters Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shinichi.tanaka45(a)gmail.com Distribution: --- Created attachment 73180 --> https://bugs.winehq.org/attachment.cgi?id=73180 files can be opened (bgm_02.CHY) and cannot be opened (音楽_02.CHY). these files are same except its filename. A MIDI sequencer application "Cherry" (http://hp.vector.co.jp/authors/VA010012/, its UI is in Japanese because of Japanese developer) cannot open some files with a path including CKJ characters. When trying to open a file with CJK path, the app Cherry shows a dialog "File reading error or a malformed file format" (in Japanese). When launch in terminal with like "wine cherry.exe" then reproduce that behavior, but this app does ntnot output any logs about that. Detailed situations are like this: - files with a name only with ASCII characters can be opened - files with a name including CJK characters cannot be opened - files with a name only with ASCII but in a directory with CJK characters cannot be opened These behaviors are reproduced in all published versions of Cherry in that website : - v1.4.3 - v1.5.2 (alpha) - v1.5.3 (alpha) And the locale info in my machine is here: ``` locale LANG=ja_JP.UTF-8 LANGUAGE=ja:en_US:en LC_CTYPE="ja_JP.UTF-8" LC_NUMERIC=ja_JP.UTF-8 LC_TIME=ja_JP.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=ja_JP.UTF-8 LC_MESSAGES="ja_JP.UTF-8" LC_PAPER=ja_JP.UTF-8 LC_NAME=ja_JP.UTF-8 LC_ADDRESS=ja_JP.UTF-8 LC_TELEPHONE=ja_JP.UTF-8 LC_MEASUREMENT=ja_JP.UTF-8 LC_IDENTIFICATION=ja_JP.UTF-8 LC_ALL= ``` I tried some launching way below with specifying locale but these behaviors are reproduced: - `LC_ALL=ja_JP.UTF-8 wine cherry.exe` and open CJK path files - `LANG=ja_JP.UTF-8 wine cherry.exe` and open CJK path files I feel this may not be a problem about WineHQ, may be simply a problem about my locale settings, but I cannot resolve this so report as a 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.

Sept. 30, 2022

[Bug 53342] quartz:mpegaudio - The 64-bit test_streaming_events() times out on fg-deb64

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53342 --- Comment #3 from François Gouget <fgouget(a)codeweavers.com> --- Created attachment 73179 --> https://bugs.winehq.org/attachment.cgi?id=73179 Trace the BaseMemAllocator semaphore -- 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.

Sept. 30, 2022

[Bug 53342] quartz:mpegaudio - The 64-bit test_streaming_events() times out on fg-deb64

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53342 --- Comment #2 from François Gouget <fgouget(a)codeweavers.com> --- Created attachment 73178 --> https://bugs.winehq.org/attachment.cgi?id=73178 trace: deadlock on the BaseMemAllocator_GetBuffer() semaphore (In reply to Rémi Bernon from comment #1) > I'm not sure how I can test something on that VM. That's because it's my desktop (Debian 11, KDE, i7-4790K), not a VM. > Does a change like this maybe fix the issue? It didn't :-( The test still gets stuck in the same place. I have dug a bit further: * The test gets stuck on this line in BaseMemAllocator_GetBuffer() with dwFlags=0: if (WaitForSingleObject(This->hSemWaiting, (dwFlags & AM_GBF_NOWAIT) ? 0 : INFINITE) != WAIT_OBJECT_0) * Tracing all uses that I could see of that semaphore it's created and waited on on the same BaseMemAllocator_GetBuffer() line shortly after the test on line 1355 in test_sample_processing(). hr = IMemAllocator_GetBuffer(allocator, &sample, NULL, NULL, 0); * I have confirmed that it is test_sample_processing() that fouls things up for test_streaming_events(). Either of them is fine on its own but together the second one gets stuck because the semaphore is never released. -- 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.

Sept. 30, 2022

[Bug 53737] Incoming (game): crashes after the intro video

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53737 --- Comment #3 from Prajna Sariputra <putr4.s(a)gmail.com> --- Created attachment 73177 --> https://bugs.winehq.org/attachment.cgi?id=73177 Backtrace from the crash reporter (demo 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.

Sept. 30, 2022