wine-bugs December 2022

wine-bugs@winehq.org

1 participants
3697 discussions

[Bug 31927] New: ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0'
by wine-bugs＠winehq.org 21 Dec '22

21 Dec '22

http://bugs.winehq.org/show_bug.cgi?id=31927 Bug #: 31927 Summary: ws2_32: sock.c fails intermittently - 'Test succeeded inside todo block: GetQueuedCompletionStatus returned 0' Product: Wine Version: 1.5.14 Platform: x86 OS/Version: Linux Status: NEW Keywords: download, testcase Severity: minor Priority: P2 Component: winsock AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Classification: Unclassified Running in a loop for about 15 minutes, I got: sock.c:5385: Test succeeded inside todo block: GetQueuedCompletionStatus returned 0 sock.c:5386: Test succeeded inside todo block: Last error was 64 make: *** [sock.ok] Error 2 -- 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 10

[Bug 54094] New: kernel32:process - test_services_exe() sometimes fails due to an invalid buffer size in Windows
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=54094 Bug ID: 54094 Summary: kernel32:process - test_services_exe() sometimes fails due to an invalid buffer size in Windows Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com test_services_exe() sometimes fails due to an invalid buffer size in Windows: process.c:4962: Test failed: got 0xc0000004 See https://test.winehq.org/data/patterns.html#kernel32:process Where 0xc0000004 == STATUS_INFO_LENGTH_MISMATCH This causes a little bit over one failure per month. I think the failure simply happens when a process is started between the first call to NtQuerySystemInformation(), which returns the buffer size to hold the *array* of SYSTEM_PROCESS_INFORMATION structures, and the time we call it again with that size. Obviously we don't start new processes ourselves so it must be a scheduled task or some equivalent. We should probably loop a couple of times to defend against that. -- 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

[Bug 53941] New: Chicken Tournament crashes on start
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53941 Bug ID: 53941 Summary: Chicken Tournament crashes on start Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dmusic Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 73511 --> https://bugs.winehq.org/attachment.cgi?id=73511 Log file Other issue with directmusic not being implemented completely. -- 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 53625] New: In function ‘get_gnutls_cipher’ ... error: ‘GNUTLS_CIPHER_AES_128_CFB8’ undeclared
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53625 Bug ID: 53625 Summary: In function ‘get_gnutls_cipher’ ... error: ‘GNUTLS_CIPHER_AES_128_CFB8’ undeclared Product: Wine Version: 7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: version2013(a)protonmail.com Distribution: --- Created attachment 73024 --> https://bugs.winehq.org/attachment.cgi?id=73024 log.txt Compiling in distro with: compiler version 4.8.4 # gcc --version glibc 2.19 # ldd --version config line: configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i686 -mtune=i686" Compile error in wine-7.15 In function ‘get_gnutls_cipher’: error: ‘GNUTLS_CIPHER_AES_128_CFB8’ undeclared error: ‘GNUTLS_CIPHER_AES_192_CFB8’ undeclared error: ‘GNUTLS_CIPHER_AES_256_CFB8’ undeclared -- 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

[Bug 53384] New: Hogia Hemekonomi Unexpected error on first start
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53384 Bug ID: 53384 Summary: Hogia Hemekonomi Unexpected error on first start Product: Wine Version: 7.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)jonass.user.lysator.liu.se Distribution: --- Created attachment 72771 --> https://bugs.winehq.org/attachment.cgi?id=72771 Terminal with start of wine, error dialog and application in background. On first start Hogia Hemekonomi tries to determine if this is the first run of the program. If it is, it tries to start another executable called hekintro.exe. hekintro.exe opens a new windows and shows an introduction. This bug gives and Unexpected error dialog instead of the intro window. I have tried bisecting but can not find a conclusive commit. Only that it may be around commit 9b9d818252fe1a47f3ca52d028dc10d52fa33597 Mar 4 14:29:21 2022. Wine 7.1 seems to be fine, 7.4 seems to be bad. Testing on XUbuntu 18.04.6 LTS i686. -- 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 50013] New: MyPhoneExplorer 1.8.15 crashes
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=50013 Bug ID: 50013 Summary: MyPhoneExplorer 1.8.15 crashes Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Created attachment 68435 --> https://bugs.winehq.org/attachment.cgi?id=68435 Backtrace (5.18 Staging) Hello everyone, Download-URL is at: https://fjsoft.at/de/ There is also an AppDB entry: https://appdb.winehq.org/objectManager.php?sClass=version&iId=34110 Installation works fine in a clean prefix with 5.18 (Staging) and the app requires vb6run installed to start it up. However it throws a fatal error. Backtrace is attached. -- 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 13

