December 2021 - Wine-bugs - list.winehq.org

[Bug 25486] New: Lego Stunt Rally: 3d scene is black
by wine-bugs＠winehq.org 02 Jan '22

02 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=25486 Summary: Lego Stunt Rally: 3d scene is black Product: Wine Version: 1.3.9 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: support.intranet(a)libero.it In Lego Stunt Rally 1.0, both in racing and costruction mode, the 3d scene is black, as if no textures were present. Only a few lights are displayed. -- 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 36

[Bug 51263] New: [Regression] Frostpunk crash after updating to Wine wine-6.10 on Fedora
by WineHQ Bugzilla 02 Jan '22

02 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=51263 Bug ID: 51263 Summary: [Regression] Frostpunk crash after updating to Wine wine-6.10 on Fedora Product: Wine Version: 6.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: roidal(a)googlemail.com Distribution: --- Created attachment 70141 --> https://bugs.winehq.org/attachment.cgi?id=70141 STDOUT and STDERR After updating to wine-6.10 frostpunk is crashing before able to create a window. STDOUT is attached. Iam on Fedora 34 with an AMD-GPU. Maybe it is related to Bug https://bugs.winehq.org/show_bug.cgi?id=51244 Let me know if you need more details. -- 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 45505] New: Trying to open PEsS2017 settings.exe
by wine-bugs＠winehq.org 02 Jan '22

02 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=45505 Bug ID: 45505 Summary: Trying to open PEsS2017 settings.exe Product: Wine Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: donnisnoni.tid3(a)gmail.com Distribution: --- Created attachment 61881 --> https://bugs.winehq.org/attachment.cgi?id=61881 some bug when i try to open pes2017 settings.exe I already install directx -- 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 52024] New: App Never Receives Winsock FD_* Messages After FD_ACCEPT
by WineHQ Bugzilla 02 Jan '22

02 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=52024 Bug ID: 52024 Summary: App Never Receives Winsock FD_* Messages After FD_ACCEPT Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: jbrown(a)statslog.com CC: dimesio(a)earthlink.net Distribution: --- Created attachment 71023 --> https://bugs.winehq.org/attachment.cgi?id=71023 Broken +server,+winsock Trace from 6.x I'm using a 32-bit Wine 6.21devel prefix on Ubuntu 20.04.3. I have a custom application written in VB6 that uses the winsock (ws2_32.dll) API to listen for network connections and respond to requests. I use the following winetricks: DISPLAY=:99 winetricks -q vcrun2008 DISPLAY=:99 winetricks -q vcrun2010 DISPLAY=:99 winetricks -q msxml6 DISPLAY=:99 winetricks -q corefonts DISPLAY=:99 winetricks -q vb6run I run the application with the following command line: WINEARCH="win32" WINEDLLOVERRIDES="oleaut32=n" wine RCWebServerTest.exe & NOTE: I've tried both with and without the oleaut32 native override. The application is able to bind OK to 127.0.0.1:8080, but when try to curl to it with the following command: curl http://127.0.0.1:8080 curl is able to connect to the application, but the application does not subsequently respond to the request. Some debugging shows that the I'm receiving an FD_ACCEPT message in my app's socket windowproc, but unexpectedly I receive no other FD_ messages (notably, no FD_READ message). After dumping +server,+winsock debug channels (attached), I see the server's "get_message" and "select" calls are apparently "stuck" in a PENDING state, with many repeated log messages along these lines: 0024: get_message( flags=00000000, get_win=00000000, get_first=00000000, get_last=ffffffff, hw_id=00000000, wake_mask=00000000, changed_mask=00000000 ) 0024: get_message() = PENDING { win=00000000, msg=00000000, wparam=00000000, lparam=00000000, type=0, x=0, y=0, time=00000000, active_hooks=80000001, total=0, data={} } 0024: select( flags=2, cookie=0031ef4c, timeout=infinite, size=8, prev_apc=0000, result={}, data={WAIT,handles={007c}}, context={} ) 0024: select() = PENDING { call={APC_NONE}, apc_handle=0000, context={} } I've tried the exact same app on 5.x versions of Wine and it works as expected - curl connects and receives data from my application. I performed a similar +server,+winsock dump under the working 5.x version, and 2 things that stand out are that the 5.x series performs periodic "flush" calls, and the "get_message" and "select" calls never have a "PENDING" status. For example: 0009: flush( async={handle=0004,event=0000,iosb=0032ee10,user=006414b8,apc=00000000,apc_context=00000000} ) 0009: flush() = 0 { event=00d8 } 0009: select( flags=2, cookie=0032eadc, timeout=infinite, prev_apc=0000, result={}, data={WAIT_ALL,handles={00d8}} ) 0009: select() = 0 { timeout=infinite, call={APC_NONE}, apc_handle=0000 } 0009: get_message( flags=00000001, get_win=00000000, get_first=00000000, get_last=ffffffff, hw_id=00000000, wake_mask=00000000, changed_mask=00000000 ) 0009: get_message() = 0 { win=0001006c, msg=00000804, wparam=000000d4, lparam=00000001, type=6, x=0, y=0, time=a00af81e, active_hooks=80000001, total=0, data={} } The attached working & broken logs are quite large, but if you search for FD_ACCEPT, that's where the curl connection gets accepted, and then the subsequent lines are where the problem is evident in the broken log (or expected behaviour is evident in the working log). At this point I am stumped and not sure what else I can do to get the app working under Wine 6.x, as I believe that there is a bug that is beyond my capabilities to diagnose & fix. Thank you in advance for any help, and If there's any additional information needed from me, I will provide 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 24

