wine-bugs September 2023

wine-bugs@winehq.org

1 participants
2283 discussions

[Bug 55557] New: wpcap:wpcap crashes on macOS
by WineHQ Bugzilla 02 Sep '24

02 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=55557 Bug ID: 55557 Summary: wpcap:wpcap crashes on macOS Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: wpcap Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com wpcap:wpcap crashes on macOS: wpcap.c:368: lib version wpcap.c:369: supports PCAP_MMAP_32BIT: no Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit code (0x000002c74cd410). See https://test.winehq.org/data/patterns.html#wpcap:wpcap The crash is systematic and only happens macOS (see Remi's rbernon-macos-* cloud test machines). The issue is probably that Wine is being compiled against macOS' pcap library which is too old. Using a newer library would require installing it with something like Homebrew and then making sure Wine can find and use it. So there are two things to do: * Detect cases when the pcap library is too old and skip the tests accordingly. * Check if installing a newer pcap library on the macOS test machines is feasible. -- 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 55263] New: Boulder Remake doesn't recognise arrow keys (other keys work)
by WineHQ Bugzilla 31 Aug '24

31 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=55263 Bug ID: 55263 Summary: Boulder Remake doesn't recognise arrow keys (other keys work) Product: Wine Version: 8.11 Hardware: x86-64 URL: https://home.deds.nl/~bremake/download.htm OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: skorohodov4219(a)gmail.com Distribution: --- Created attachment 74879 --> https://bugs.winehq.org/attachment.cgi?id=74879 terminal output (i launch the game, load a level, start the game, attempt to move, then quit) OS: Manjaro Linux x86_64 Kernel: 6.1.38-1-MANJARO CPU: Intel i5-2320 (4) @ 3.000GHz GPU: NVIDIA GeForce GTX 550 Ti (using the proprietary driver) When you launch the game executable, load a level, then start the game, it won't let you move around with arrow keys and you'll stay in place. Note that other hotkeys, like loading levels with L or watching demos with D, still work. Btw, is that still minor? No movement makes the game unplayable but it's not crashing because of 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 5

[Bug 32619] New: Tom Clancy's Rainbow Six: Lockdown can't save a game (directory not created)
by wine-bugs＠winehq.org 31 Aug '24

31 Aug '24

http://bugs.winehq.org/show_bug.cgi?id=32619 Bug #: 32619 Summary: Tom Clancy's Rainbow Six: Lockdown can't save a game (directory not created) Product: Wine Version: 1.5.20 Platform: x86 URL: http://www.fileplanet.com/160005/160000/fileinfo/Tom-C lancy%27s-Rainbow-Six:-Lockdown-Demo OS/Version: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Classification: Unclassified Created attachment 43045 --> http://bugs.winehq.org/attachment.cgi?id=43045 terminal output Normally the game should perform an autosave when starting the first mission, and it should allow you to perform a manual save anytime in a mission. Neither of them work in Wine. 1. After performing a manual save in the game, a 'save successful' message is shown on the screen, however, if I open the <Load game> menu, it is empty. 2. When the player dies there is an option to restore the last saved game: clicking on this option results in a crash as can be seen in the attached log file. The demo version doesn't let you save the game, but it does perform an autosave, thus the crash can be reproduced with the demo too. Here's how: 1. install the demo, the game needs native d3dx9_36 and dxdiagn (bug #32163). 2. start the demo with Lockdown.exe, skip the intros. In the menu choose <Single Player> - <Start Mission> and wait until the game is loaded. 3. press '4' to instruct teammates to stay back. There will be some bad guys around the corner, step to them without shooting so the player dies pretty soon. 4. the menu with statistics appears, click on <Load Last Save>...the game crashes at this point. There's nothing serious in the terminal, the game's own log file contains: [ERROR | IkeStateMgr::SaveGame | 735] Could not open file c:/program files/ubisoft/red storm entertainment/rainbow six lockdown demo/data/save/game/autosave.sav This directory structure does exist in Wine: C:/Program Files/Ubisoft/Red Storm Entertainment/Rainbow Six Lockdown Demo/data/save Inside ../save there should be a /game directory which contains the saved games. This directory (as well as an autosave.sav) should be created when you start the first mission. For some reason the /game directory is not created in Wine. Workaround: you have to manually create the /game directory before starting the game the first time. Saving/loading will work from then on. -- 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

[Bug 54372] New: World in Conflict crashes due to missing SM1 'cast' handling
by WineHQ Bugzilla 30 Aug '24

