wine-bugs April 2022

wine-bugs@winehq.org

1 participants
3575 discussions

[Bug 14831] New: ws2_32: sock.ok fails in Solaris, but not Linux
by wine-bugs＠winehq.org 28 Jan '23

28 Jan '23

http://bugs.winehq.org/show_bug.cgi?id=14831 Summary: ws2_32: sock.ok fails in Solaris, but not Linux Product: Wine Version: 1.1.2 Platform: PC OS/Version: Solaris Status: NEW Keywords: testcase Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com austin@opensolaris:~/wine-git/dlls/ws2_32/tests$ make testclean ; wineserver -k ; rm -rf ~/.wine ; make sock.ok rm -f protocol.ok sock.ok ../../../tools/runtest -q -P wine -M ws2_32.dll -T ../../.. -p ws2_32_test.exe.so sock.c && touch sock.ok wine: created the configuration directory '/export/home/austin/.wine' err:iphlpapi:getNumWithOneHeader Unable to open '/proc/net/route' to count entries! err:iphlpapi:getRouteTable unimplemented! Could not load Mozilla. HTML rendering will be disabled. sock.c:947: Test failed: get/setsockopt(SO_RCVTIMEO) failed error: 10042 sock.c:955: Test failed: get/setsockopt(SO_SNDTIMEO) failed error: 10042 err:iphlpapi:getNumWithOneHeader Unable to open '/proc/net/route' to count entries! err:iphlpapi:getRouteTable unimplemented! sock.c:1258: Test failed: Failed to create socket: 10043 sock.c:1662: Test succeeded inside todo block: select should not return any socket handles sock.c:1663: Test succeeded inside todo block: FD should not be set sock.c:1664: Test succeeded inside todo block: FD should not be set sock.c:1688: Test failed: closesocket did not wakeup select sock.c:1765: Test failed: closesocket did not wakeup accept +winsock attached -- 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 15

[Bug 52772] New: winetricks wmp9 fails to install (kernel32 version string doesn't match windows version)
by WineHQ Bugzilla 28 Jan '23

28 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52772 Bug ID: 52772 Summary: winetricks wmp9 fails to install (kernel32 version string doesn't match windows version) Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: NEW Keywords: download, Installer, regression Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Regression SHA1: 04a8213ba9e3b8aa1f980d19b240929948da5abe Distribution: --- After: commit 04a8213ba9e3b8aa1f980d19b240929948da5abe Author: Arkadiusz Hiler <ahiler(a)codeweavers.com> Date: Tue Apr 20 14:38:09 2021 +0300 kernel32: Update version to Win 10. This fixes the game Evil Genius 2 complaining about unsupported OS. Signed-off-by: Arkadiusz Hiler <ahiler(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> `winetricks wmp9` no longer installs; instead an error dialog saying that <= WINXP is required: 0124:trace:text:DrawTextExW L"This version of Windows Media Player can be installed only on Windows 98 Second Edition, Windows Millennium Edition, Windows 2000, Windows XP, and Windows .NET Server.", -1, [(0,0)-(237,52)] 00000850 winetricks is setting the windows version of the wineprefix to winxp before installing, but it seems that the installer is checking the kernel32 version strings, and failing to install as a result. Still present in wine-7.5-175-g0de8d01b09b, reverting the patch allows the installer to proceed. I'm not sure what we can do here. Currently the version string is hardcoded regardless of what version of windows we're reporting. I'd guess either we need to allow overriding the string/shipping different resource files for different reported windows versions, or call this a WONTFIX? -- 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 52681] New: Google Chrome Stopped working after 7.2
by WineHQ Bugzilla 28 Jan '23

28 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52681 Bug ID: 52681 Summary: Google Chrome Stopped working after 7.2 Product: Wine-staging Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ndk+whq(a)esperanca.biz CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hi! I have been using Google Chrome Portable for some time now. It was working with some options (--no-sandbox) right until wine-staging-7.3. It stopped starting after 7.3. The installation process from portableapps is smooth, it just does not want to start (no 'usual' black screen, just fails starting). I have tried to use old wine directory, new wine directory, installed corefonts as someone suggested in some of the bugs, etc. I also have tried to use wine-staging-7.4 with no luck. After I downgraded back to 7.2 - chrome started working again with --no-sandbox. The system: the latest Gentoo x64. Video card: AMD Radeon 480 (amdgpu Xorg driver). Command: WINEPREFIX=/path/to/wine wine /path/to/chrome --no-sandbox Expected Behavior (works until wine-staging-7.3): Chrome starts and is usable Actual Behavior (wine-staging-7.3; wine-staging-7.4): Chrome fails to start. Let me know if there are any debug info is needed (preferrably which options to enable for WINEDEBUG). -- 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 52567] New: 16-bit version of Project Pluto Guide 8.0 crashes on start with division by zero exception
by WineHQ Bugzilla 28 Jan '23