[Bug 51063] New: Version changes in Wine 6.7 break Spitfire Audio plugins
by WineHQ Bugzilla 02 Jan '22

02 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=51063 Bug ID: 51063 Summary: Version changes in Wine 6.7 break Spitfire Audio plugins Product: Wine Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: mail(a)robbertvanderhelm.nl Regression SHA1: 04a8213ba9e3b8aa1f980d19b240929948da5abe Distribution: --- The LABS and BBC Symphony Orchestra Discover plugins can no longer find their sample libraries as of Wine 6.7, and they'll show a generic 'Error #1: Something went wrong' error message instead. After bisecting, it seems like commit 04a8213 caused this regression. That commit changes WINE_FILEVERSION and WINE_PRODUCTVERSION to match Windows 10 instead of Windows 7. There aren't any new or different warnings or fixmes printed between Wine 6.6 (where those plugins did work correctly) and Wine 6.7 (where they don't), but I've only tested that with WINEDEBUG's defaults. Reverting the commit on the master branch makes the plugins work again as expected. I tested this with the 64-bit VST3 versions of BBCSOD 1.1.9 and LABS 1.3.7 under yabridge 3.1.1 (or, well, the version that's to become 3.1.1). https://source.winehq.org/git/wine.git/commit/04a8213ba9e3b8aa1f980d19b2409… -- 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 20

[Bug 49401] New: Desperados 3 suffering from wrong colors
by WineHQ Bugzilla 02 Jan '22

02 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=49401 Bug ID: 49401 Summary: Desperados 3 suffering from wrong colors Product: Wine Version: 5.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 67474 --> https://bugs.winehq.org/attachment.cgi?id=67474 Log Output on High Details No matter if you play on high details or low details, The Desperados 3 Release has a purple roads and other graphic curiosities during the tutorial level -- 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 25462] New: Unable to break while remote debugging with VS2008
by wine-bugs＠winehq.org 02 Jan '22

02 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=25462 Summary: Unable to break while remote debugging with VS2008 Product: Wine Version: 1.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jdluzen(a)gmail.com I've got the Visual Studio Remote Debugger working with breakpoints, but not with forcing the process to pause. It immediately exits with "Trace/breakpoint trap." http://bugs.winehq.org/show_bug.cgi?id=20534 might be related. -- 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 13

[Bug 52199] New: Grand Theft Auto Vice City doesn't start.
by WineHQ Bugzilla 02 Jan '22

02 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=52199 Bug ID: 52199 Summary: Grand Theft Auto Vice City doesn't start. Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jon9097(a)gmail.com Distribution: --- Grand Theft Auto Vice City and GTA 3 doesn't start. -- 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 52312] New: page fault on read access to 0xffffffffffffffff
by WineHQ Bugzilla 02 Jan '22

02 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=52312 Bug ID: 52312 Summary: page fault on read access to 0xffffffffffffffff Product: Wine Version: 6.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nidpick(a)nidpick.de Distribution: --- Created attachment 71473 --> https://bugs.winehq.org/attachment.cgi?id=71473 backtrace after starting the wine configuration Every time I start an wine application I get an error-report. However I then start the application. This happens even when I only start the Wine Configuration. See attached backtrace.txt -- 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 13515] New: Outcast demo: tooltips are drawn behind the window
by wine-bugs＠winehq.org 02 Jan '22

02 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=13515 Summary: Outcast demo: tooltips are drawn behind the window Product: Wine Version: 1.0-rc2 Platform: Other OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nowic(a)wenner.ch Created an attachment (id=13436) --> (http://bugs.winehq.org/attachment.cgi?id=13436) tooltip bug screenshot When I start the demo in the 'virtual desktop' the tooltips of the configuration menu are drawn behind the actual window. If I run the demo in full screen mode the tooltips are drawn correctly. Download: http://www.jeuxvideopc.com/demo/82-outcast.php -- 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 9