wine-bugs June 2023

wine-bugs@winehq.org

1 participants
2529 discussions

[Bug 48024] New: Betfair Poker: black screen during install
by WineHQ Bugzilla 03 Sep '24

03 Sep '24

https://bugs.winehq.org/show_bug.cgi?id=48024 Bug ID: 48024 Summary: Betfair Poker: black screen during install Product: Wine Version: 4.18 Hardware: x86-64 URL: https://poker-com-banner.bfcdl.com/installer/SetupPoke r.exe OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Created attachment 65562 --> https://bugs.winehq.org/attachment.cgi?id=65562 Wine 4.18 console log The Betfair Poker install client briefly shows the install screen before being blacked out. The installation cannot continue. https://youtu.be/U53jzEdIN98 Workarounds: winetricks ie6 (Bug 38929) The workaround is to use a virtual desktop where the black screen appears BEHIND the main installer. (Z-order problem?) Same with Staging 4.18. No account needed to get this far. -- 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 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 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

[Bug 54561] New: Google Chrome unable to load widevine_cdm.dll 4.10.2557.0 (and up)
by WineHQ Bugzilla 26 Aug '24

26 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=54561 Bug ID: 54561 Summary: Google Chrome unable to load widevine_cdm.dll 4.10.2557.0 (and up) Product: Wine Version: 8.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ionic(a)ionic.de Distribution: --- Created attachment 74101 --> https://bugs.winehq.org/attachment.cgi?id=74101 WINEDEBUG=warn+all /usr/bin/wine-vanilla-9999 GoogleChromePortable64/App/Chrome-bin/chrome.exe --no-sandbox Google Chrome is currently unable to load widevine_cdm.dll as of version 4.10.2557.0. Version 4.10.2449.0 of widevine_cdm.dll (for instance shipped/bundled with Google Chrome 105.0.5195.127) will load just fine, but is now useless, since most streaming services have blocked this old version by now. I've tested with wine 8.2 (I'm currently using git master from about a week ago, built 20.02.2023), but the behavior shows also up with older wine versions, down to 7.0. My main use case is to watch content on Amazon Prime in Full HD resolution - which is now impossible. I'm also attaching a warn+all log, but the relevant part, as far as I can tell, is this one: 033c:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised 033c:warn:module:process_attach Initialization of L"widevinecdm.dll" failed [824:828:0223/065058.326:ERROR:cdm_module.cc(114)] CDM at C:\users\ionic\AppData\Local\Google\Chrome\User Data\WidevineCdm\4.10.2557.0\_platform_specific\win_x64\widevinecdm.dll could not be loaded. [824:828:0223/065058.326:ERROR:cdm_module.cc(115)] Error: 998 Error 998, conveniently, is ERROR_NOACCESS, which doesn't seem surprising given the previous access violation. I honestly don't know if this issue is caused by wine itself, especially since older versions of the widevine library still load just fine. For testing this, I recommend installing the current version of Google Chrome, either normally or using the (64 Bit testing) version of Google Chrome Portable and starting video playback on https://www.nuevodevel.com/nuevo/showcase/drm , which embeds the free Big Buck Bunny video in a Widevine-based DRM setting. Note, however, that downgrading to widevine 4.10.2449.0 will make it work - but Amazon Prime will complain about an outdated browser version (which is a lie, because it really [also] checks the widevine version) and refuse to play any content. -- 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 1

[Bug 48614] New: Windows 10 Opera browser hangs/freezes immediatly on install using Wine 4.1 linux x86/64bit
by WineHQ Bugzilla 26 Aug '24

26 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=48614 Bug ID: 48614 Summary: Windows 10 Opera browser hangs/freezes immediatly on install using Wine 4.1 linux x86/64bit Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stevedonato(a)gmail.com Distribution: --- trying to use windows 10 Opera browser because native linux browser nolonger can run Amazon Prime Videos. Tried playing NEW Amazon Prime tv series called "Hunter" at https://www.amazon.com/gp/video/detail/B07ZPF4DVK/ref=atv_dl_rdr?autoplay=1 Gets Digital rights error. Win 10 version of Opera works OK. Linux and Windows version of Opera have no option to enable DRM, also called "Widevine". The error msg text is"A later version of Opera is required for Prime Video. To check for updates, click the Opera menu, click About Opera, and then click Relaunch Now." But I am using latest Oper ver 66. also tried the Developer and Beta versions of Oper ver 67 and 68. Same error. Oddly, the windows 10 version of Opera was even older,at ver 63 but it worked? Something to do with HTML5 videos and DRM/Widevine ? -- 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

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