28 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52567 Bug ID: 52567 Summary: 16-bit version of Project Pluto Guide 8.0 crashes on start with division by zero exception Product: Wine Version: 7.1 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 71888 --> https://bugs.winehq.org/attachment.cgi?id=71888 Console output Steps to reproduce: 1. Run `wine setup16.exe` 2. Select "Windows 3.1 software (16 bit)" 3. Run `cd ~/.wine/drive_c/GUIDE8 && wine guide8a.exe` Console output 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 6

[Bug 51427] New: CaptureAge crashes on startup
by WineHQ Bugzilla 26 Jan '23

26 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=51427 Bug ID: 51427 Summary: CaptureAge crashes on startup Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: raphael.nestler(a)gmail.com Distribution: --- Created attachment 70280 --> https://bugs.winehq.org/attachment.cgi?id=70280 Console output of wine CaptureAge (https://appdb.winehq.org/objectManager.php?sClass=version&iId=39970) crashes on startup. After checking for updates it is just showing a white window before crashing. My System ArchLinux wine 6.12 from the ArchLinux repositories You can download CaptureAge from https://captureage.com/cade -- 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 43188] New: Crash when accessing File Open dialog
by wine-bugs＠winehq.org 26 Jan '23

26 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=43188 Bug ID: 43188 Summary: Crash when accessing File Open dialog Product: Wine Version: 2.9 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: ph.schaefe(a)gmail.com Each time I use any of my windows programs with wine, and click the "Open File" menu item (or the "Open File ..." button) to get the 'file open dialog', the program crashes. This is consistent in all the windows programs I use. My version of Wine-devel seems up to date though, as I just did both "port upgrade wine-devel" and "port upgrade winetricks"on the console and it didn't upgrade anything. err:module:DelayLoadFailureHook failed to delay load comctl32.dll.HIMAGELIST_QueryInterface wine: Call from 0x7b42965e to unimplemented function comctl32.dll.HIMAGELIST_QueryInterface, aborting wine: Unimplemented function comctl32.dll.HIMAGELIST_QueryInterface called at address 0x7b42965e (thread 0009), starting debugger... Unhandled exception: unimplemented function comctl32.dll.HIMAGELIST_QueryInterface called in 32-bit code (0x7b42965e). -- 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 20

[Bug 38886] New: AArch64 platforms: ABI Problems wrt varargs (needs arm64 specific __builtin_ms_va_list)
by wine-bugs＠winehq.org 26 Jan '23

26 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=38886 Bug ID: 38886 Summary: AArch64 platforms: ABI Problems wrt varargs (needs arm64 specific __builtin_ms_va_list) Product: Wine Version: 1.7.46 Hardware: aarch64 URL: http://go.microsoft.com/fwlink/p/?LinkId=536682 OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nerv(a)dawncrow.de CC: focht(a)gmx.net, nerv(a)dawncrow.de Distribution: --- Hi, running e.g. makecat.exe or midl.exe gives backtraces which suggest varargs problems. relevant part: (stripped) Backtrace: =>0 0x0000007f84d4aa04 raise_segv_exception(rec=0x7f83e8fa18, context=0x7f83e8f908) in ntdll (0x0000007f83e8fab0) 1 0x0000007f83d65864 pf_printf_w+0x8cb(pf_puts=0x7f83d61b18, puts_ctx=0x7f83e8fc70, fmt=<is not available>, locale=<is not available>, positional_params=0, invoke_invalid_param_handler=0x740020, pf_args=0x78003000200068, args_ctx=0x2d0020003a0000, valist=0x7f83e8fcb0) in msvcrt (0x0000007f83e8fab0) 2 0x0000007f83d65864 pf_printf_w+0x8cb(pf_puts=0x7f83d67ec0, puts_ctx=0x7f83e8fc70, fmt=<is not available>, locale=<is not available>, positional_params=0, invoke_invalid_param_handler=0, pf_args=0x7f83d617d8, args_ctx=0x0(nil), valist=0x7f83e8fcc8) in msvcrt (0x0000007f83e8fac0) 3 0x0000007f83d65864 pf_printf_w+0x8cb(pf_puts=0x7f836822c0, puts_ctx=0x0(nil), fmt=<is not available>, locale=<is not available>, positional_params=0x40020000, invoke_invalid_param_handler=0x7f, pf_args=0x140020000, args_ctx=0x140020000, valist=0x7f84280910) in msvcrt (0x0000007f83e8fc50) 4 0x0000007f83d67ec0 MSVCRT_vsnwprintf+0x47(str=<is not available>, len=<is not available>, format=<is not available>, valist={__stack=0x7f836819f0, __gr_top=0x140010170, __vr_top=0x7f8428071c, __gr_offs=0x83681a28, __vr_offs=0x7f}) in msvcrt (0x0000007f83e8fc80) 5 0x0000000140012328 in makecat (+0x12327) (0x0000007f83e8fcb0) 6 0x00000001400123b0 in makecat (+0x123af) (0x0000007f83e8fcb0) uuidgen.exe -i this generates a different path which involves MSVCRT_vsnprintf, pf_printf_a and pf_handle_string_a -- 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 43287] New: Farming Simualtor 17
by wine-bugs＠winehq.org 24 Jan '23

