wine-bugs January 2025

wine-bugs@winehq.org

1 participants
669 discussions

[Bug 35981] New: Battlefield: Bad Company 2 Updater has missing glyphs
by wine-bugs＠winehq.org 07 Feb '25

07 Feb '25

http://bugs.winehq.org/show_bug.cgi?id=35981 Bug ID: 35981 Summary: Battlefield: Bad Company 2 Updater has missing glyphs Product: Wine Version: 1.7.16 Hardware: x86 OS: Linux Status: NEW Severity: trivial Priority: P2 Component: fonts Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Created attachment 48100 --> http://bugs.winehq.org/attachment.cgi?id=48100 screenshot In English game locale BFBC2Updater has a normal text, but in Russian isn't. -- 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 9

[Bug 41342] New: Build with winegcc is not reproducible
by wine-bugs＠winehq.org 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=41342 Bug ID: 41342 Summary: Build with winegcc is not reproducible Product: Wine Version: 1.9.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: javier--fqu3sqxsVIm7PkQvPySPMwTV4r0Nxk(a)jasp.net Distribution: --- Building with winegcc is not reproducible because the name of a temporary file is included.[1] The function that creates this file should try char* tmp = strmake("%s%s", prefix, suffix); fd = open(tmp, O_CREAT | O_EXCL, 0600); before mkstemps().[2] About reproducible builds: https://reproducible-builds.org/ [1] https://tests.reproducible-builds.org/debian/dbd/unstable/i386/lmms_1.1.3-5… , look for "spec.". [2] http://source.winehq.org/git/wine.git/blob/HEAD:/tools/winegcc/winegcc.c#l2… -- 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 11

[Bug 39733] New: OpenGL Extensions Viewer 4.1 is not started
by wine-bugs＠winehq.org 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=39733 Bug ID: 39733 Summary: OpenGL Extensions Viewer 4.1 is not started Product: Wine Version: 1.8-rc2 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Infinite loop. If stop last messages are ~~~ fixme:mscoree:ConfigFileHandler_startElement Unknown element L"configSections" in state 2 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"sectionGroup" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"section" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"userSettings" in state 2 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"openglex.Properties.Settings" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"setting" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"value" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"appSettings" in state 2 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"add" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"add" in state 6 fixme:mscoree:ConfigFileHandler_startElement Unknown element L"add" in state 6 fixme:gdiplus:GdipGetLineSpacing ignoring style fixme:gdiplus:GdipGetLineSpacing ignoring style fixme:gdiplus:GdipGetLineSpacing ignoring style fixme:gdiplus:GdipGetLineSpacing ignoring style -- 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 14

[Bug 57711] New: The 32-bit wpcap program has a stack leakage issue
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57711 Bug ID: 57711 Summary: The 32-bit wpcap program has a stack leakage issue Product: Wine Version: 10.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wpcap Assignee: wine-bugs(a)winehq.org Reporter: csumushu(a)126.com Distribution: --- Created attachment 77913 --> https://bugs.winehq.org/attachment.cgi?id=77913 test code I compiled a 32-bit wpcap application using VS2010, and when running this program with Wine, it caused a stack overflow. Therefore, I wrote a test program to print the stack address in the callback function, and I noticed that the address was gradually decreasing. This issue does not occur with the 64-bit program. The test program is included in the attachment. -- 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 10