30 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=54372 Bug ID: 54372 Summary: World in Conflict crashes due to missing SM1 'cast' handling Product: vkd3d Version: 1.6 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: hlsl Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Distribution: --- Split off from bug 41310. 0024:err:d3dcompiler:D3DCompile2 Shader log: 0024:err:d3dcompiler:D3DCompile2 <anonymous>:7:1: E5017: Aborting due to not yet implemented feature: SM1 "cast" expression. 0024:err:d3dcompiler:D3DCompile2 -- 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 31078] New: Need For Speed Hot Pursuit (2010) performance is unacceptable
by wine-bugs＠winehq.org 30 Aug '24

30 Aug '24

http://bugs.winehq.org/show_bug.cgi?id=31078 Bug #: 31078 Summary: Need For Speed Hot Pursuit (2010) performance is unacceptable Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: vanuan(a)gmail.com Classification: Unclassified After fixing the crash http://bugs.winehq.org/show_bug.cgi?id=31031 I was able to run NFS11 (via Launcher.exe). The performance, however, is unacceptable. Running WINEDEBUG=fps reveals 5 fps on car selection screen. Setting UseGLSL to disabled makes it 6 fps. AlwaysOffsceen=enabled makes it 4 fps. When actually playing the game I see a mere 4 fps when UseGLSL=disabled and minimal settings. trace:fps:swapchain_gl_present 0x15e280 @ approx 4.35fps trace:fps:glxdrv_SwapBuffers @ approx 4.52fps, total 14.99fps trace:fps:swapchain_gl_present 0x15e280 @ approx 4.52fps trace:fps:glxdrv_SwapBuffers @ approx 4.45fps, total 14.96fps trace:fps:swapchain_gl_present 0x15e280 @ approx 4.45fps trace:fps:glxdrv_SwapBuffers @ approx 4.52fps, total 14.93fps trace:fps:swapchain_gl_present 0x15e280 @ approx 4.52fps trace:fps:glxdrv_SwapBuffers @ approx 4.39fps, total 14.90fps trace:fps:swapchain_gl_present 0x15e280 @ approx 4.39fps trace:fps:glxdrv_SwapBuffers @ approx 4.42fps, total 14.87fps trace:fps:swapchain_gl_present 0x15e280 @ approx 4.42fps trace:fps:glxdrv_SwapBuffers @ approx 4.29fps, total 14.85fps trace:fps:swapchain_gl_present 0x15e280 @ approx 4.29fps trace:fps:glxdrv_SwapBuffers @ approx 3.79fps, total 14.81fps trace:fps:swapchain_gl_present 0x15e280 @ approx 3.79fps trace:fps:glxdrv_SwapBuffers @ approx 3.85fps, total 14.78fps trace:fps:swapchain_gl_present 0x15e280 @ approx 3.85fps I have nvidia GeForce 8600 which is enough according to http://www.game-debate.com/games/index.php?g_id=1099&game=Need%20for%20Spee… Appreciate any suggestions on improving the game performance. -- 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 55476] New: Unhandled exception: page fault on read access to 0x0000000000000010 in 64-bit code (0x000000073586a3).
by WineHQ Bugzilla 30 Aug '24

30 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=55476 Bug ID: 55476 Summary: Unhandled exception: page fault on read access to 0x0000000000000010 in 64-bit code (0x000000073586a3). Product: Wine Version: 8.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: masterweb801(a)gmail.com Distribution: Debian Created attachment 75038 --> https://bugs.winehq.org/attachment.cgi?id=75038 Wine had given this backtrace file. I am installing my own application. I build it with python and made it executable using pyinstaller. Then created MSI Installer of it using Advanced Installer. Then I installed it with wine on Debian 12. It installed but when I open it up, it throws an error. But this gives no error in Windows 10. I have attached some files related this error. -- 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 54656] New: The winscard tests are not run on the GitLab CI
by WineHQ Bugzilla 30 Aug '24

30 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=54656 Bug ID: 54656 Summary: The winscard tests are not run on the GitLab CI Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winscard Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The winscard tests are not run on the GitLab CI: winscard=dll is missing See the gitlab-debian-* Linux results on: http://winetest.dolphin/data/tests/winscard:winscard.html I'm putting this as a Wine bug rather than a Wine GitLab one because I think the fix is to update the tools/gitlab/image.docker file. Also I'd argue this is a regression introduced by the commit that added the dependency on libpcsclite because the Docker image update should have been made there. commit 8490c43f38e306fef7b5fed3ffcb256efd73af58 Author: Hans Leidekker <hans(a)codeweavers.com> AuthorDate: Thu Feb 16 09:56:12 2023 +0100 winscard: Implement SCardEstablish/ReleaseContext() on top of libpcsclite. -- 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 14