24 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=43287 Bug ID: 43287 Summary: Farming Simualtor 17 Product: Wine Version: 2.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: sascha.spaces(a)yandex.ru Distribution: --- Created attachment 58629 --> https://bugs.winehq.org/attachment.cgi?id=58629 Backtrace Farming Simulator 17 does not start. The log is here. I'm from Russia and use google translator. There may be errors in the text. closed the game for abit but when i got back and tried playing it said could not init 3d system shader model is required and this is confusing me since a just played it and i check if anything needed a driver update. -- 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 50779] New: winegstreamer is leaking something
by WineHQ Bugzilla 24 Jan '23

24 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=50779 Bug ID: 50779 Summary: winegstreamer is leaking something Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- A rough summary of the problem and things said on chat. Awhile ago a thing, that had been working reasonably well for quite a few years (with exception of a short period when code changes made the music stop looping), has began to randomly freeze to a point that you'd needed to wait for wm's kill dialog to appear after trying to close the main window. The messages in the console were saying something about being unable to create thread due to running out of resources. The freezes usually took a quite a bit of time, but didn't seem to have any obvious trigger. As far as free memory went, the situation was still fine at such time, but zf suggested it was an address space problem. Forcibly setting the executable to LARGE_ADDRESS_AWARE gave it more running time, but eventually seem to have resulted in a whole system freeze. As such, I was once put into realm of wild ass guesses and even crazier attempted solutions. So, I took a gamble and removed gst_object_ref calls from mpeg_audio_parser_init_gst and wave_parser_init_gst first. This didn't seem to have any effect. Then I've removed the last gst_object_ref - one in pad_added_cb. This resulted in a flood of 'gst_object_unref: assertion '((GObject *) object)->ref_count > 0' failed', yet after running for quite awhile the freeze is yet to happen. Now, this is far from conclusive, as we're trying to literally prove a negative here, but it would align well with the fact that free memory used at the time of freeze isn't all that significant. I'm not sure when the problem began. I think it was somewhere between 5.22 and 6.1 (though only the upper bound being definite). -- 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 35

[Bug 26715] New: Win1.0 executable triggers Dosbox
by wine-bugs＠winehq.org 21 Jan '23

21 Jan '23

http://bugs.winehq.org/show_bug.cgi?id=26715 Summary: Win1.0 executable triggers Dosbox Product: Wine Version: 1.3.17 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: spammis(a)spam.la $ wine paint This seems to be a very old (pre-3.0) Windows executable. Expect crashes, especially if this is a real-mode binary ! DOSBox version 0.74 Copyright 2002-2010 DOSBox Team, published under GNU GPL. --- CONFIG:Loading primary settings from config file /home/user/.wine/dosdevices/c:/users/user/Temp/cfg1bc1.tmp MIXER:Got different values from SDL: freq 44100, blocksize 512 ALSA:Can't subscribe to MIDI port (65:0) nor (17:0) MIDI:Opened device:none $ The executable (paint/PAINT.EXE) is the Windows 1.0 version of Paint. Wine properly recognises it as a "very old" Windows executable, but after doing that, Wine thinks that it is a DOS executable and tries to launch Dosbox. Dosbox gives the usual message: "This program requires Microsoft Windows." The lines about the old executable come from Wine while the rest of the lines come from Dosbox. -- 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 17

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