[Bug 57690] New: .NET Framework 4.8 installer hangs with sync:RtlpWaitForCriticalSection
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57690 Bug ID: 57690 Summary: .NET Framework 4.8 installer hangs with sync:RtlpWaitForCriticalSection Product: Wine Version: 9.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: its.kutepov(a)gmail.com Distribution: --- Hangs with the following error messages starting from 9.17 up to 10.0-rc6: ``` 033c:err:sync:RtlpWaitForCriticalSection section 7BD7A2E0 "../dlls/ntdll/loader.c: loader_section" wait timed out in thread 033c, blocked by 02a0, retrying (60 sec) ``` I tried to install using winetricks and by steps described on appdb.winehq.org. The issue is highly reproducible, I was unable to complete the installation even once. -- 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 56876] New: Paint Tool SAIv2 VirtualAlloc invalid address on commit
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=56876 Bug ID: 56876 Summary: Paint Tool SAIv2 VirtualAlloc invalid address on commit Product: Wine Version: 9.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: cromachina(a)gmail.com Distribution: --- When using Paint Tool SAIv2 (any recent version, Preview.2024.05.22 for example), the program will often start emitting errors when a few files are opened and random scatter brushes are selected (brushes that open bitmap files to draw themselves). After this point, the program can quickly become unstable and inoperable, further opening of files may fail, and attempting to save files in this state may cause file corruption. I've never experienced this issue when using SAI in Windows 10, so I think it is more likely an issue within Wine than SAI itself. What I think is causing the errors: Although the errors seems to be related to files being opened, it seems to be caused by subsequent memory allocations. Checking SAI's error log, it says "!WinError(487): Invalid address." When running with WINDDEBUG=+all, I found that an invalid address error (0x000001E7, 487) is reported after the program attempts to commit a page of memory with VirtualAlloc: For this particular example, the program likely attempted to write to a reserved address 177FFF8, so then a SEH for EXCEPTION_ACCESS_VIOLATION occured. The SEH then attempted to commit 177FFF8 with VirtualAlloc, but it failed, and then GetLastError returned 000001e7 ERROR_INVALID_ADDRESS: 38822.915:0020:01b8:Call KERNEL32.VirtualAlloc(0177fff8,00001000,00001000,00000004) ret=14019f0d2 38822.915:0020:01b8:Ret KERNEL32.VirtualAlloc() retval=00000000 ret=14019f0d2 This should have been a valid address to commit, which should have returned the next lowest page, for example 177f000. The internal call to ntdll.NtAllocateVirtualMemory returned c0000019, which is STATUS_NOT_MAPPED_VIEW. Looking earlier into the log, I can confirm that the region should have indeed been reserved: 38744.422:0020:0024:Call KERNEL32.VirtualAlloc(00000000,00400000,00002000,00000004) ret=1401a0a0e 38744.422:0020:0024:Ret KERNEL32.VirtualAlloc() retval=01380000 ret=1401a0a0e This region 01380000 - 1780000 contains address 177FFF8 (8 bytes from the end of the last page). I could not find any indication that this reserved region is ever freed by VirtualFree. Therefore, I think that this may indicate that the views_tree used by find_view had become damaged somehow: https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/unix/virtual.c#L… I've compressed the massive log file, but it's still too large to attach, so I've uploaded it here: https://mega.nz/file/ET5S1LzY#WyVvta3n4QxeLjmzkyJqWmU5ZdgODWh4jILvNg32_rE -- 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 4

[Bug 55155] New: Telegram can not be run in latest version wine, but ok in wine6.0.4
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=55155 Bug ID: 55155 Summary: Telegram can not be run in latest version wine, but ok in wine6.0.4 Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 398063392(a)qq.com Distribution: --- the Telegram which I used is unpacked from https://updates.tdesktop.com/tx64/tportable-x64.4.8.3.zip -- 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 16

[Bug 57692] New: No context menu in Reason (DAW)
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57692 Bug ID: 57692 Summary: No context menu in Reason (DAW) Product: Wine Version: 10.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: schroedingerscat(a)disroot.org Distribution: --- The context menu in ReasonStudio's DAW Reason is broken. The regression was introduced with v10.0-rc6 as context menus worked fine until Wine v10.0-rc5. To reproduce, following the installation procedure from here (under Additional Notes): https://appdb.winehq.org/objectManager.php?sClass=version&iId=42495 Then after starting the app and finishing the initial configuration dialogues, try to right-click with your mouse anywhere in the application to open the context menu. Nothing will happen. There's also nothing being logged when trying to open the context menu. -- 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 56530] New: Final Fantasy XI Online: Memory leak when Wine is built with CFLAGS="-g -mno-avx".
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=56530 Bug ID: 56530 Summary: Final Fantasy XI Online: Memory leak when Wine is built with CFLAGS="-g -mno-avx". Product: Wine Version: 8.13 Hardware: x86-64 URL: https://web.archive.org/web/20210810150839/http://www. playonline.com/ff11eu/download/media/install_win.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: chiitoo(a)gentoo.org Regression SHA1: c065b4fe0b3622e0c737a4c7c1c514273ad2d8a7 Distribution: --- After c065b4fe0b3 [1], a memory leak can be seen in Final Fantasy XI Online, but only when building with CFLAGS="-g" instead of CFLAGS="-march=znver4 -O2 -pipe -mindirect-branch=thunk -mno-avx" ---- err:d3d:wined3d_debug_callback 01DBBCF8: "GL_OUT_OF_MEMORY in glGetTexImage". ---- Nothing too specific needs to be done, aside from simply logging in to the game, and standing still, which will make the address space fill up in a few minutes (some in-game area requirements may be present, or at least some make it happen faster than others). Thank you! 1. https://source.winehq.org/git/wine.git/commitdiff/c065b4fe0b3622e0c737a4c7c… -- 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 11

[Bug 57766] New: Win3_BIOS most likely should be Win32_BIOS instead
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=57766 Bug ID: 57766 Summary: Win3_BIOS most likely should be Win32_BIOS instead Product: Wine Version: 10.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: depaoli.renzo(a)gmail.com Distribution: --- wine-10.0-rc6/dlls/wbemprox/tests/query.c Line #93 states L"SELECT * FROM Win3_BIOS WHERE NAME <> NULL", It seems likely that this was intended instead L"SELECT * FROM Win32_BIOS WHERE NAME <> NULL", e.g. the line #94 states L"SELECT * FROM Win32_BIOS WHERE NULL = NAME", -- 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 3

← Newer
1
...
17
18
19
20
21
22
23
...
67
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs January 2025