[Bug 52592] New: MilkyTracker does not work: no valid waveout devices.
by WineHQ Bugzilla 28 Aug '24

28 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=52592 Bug ID: 52592 Summary: MilkyTracker does not work: no valid waveout devices. Product: Wine Version: unspecified Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: carlo.bramix(a)libero.it Distribution: --- MilkyTracker is an multi-platform music application for creating .MOD and .XM module files. https://github.com/milkytracker/MilkyTracker Unfortunately, it doesn't work on WINE because it cannot open any waveout device. Sources of MilkyTracker do these actions: 1) waveOutOpen(&hwo, WAVE_MAPPER, &format, 0, 0, CALLBACK_NULL); This call is a success and it returns a valid handle. 2) waveOutGetID(hwo,(LPUINT)&waveOutID); This call also returns success and it returns a value of 63 into "waveOutID". BUT THIS IS WRONG. "waveOutID" should be equal to WAVE_MAPPER, which equal to -1, as you can see in point (1). 3) waveOutGetDevCaps((UINT)waveOutID, &waveoutcaps, sizeof(waveoutcaps)); As result, this call to waveOutGetDevCaps() fails with return value of MMSYSERR_BADDEVICEID. Here there is the point where there is the code that I'm talking about: https://github.com/milkytracker/MilkyTracker/blob/4f97b7011b20519890e30368e… The cause of the trouble is the way the function waveOutGetID() is implemented. waveOutGetID() calls WINMM_GetDeviceFromHWAVE(). And WINMM_GetDeviceFromHWAVE() calls WINMM_DecomposeHWAVE() Into WINMM_DecomposeHWAVE(), there are these lines: ULONG32 l = HandleToULong(hwave); *device_index = l & 0xFF; But this is wrong, because *device_index will be never able to return -1 that is the value for WAVE_MAPPER. -- 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 15

[Bug 48068] New: Mostly black window in Epic Games Launcher
by WineHQ Bugzilla 27 Aug '24

27 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=48068 Bug ID: 48068 Summary: Mostly black window in Epic Games Launcher Product: Wine Version: 4.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: michelle(a)iheartmichelle.com Distribution: --- Created attachment 65617 --> https://bugs.winehq.org/attachment.cgi?id=65617 Output of % wine {Prefix}/drive_c/Program Files (x86)/Epic Games/Launcher/Portal/Binaries/Win64/EpicGamesLauncher.exe -SkipBuildPatchPrereq I have installed the Epic Games Launcher. It opens up with a mostly black window. However, the app draws its own window controls, such as minimize and close, and those work. Also, there's a "Settings" icon in the corner. When I click that, it takes me to a settings screen which appears to work. However, the rest of the window is black and I cannot install the untitled goose game, as I so desperately want to do. I'm using wine 4.19-staging. The Epic Games Launcher version ... well, I have a story about that: While I was gathering info for this bug report, I started the launcher and this time, the "Settings" icon had a dot on it. So I clicked the Settings icon, and it said there was a new version of the launcher and I should click here to install the new version and restart the launcher, and I did and it worked. So at least that much of the app is working. Anyway, the version (which is visible from the Settings screen) is now 10.9.1-10088168+++Portal+Release-Live I don't think this is related to the ancient #40376 since that was last updated 2 years ago and seems to be caused by a bug which was fixed in a prior version of wine. -- 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 19153] New: DX3 game does not recognize graphics capabilities
by wine-bugs＠winehq.org 26 Aug '24

26 Aug '24

http://bugs.winehq.org/show_bug.cgi?id=19153 Summary: DX3 game does not recognize graphics capabilities Product: Wine Version: 1.1.24 Platform: PC URL: http://appdb.winehq.org/objectManager.php?sClass=versi on&iId=9396 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: bobbyg(a)gmx.net Resident Evil 1 does not start giving the error "Failed to initialize the Graphics Hardware Device.(3)". It's a DirectX 3 game using immediate mode. After some debugging I found that it relies on 3 (three) entries returned by EnumDevices whereas wine returns only the Direct3D HAL entry in this case (d3dversion == 1). Removing the if-clause in ddraw/direct3d.c and duplicating the HAL entry solves the problem and the game actually runs almost perfectly (Garbage -> Platinum). I checked a Windows installation which returns "HAL", "RGB Emulation" and "Ramp Emulation" but the comments in the file suggest that not all games are happy about that. So how to fix this properly? -- 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 48

Jump to page:

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 September 2023