May 2022 - Wine-bugs - list.winehq.org

[Bug 48175] New: AION (64 bit) - crashes in CrySystem32.dll.CryFree() due to high memory pointers allocated
by WineHQ Bugzilla 01 Dec '24

01 Dec '24

https://bugs.winehq.org/show_bug.cgi?id=48175 Bug ID: 48175 Summary: AION (64 bit) - crashes in CrySystem32.dll.CryFree() due to high memory pointers allocated Product: Wine Version: 4.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: gofmanp(a)gmail.com Distribution: --- Created attachment 65809 --> https://bugs.winehq.org/attachment.cgi?id=65809 Force down-top memory allocation Split off from bug #40334. The crash happens after the original issue in Bug #40334 is solved, after the loading screen or very soon after login. The game expects memory pointers from HeapAlloc and VirtualAlloc to fit in the certain range. It is fine with ~16GB range as per my observations, that is, up to 0x3ffffffff address. I am attaching the patch which is confirmed to fix the issue with AION. The patch consists of two, the first one is not exactly related but the second one depends on it. At the present moment the first one is passing the review upstream. The solution in the second patch is to force virtual memory allocation return lower addresses when they are available (unless top-down allocation is explicitly requested), that's how it seem to work on Windows. The patch does it essentially the same way as the allocation with zero_bits mask is performed. -- 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.

1 8

[Bug 52212] New: Doom Eternal - Crash on Launch
by WineHQ Bugzilla 30 Nov '24