[Bug 49394] New: CED1401 USB function driver fails to install
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=49394 Bug ID: 49394 Summary: CED1401 USB function driver fails to install Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: usb Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 67461 --> https://bugs.winehq.org/attachment.cgi?id=67461 WINEDEBUG=+wineusb,+setupapi,+ntoskrnl,+plugplay,+pid,+msgbox ./wine winsupp.exe I'm try to test the fix for bug 35903. In order to do so, I compiled wine from source (commit 634cb775c27b61ad6ce1fbe3e9972b0edfa31dcb), and used wine from the build directory. Now the installation of winsupp.exe is failing (this has been working before) with this error: 0020:0024:err:module:__wine_process_init L"Z:\\home\\schloegl\\src\\wineapps\\winsupp.8081a20bbc0c9b99f37b98a823ce07ab25f15e9d.exe" not supported on this system The log file is attached. -- 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

[Bug 53918] New: Building with external PE libraries fails when static libraries are also installed
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53918 Bug ID: 53918 Summary: Building with external PE libraries fails when static libraries are also installed Product: Wine Version: 7.20 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Regression SHA1: 6a912649188a765d0c58e8b26e093fb0c31b3e3d Distribution: --- The basic problem is that winegcc, when passed e.g. "-L/usr/x86_64-w64-mingw32/lib -lvkd3d", looks up that library in the search path, finds libvkd3d.a, and tries to link to it. The mingw-w64 linking process, at least for vkd3d (but presumably others as well), provides both "libvkd3d.a" and "libvkd3d.dll.a". The former is a static library, and the latter is essentially an import library for libvkd3d-1.dll. Normal mingw-w64 gcc, when passed -lvkd3d, links to the latter, according to the search path specified in [1] s.v. "direct linking to a dll". winegcc does not know about .dll.a and hence finds the static library first. This worked before 6a912649 because winegcc would try to find a library ending in ".cross.a", fail to find *any* vkd3d libraries, and just leave the linker argument as "-lvkd3d". Given this, an obvious solution is to teach winegcc about the ld linker path. However, I find myself asking—why are we trying to rewrite the command line at all? Why can't we just let mingw-w64 gcc work by itself? winegcc is, naturally, devoid of any comments, and as far as I can tell the code doesn't actually *do* anything that depends on the library type or path, so I started looking in the git history, but unfortunately was only partly able to answer the question. Here is what I found: * c7a210bc2f27 forces the use of library paths if -mno-cygwin is set (in addition to some other conditions). The commit message specifies that we *can* do this (due to our use of -nodefaultlibs), but doesn't specify why we *need* to do this. Jacek, can you by chance explain? * 33147c947500 forces the use of library paths (sort of) if lib_suffix is set, which makes sense—gcc won't be able to find any libraries if we are overriding lib_suffix. * 870d490eecdb forces the use of library paths for all winelib DLLs, so that "-lfoo" links to "foo/foo.dll". This makes sense, but is also now obsolete—our makefiles pass the direct paths. Or do we want to support winelib users outside of wine including from the build tree? * 006ec80dd5c1 introduces the logic in the first place, forcing the use of library paths for static libraries. This was written by Dimitrie O. Paun, with the comment "For static libs (.a) we need to pass the actual filename to winebuild, not a -l switch." No further explanation is given. Alexandre, can you please shed light on this? [1] https://sourceware.org/binutils/docs-2.39/ld/WIN32.html -- 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 6

[Bug 53623] New: Resident Evil 7 has broken rendering in DX11 mode
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53623 Bug ID: 53623 Summary: Resident Evil 7 has broken rendering in DX11 mode Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: z.figura12(a)gmail.com Regression SHA1: b2087112144ca945d1df9ab9d82ef8a9f6e6d00b Distribution: --- Created attachment 73021 --> https://bugs.winehq.org/attachment.cgi?id=73021 example Using 'dx11_non-rt' branch. -- 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 2

[Bug 53406] New: Had been running 7.10 Fedora version no problem, but today updated to 7.12 broke??
by WineHQ Bugzilla 21 Dec '22

21 Dec '22

https://bugs.winehq.org/show_bug.cgi?id=53406 Bug ID: 53406 Summary: Had been running 7.10 Fedora version no problem, but today updated to 7.12 broke?? Product: Wine Version: 7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikes(a)kuentos.guam.net Distribution: --- Did the dnf update and it was mostly the 7.12 version of wine from Fedora. Upgrade went thru fine, or so I thought. But primary program I use the wine to run is Pegasus Mail. After running it, it came up fine, and had it download new mail. Was 14 new messages, went to view them, but just got a spinning little circle icon. No error message shows, top and ps -ef don't seem to show anything. Had to kill program to close it. Tried different message, but all did the same thing. Restarted machine, same result. Only option I could think of was dnf downgrade wine* That ran fine, but installed wine-core-6.16-1.fc35, thought it would have gone to 7.10 that had been working fine before todays upgrade to 7.12? Since no error shows other than ivy bridge is incomplete, so can't report more than just getting a spinning icon and no response. Have never done a downgrade before, so not sure why it went to 6.16. Just to see what would happen type dnf upgrade wine* and it showed that it would intall that 7.12 version, so I responsed N. Don't know if there is some option I could run to hopefully get more details on what is going on. But after the downgrade the messages view fine. Have it set to using windows 10 option, so not sure if using 8.1 or some other option might make a different. -- 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 5

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 December 2022