wine-bugs July 2024

wine-bugs@winehq.org

1 participants
1483 discussions

[Bug 39576] New: Sound in StarCraft 2 breaks after
by wine-bugs＠winehq.org 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=39576 Bug ID: 39576 Summary: Sound in StarCraft 2 breaks after Product: Wine Version: 1.7.54 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolAflash(a)kolahilft.de Distribution: --- At least since StarCraft 2 Legacy of the void (released 2015-11-10) and Wine 1.7.52 (currently 1.7.54) I'm experiencing sound issues. I'll try to find out some more about it in the next weeks... The problem: After playing a while, especially in missions with many units, the sound becomes very strange. Suddenly there is a lot of loud noise and voices are spoken very fast. Playback is probably about two times the speed of normal. I can temporarily let the sound return to normal, by opening the StarCraft 2 sound options and changing the number of sound channel to any other value (which value doesn't seems to be important). Sometimes (very rarely) the sound suddenly returns to normal without any further actions. I tried setting the value "default-fragment-size-msec" in the file /etc/pulse/daemon.conf to different value. Afterwards I always did "killall pulseaudio" and restartet Wine/StarCraft. But that didn't helped. Values I tried: 5, 100, 400 -- 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 18

[Bug 56703] New: Crash when installing Rhinoceros 8.6
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=56703 Bug ID: 56703 Summary: Crash when installing Rhinoceros 8.6 Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: daniel.lawrence.lu(a)gmail.com Distribution: --- Created attachment 76490 --> https://bugs.winehq.org/attachment.cgi?id=76490 backtrace When installing Rhinoceros 8.6 in a clean wineprefix where I only installed dotnet48 (using winetricks), the installer crashes at the end with 03f8:err:msi:__wine_msi_call_dll_function Custom action (L"C:\\users\\dllu\\Temp\\msi6b88.tmp":"AddMachineCertificate") caused a page fault: 0xc0000005 Using wine-9.9-50-gd41a1f0183f but also tested with wine-staging-9.8 and wine-9.8. -- 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 56559] New: wine is unable to launch a .exe that just downloads a file
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=56559 Bug ID: 56559 Summary: wine is unable to launch a .exe that just downloads a file Product: Wine Version: 9.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gerard.labadie(a)sysgroup.fr Distribution: --- all the info is in https://forum.winehq.org/viewtopic.php?t=38779 I want to launch iologo-launcher that is avalable at https://cellar-c2.services.clever-cloud.com/iologo-app/launcher2/5/iologo-l… and wine iolog-launcher.exe does nothing on Windows this file just downloads iologo_setup.exe and then I am able to launch iologo_setup.exe with wine qwertymnb offered a hack and said it is a wine bug [quote]diff --git a/dlls/cryptnet/cryptnet_main.c b/dlls/cryptnet/cryptnet_main.c index 7768e9e5bd3..e23f63f86e7 100644 --- a/dlls/cryptnet/cryptnet_main.c +++ b/dlls/cryptnet/cryptnet_main.c @@ -2304,7 +2304,7 @@ typedef struct _OLD_CERT_REVOCATION_STATUS { BOOL WINAPI CertDllVerifyRevocation(DWORD dwEncodingType, DWORD dwRevType, DWORD cContext, PVOID rgpvContext[], DWORD dwFlags, PCERT_REVOCATION_PARA pRevPara, PCERT_REVOCATION_STATUS pRevStatus) -{ +{return 1; DWORD error = 0, i; FILETIME now; LPFILETIME pTime = NULL; [/quote] my wine version [code]$ wine --version wine-9.6 [/code] -- 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 7

[Bug 56658] New: When using Kosugi for vertical writing, some punctuation marks are not placed correctly.
by WineHQ Bugzilla 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=56658 Bug ID: 56658 Summary: When using Kosugi for vertical writing, some punctuation marks are not placed correctly. Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 Assignee: wine-bugs(a)winehq.org Reporter: sagawa.aki+winebugs(a)gmail.com Distribution: Ubuntu Created attachment 76433 --> https://bugs.winehq.org/attachment.cgi?id=76433 Vertical writing comparison (Orange squares added for emphasis) When using Kosugi, a Japanese font designed by MOTOYA[1], for vertical writing, some punctuation marks are not placed correctly. Ume Gothic[2], another Japanese font, doesn't have this issue. See the attachment for details. Steps to Reproduce: 1. Install Kosugi font, Kosugi-Regular.ttf, to your font directory. SHA1(Kosugi-Regular.ttf) = fb02b5f57e8652a1fd499195d7070bafd58e16e2 2. Download Mery Text Editor Ver 3.7.1[3] and unzip it. SHA1(MeryPortable-3.7.1.zip) = 8355bbf8919bade31bf333731167b48cb47d9e5e 3. Launch Mery editor with Japanese locale, i.e. % LANG=ja_JP.UTF-8 wine Mery.exe 4. Choose Kosugi font in ツール(T) - オプション(O) - 表示 - フォント(F). 5. Enable vertical writing view at 表示(V) - 縦書き(V). 6. Copy and paste the following Japanese text: あのイーハトーヴォのすきとおった風、夏でも底に冷たさをもつ青いそら、うつくしい森で飾られたモリーオ市、郊外のぎらぎらひかる草の波。 Actual results: "。" and "、" are placed in the lower left hand corner of the square. See the left side of the attached image, Kosugi. Expected results: "。" and "、" are placed in the upper right hand corner of the square. See the right side of the attached image, Ume Gothic. [1] https://fonts.google.com/specimen/Kosugi [2] https://ja.osdn.net/projects/ume-font/wiki/FrontPage [3] https://www.haijin-boys.com/download/MeryPortable-3.7.1.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 7

[Bug 46702] New: GNUTLS_CURVE_TO_BITS not found
by wine-bugs＠winehq.org 07 Feb '25

07 Feb '25

https://bugs.winehq.org/show_bug.cgi?id=46702 Bug ID: 46702 Summary: GNUTLS_CURVE_TO_BITS not found Product: Wine Version: 4.2 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Using latest gnutls3.6.6 I got compilation error ~~~ Undefined symbols for architecture i386: "_GNUTLS_CURVE_TO_BITS", referenced from: _key_asymmetric_generate in gnutls.o ld: symbol(s) not found for architecture i386 clang: error: linker command failed with exit code 1 (use -v to see invocation) winegcc: clang failed make[1]: *** [bcrypt.dll.so] Error 2 make: *** [dlls/bcrypt] Error 2 -- 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 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 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

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 July 2024