30 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=52212 Bug ID: 52212 Summary: Doom Eternal - Crash on Launch Product: Wine-staging Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: linards.liepins(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 71270 --> https://bugs.winehq.org/attachment.cgi?id=71270 report_1 See attached bugreports for various wine and launch options. -- 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.

1 18

[Bug 46803] New: Diablo 1 GOG.com crash
by wine-bugs＠winehq.org 30 Nov '24

30 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=46803 Bug ID: 46803 Summary: Diablo 1 GOG.com crash Product: Wine Version: 4.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xzgamertag(a)mail.com Distribution: --- Created attachment 63823 --> https://bugs.winehq.org/attachment.cgi?id=63823 Log Diablo crashes immidiately after skipping intro, while using hi-res, latest version. When I try to run Diablo (Classic) version, it requires original CD to proceed. -- 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.

2 13

[Bug 16302] New: [oblivion] can not skip the intro movie by press ESC
by wine-bugs＠winehq.org 27 Nov '24

27 Nov '24

http://bugs.winehq.org/show_bug.cgi?id=16302 Summary: [oblivion] can not skip the intro movie by press ESC Product: Wine Version: 1.1.8 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: wangbinrobin(a)yahoo.com.cn when runing Oblivion on Windows, we can skip the intro movie by pressing ESC, but when runing Oblivion by wine, we can not skip it by ESC. it is quite a long time to wait the intro movie end. The graphic card I use is ATI Radeon 2600, driver 8.10 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 45

[Bug 45871] New: Several apps in .NET472 crash with unhandled exception.\nException at System.Windows.Media.Composition.DUCE+Channel.SyncFlush ()\n at System.Windows.Media.MediaContext.Complet"...( native d3dcompiler works around it)
by wine-bugs＠winehq.org 25 Nov '24

25 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=45871 Bug ID: 45871 Summary: Several apps in .NET472 crash with unhandled exception.\nException at System.Windows.Media.Composition.DUCE+Channel.SyncFlus h()\n at System.Windows.Media.MediaContext.Complet"...(native d3dcompiler works around it) Product: Wine Version: 3.16 Hardware: x86 OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Created attachment 62374 --> https://bugs.winehq.org/attachment.cgi?id=62374 part of crashlog Hi Seen this for a bunch of programs while trying to run them with installed dotnet472. The bug seems to be hidden for several apps as they ship their owm d3dcompiler_47, but some don`t I found out, and they crash Something like: 01c2:fixme:d3dcompiler:make_assignment Check for casts in the lhs. 01c2:err:d3dcompiler:compile_shader HLSL shader parsing failed. 01c2:err:ntdll:vDbgPrintExWithPrefix 65: MIL FAILURE: Unexpected HRESULT 0x88760b59 in caller: intermediate rendering error 01c2:err:ntdll:vDbgPrintExWithPrefix 65: MIL FAILURE: Unexpected HRESULT 0x88760b59 in caller: The render thread failed unexpectedly. Then crash Example: Slackinstaller.exe: winetricks dotnet452 win7 corefonts, then start installer with builtin d3dcomiler_47 works fine. However winetricks dotnet472 win7 corefonts, then start installer with builtin d3dcomiler_47 --> crash (Note: for Slackinstller one also needs Staging-patches for bug 40613) -- 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.

2 24

[Bug 52078] New: MusicBee: exception when attempting to drag tabs
by WineHQ Bugzilla 24 Nov '24

24 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=52078 Bug ID: 52078 Summary: MusicBee: exception when attempting to drag tabs Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sangv(a)protonmail.com Distribution: --- Created attachment 71090 --> https://bugs.winehq.org/attachment.cgi?id=71090 The exception MusicBee gives + the console output, in a tarball When attempting to move the tabs located near the top of the window (the ones labelled "Music", "Now Playing", "Playlists", etc by default) MusicBee will throw an exception. This happens on both my existing MusicBee wineprefix as well as a fresh one, and on MusicBee versions 3.2.6804 and 3.4.7805. In addition to happening in Wine version 6.21, the issue remains in 6.22. Both versions of Wine were compiled from source. I'm using winetricks verbs `windowscodecs dotnet45 mfc42 xmllite gdiplus d3dx9 vcrun2008 wmp10`. My OS is EndeavourOS with kernel 5.15.2-zen1-1-zen. (I don't know how much of this information is really needed but I thought it was all worth a mention just in case?) Attached I have both the error MusicBee provides, as well as terminal output with debug channels warn+all as no information was printed in the terminal without 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.

1 9

[Bug 10472] New: File open dialog buffer too short for multiple file selection
by wine-bugs＠winehq.org 23 Nov '24

23 Nov '24

http://bugs.winehq.org/show_bug.cgi?id=10472 Summary: File open dialog buffer too short for multiple file selection Product: Wine Version: 0.9.49. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: wine-comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: freireclaudio(a)yahoo.com.ar The file open dialog seems to be using a buffer which is too short for multiple file selection. While Windows itself has this bug/feature, wine's version is much more annoying since I'm unable to select over 6 files usually (using long but not excessive names). A dynamic buffer (with a reasonable limit for security reasons perhaps) would be preferrable, but even a bigger buffer would help. I think windows' buffer is 4k. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 18

[Bug 52105] New: Handle to \Device\NamedPipe\ cannot be used as the RootDirectory for NtCreateNamedPipeFile
by WineHQ Bugzilla 22 Nov '24

22 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=52105 Bug ID: 52105 Summary: Handle to \Device\NamedPipe\ cannot be used as the RootDirectory for NtCreateNamedPipeFile Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com CC: jacek(a)codeweavers.com Regression SHA1: 2600ecd4edfdb71097105c74312f83845305a4f2 Distribution: --- Commit 2600ecd4edf (server: Use a separated object for each opened named pipe device file., 2018-10-29) split the role of the named pipe device and the named pipe file. However, in doing so, it changed the semantics of opening \Device\NamedPipe\. In particular, it is no longer possible to use a handle to \Device\NamedPipe\ as RootDirectory when creating a named pipe. This bug makes Cygwin's named pipe creation (https://github.com/cygwin/cygwin/blob/4f47e64b11ed8d47c62fa89e9b971f44b7e9a…) loop forever. -- 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.

1 21

[Bug 42606] New: wine doesn' t *fully* respect locale settings in some corner cases
by wine-bugs＠winehq.org 22 Nov '24

22 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=42606 Bug ID: 42606 Summary: wine doesn't *fully* respect locale settings in some corner cases Product: Wine Version: 2.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- This time it's a problem even if this is the only app currently running in the prefix. Download address for the engine: http://kikyou.info/dl_redirect.php?%2Ftvp%2Ffiles%2Fkr2_232r2.zip Instruction for setting up a project: http://kirikirikag.sourceforge.net/contents/Prepare.html (instructions seem to be for a different archive, but get the point across) So, when running 'LANG=ja_JP.utf8 wine krkr.eXe'(as it's different from my standard locale) and starting that project, most of the things seem to work correctly (as I've got the standard overrides for Gothic/Mincho set already in place), yet... When right clicking the engine console (not the game window), there's mojibake in that menu. WINEDEBUG=font log shows that for some reason CreateFontIndirectExW for Tahoma is called with charset determined by my standard locale, instead of the Japanese one. That somehow results in the text being treated as encoded in that locale's Windows codepage, instead of cp932 (or is that vice versa ?). -- 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.

2 8

[Bug 53019] New: MusicBee: inconsistent CJK/non-Latin support with Tahoma, no support on any other font.
by WineHQ Bugzilla 22 Nov '24

22 Nov '24

https://bugs.winehq.org/show_bug.cgi?id=53019 Bug ID: 53019 Summary: MusicBee: inconsistent CJK/non-Latin support with Tahoma, no support on any other font. Product: Wine Version: 7.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: activeds Assignee: wine-bugs(a)winehq.org Reporter: v_winebugs(a)outlook.com Distribution: ArchLinux Created attachment 72386 --> https://bugs.winehq.org/attachment.cgi?id=72386 All of the screenshots showcasing the bug, in a .tar.gz file. Tested on wine 7.7 as well as wine-staging 7.7. Running Arch Linux. Font replacements installed via winetricks - allfonts + fakechinese, fakejapanese, fakekorean. When Tahoma is selected as the default font, which is default on new installations of MusicBee in WINE, MusicBee displays CJK and symbols very inconsistently. 新しい日の誕生 by ２８１４ is a good example as not only is Japanese text used, but the artist name uses full-width characters which comes under the symbol part of this bug. The artist and album names are displayed just fine on the left sidebar, tag editor, track listing panel and mostly on the playing track panel. Generally, if there is no formatting on the text, it is displayed. However in the Music Explorer view, as well as playlist views such as Album & Tracks, Albums and Artists, squares are put in the text's place, typically on the portions meant to be formatted like headings (bolded, increased font size). When any other font is used, whether included by the WINE prefix or brought in from the distro, absolutely no font is displayed for those symbols whatsoever. Everywhere that renders fonts on MusicBee will not render any non-Latin symbols whatsoever. In either case, the title on the Playing Tracks panel does not display any non-Latin symbols whatsoever. I've checked the formatting and used the Regular variant of Tahoma. Changing the others on the Playing Tracks panel to Bold will result in squares, changing the size is fine. A workaround is to use a font that has all of the scripts needed for use, such as WenQuanYi Micro Hei for Japanese, Korean (on the font picker as Hangul and Hangul(Johab)) and Chinese (CHINESE_GB2312 and CHINESE_BIG5). As long as it has the relevant scripts, the symbols will be displayed, however since most fonts don't include CJK scripts, WINE/MusicBee has trouble displaying them when those fonts are picked. To make matters worse, due to .NET limitations, MusicBee can only use TrueType fonts, and some fonts result in MusicBee complaining that it's not a valid TrueType font, even though it only displays TrueType fonts in the font picker (Yu Gothic UI was used for this example). When searching for related bugs, I came across this: https://bugs.winehq.org/show_bug.cgi?id=34298#c5 Adding a font that works to the registry changes basically nothing. MusicBee still has trouble consistently rendering CJK and other symbols. -- 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.

1 12