wine-bugs May 2024

wine-bugs@winehq.org

1 participants
1619 discussions

[Bug 52454] New: QTranslate 6.3.1 fails to start
by WineHQ Bugzilla 18 May '24

18 May '24

https://bugs.winehq.org/show_bug.cgi?id=52454 Bug ID: 52454 Summary: QTranslate 6.3.1 fails to start Product: Wine Version: 7.0-rc6 Hardware: x86-64 URL: https://web.archive.org/web/20170606113219if_/http://q translate1.appspot.com/QTranslate.6.3.1.exe OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: jscript Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Distribution: --- Created attachment 71742 --> https://bugs.winehq.org/attachment.cgi?id=71742 +jscript It shows a window with 'QTranslate initialization error. The program will be closed.' After clicking 'OK' it exits. winetricks -q wsh57 fixes the issue and allows the program to start. $ sha1sum QTranslate.6.3.1.exe 7a8f9940049ec50352e732b14349b9bfc3f704a4 QTranslate.6.3.1.exe $ du -sh QTranslate.6.3.1.exe 780K QTranslate.6.3.1.exe -- 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 56690] New: Dead By Day light crashes on start
by WineHQ Bugzilla 18 May '24

18 May '24

https://bugs.winehq.org/show_bug.cgi?id=56690 Bug ID: 56690 Summary: Dead By Day light crashes on start Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sollieus(a)gmail.com Distribution: --- Created attachment 76471 --> https://bugs.winehq.org/attachment.cgi?id=76471 Logs form game crash game: Dead By Daylight Platform to launch: Heroic games (FlatPak) when trying to open the game easy anti cheat will start normally but the game itself crashes with logs provided as an attachment -- 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 35940] New: Server (and perhaps others) may fail to build on some platforms
by wine-bugs＠winehq.org 18 May '24

18 May '24

http://bugs.winehq.org/show_bug.cgi?id=35940 Bug ID: 35940 Summary: Server (and perhaps others) may fail to build on some platforms Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: carlo.bramix(a)libero.it In my opinion there is a severe mistake in the build system for the server. >From the man page of GCC, the documentation for '-I' option says: `-I DIR' Add the directory DIR to the list of directories to be searched for header files. Directories named by `-I' are searched before the standard system include directories. If the directory DIR is a standard system include directory, the option is ignored to ensure that the default search order for system directories and the special treatment of system headers are not defeated . When building the server, a '-I' option is placed on the command line, pointing to the source directory of the server. The file wine/port.h provides this piece of code: [...cut...] #ifdef HAVE_PROCESS_H # include <process.h> #endif [...cut...] The problem comes out because, inside the directory with the sources of the server, there is a file named process.h and since the -I option allows to take the files before the standard system include directories, the wine/port.h won't include the system file, but the one in the server directory: infact, it happens that the local process.h file is included two times. This is the cause for the server not compiled correctly on my platform (cygwin) but probably it can be also applied to others. I did an experiment and I have bypassed the problem by changing the generated Makefile: I replaced the '-I' option that pointed to the source directory of the server with '-idirafter'. The final result is a server that installs and runs correctly on Windows. Actually, this defect caused a failure on the server, but probably it may apply to all components of WINE with some local include files: the option that allows to point to the source directory of the component being compiled (and only this one) should be changed with '-idirafter' or something similar, depending on the compiler used, while all other paths could be left to '-I' without troubles. -- 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 6

[Bug 39532] New: Assassin's Creed Unity doesn't run
by wine-bugs＠winehq.org 17 May '24

17 May '24

https://bugs.winehq.org/show_bug.cgi?id=39532 Bug ID: 39532 Summary: Assassin's Creed Unity doesn't run Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-d3dx10 Assignee: wine-bugs(a)winehq.org Reporter: anakin.cs(a)gmail.com Distribution: --- Created attachment 52679 --> https://bugs.winehq.org/attachment.cgi?id=52679 terminal log I've been trying to run Assassin's Creed Unity from Uplay on my laptop, both on the Intel card and Nvidia card (with primusrun), and I always get the following error message (translated from French): "Can't launch the game. Your video card doesn't support DirectX 11 or the video drivers need to be updated." My video card is an Nvidia Geforce 850M. Attached is the terminal output after trying to launch the game. -- 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 12

[Bug 56607] New: steam: no tray icon starting with wine 9.2
by WineHQ Bugzilla 17 May '24

17 May '24

https://bugs.winehq.org/show_bug.cgi?id=56607 Bug ID: 56607 Summary: steam: no tray icon starting with wine 9.2 Product: Wine Version: 9.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: idarktemplar(a)mail.ru Distribution: --- Tray icon for steam is missing in wine 9.7. I did bisecting and found that it's started with following commit: b5c57b9a62c396068d18237bd6e82b37c169fdc5 is the first bad commit commit b5c57b9a62c396068d18237bd6e82b37c169fdc5 Author: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> Date: Tue Feb 6 16:51:21 2024 +0200 explorer: Set layered style on systray icons only when it's actually layered. Fixes a regression introduced by 229b4561d9a8f10cbb49342dff0b6a3472d81c68, which caused the icons to not be visible initially in the virtual desktop systray. Signed-off-by: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> programs/explorer/systray.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) But unlike battle.net in https://bugs.winehq.org/show_bug.cgi?id=56337, for steam tray icon doesn't reappear in wine 9.3 or 9.7 Reproduction: 1. install steam for windows (https://store.steampowered.com/about/) 2. run steam 3. log into steam account Expected result: steam tray icon in system tray Actual result: no steam tray icon is present in system tray Environment: Linux 6.6.21-gentoo KDE/Plasma 5.27.11 X11 -- 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 53197] New: Shogun Total War 2 needs d3dx11_42.dll.D3DX11LoadTextureFromTexture.
by WineHQ Bugzilla 17 May '24

17 May '24

https://bugs.winehq.org/show_bug.cgi?id=53197 Bug ID: 53197 Summary: Shogun Total War 2 needs d3dx11_42.dll.D3DX11LoadTextureFromTexture. Product: Wine Version: 7.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- With both wined3d and dxvk, Shogun Total War 2 generates the following in DirectX 11 mode (on both 32bit native and WoW64 prefixes) before reaching the game's main menu: ---Log output--- d3d call failed (0x80004001) : unspecified 0100:fixme:d3dx:D3DX11GetImageInfoFromMemory src_data 046FE756, src_data_size 5592532, pump 00000000, img_info 0055CBD0, hresult 00000000 stub! d3d call failed (0x80004001) : unspecified 0100:fixme:d3dx:D3DX11GetImageInfoFromMemory src_data 046F3D2A, src_data_size 5592532, pump 00000000, img_info 0055CBD0, hresult 00000000 stub! d3d call failed (0x80004001) : unspecified 0100:fixme:d3dx:D3DX11GetImageInfoFromMemory src_data 046FEA86, src_data_size 5592532, pump 00000000, img_info 0055CBD0, hresult 00000000 stub! d3d call failed (0x80004001) : unspecified 0100:fixme:d3dx:D3DX11GetImageInfoFromMemory src_data 046F405A, src_data_size 5592532, pump 00000000, img_info 0055CBD0, hresult 00000000 stub! d3d call failed (0x80004001) : unspecified wine: Call from 7B0122F6 to unimplemented function d3dx11_42.dll.D3DX11LoadTextureFromTexture, aborting 0100:fixme:faultrep:ReportFault 0055C6B8 0x0 stub wine: Unimplemented function d3dx11_42.dll.D3DX11LoadTextureFromTexture called at address 7B0122F6 (thread 0100), starting debugger... ---Log output--- As a workaround, the game can be played in DirectX 9 mode. -- 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 49674] New: Feature Request: Restoring previous resolution upon an app crashing
by WineHQ Bugzilla 17 May '24

17 May '24

https://bugs.winehq.org/show_bug.cgi?id=49674 Bug ID: 49674 Summary: Feature Request: Restoring previous resolution upon an app crashing Product: Wine Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: s.maddox(a)lantizia.me.uk So this has been a bit of a bug of mine with Wine for a while, but you may think it's not really a problem Wine should deal with - which may be a fair point. But I couldn't find anything clearly asking for this as a feature request... so lets see how well it fairs. # The problem Lets say you open up a Windows executable which changes your screens resolution (e.g. a game) and it either... a) freezes b) is broken enough that its UI (if any appears) can't be used to nicely ask it to quit c) crashes and quits differently to how it'd normally do so upon user request With a) and b) you likely need to kill that process, which ultimately leaves you in the same situation as c). But however it happens... you're likely to find your resolution now stuck to whatever it set. If that is an incredibly low resolution (like 320x240 or 640x480)... then with the desktop environment of today (especially with HiDPI) you're likely going to struggle finding the proper option to fix it. Worse you might resort to a terminal (or switch TTY) and mess around with the xrandr command for a stupid amount of time trying to find the names of screens and such. # Expected Behaviour Well I'm not sure what actually does this. But in actual Windows (e.g Windows 10), when this same circumstance occurs... the resolution is always restored back to what it was. This leaves me to believe that Windows itself has something for this eventuality. # Research Well I've been searching around for solutions to this one for years and the best I always come across... is someone saying you're better off with a script (usually calling xrandr) mapped to a hot key or something for this eventuality. Which is fine if the number of displays you've got connected and their resolutions are always consistent... but often for laptop users moving between docks and such - it isn't. A quick chat on the #winehq IRC channel had someone mention that Proton can now scale games to the resolution you're already using instead (when the app requests a resolution change)... and pointed out these patches... https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/pro… https://github.com/GloriousEggroll/proton-ge-custom/blob/master/patches/pro… That's fine, and it's a welcome feature. But I do wonder if this is a universal fix for any request for any resolution change... regardless the age (and compatibility with which version of Windows it was meant for) of the game and the way it draws on the screen (e.g. SDL, OpenGL, DirectDraw, Vulkan, etc...). However it *may* give some hope for people wanting to run older windowed-mode games from the early Win 3.1/95 era which refuse to be re-sized/re-scaled... but that's a topic for another feature request :) # Conclusion I've not got any. Should this be the job of Wine to restore the prior resolution if the app/game fails to? Like Windows somehow does? Or is this something the OS (whatever that may be, Linux/macOS or even Windows) should be doing separately from Wine for any process? Also if this is a dupe, feel free to mark it as such... I've looked and couldn't find anything that is quite so specific - at least with the points raised here. Thoughts? -- 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 56661] New: Commit 8b3944e1341baaf693927c8b758851d2dbba725a breaks Project Diablo 2's Game.exe game client
by WineHQ Bugzilla 17 May '24

17 May '24

https://bugs.winehq.org/show_bug.cgi?id=56661 Bug ID: 56661 Summary: Commit 8b3944e1341baaf693927c8b758851d2dbba725a breaks Project Diablo 2's Game.exe game client Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: spaskalev(a)protonmail.com Distribution: --- Commit 8b3944e1341baaf693927c8b758851d2dbba725a breaks Project Diablo 2's Game.exe game client. The game client itself crashes later in its error handling logic leading to a stack overflow while trying to report the error [user@monovo wine-git]$ ./wine ~/.wine/drive_c/Diablo2/ProjectD2/Game.exe -w 002c:err:winediag:getaddrinfo Failed to resolve your host name IP 0074:err:wineusb:DriverEntry Failed to initialize Unix library, status 0xc0000135. 0074:err:ntoskrnl:ZwLoadDriver failed to create driver L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\wineusb": c0000135 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"wineusb" failed to start: 126 wine: Unhandled stack overflow at address 6FF6879B (thread 0024), starting debugger... 0024:err:virtual:virtual_setup_exception stack overflow 1408 bytes addr 0x7bf966ef stack 0x220a80 (0x220000-0x221000-0x320000) The game client itself works fine before this commit - discovered using git bisect. To setup PD2 follow the instructions at https://www.projectdiablo2.com/ For starting the game client a set of battlenet cd keys is not necessary. -- 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 16

[Bug 56506] New: strmbase TRACEs occasionally fail to print floats
by WineHQ Bugzilla 17 May '24

17 May '24

https://bugs.winehq.org/show_bug.cgi?id=56506 Bug ID: 56506 Summary: strmbase TRACEs occasionally fail to print floats Product: Wine Version: 9.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: quartz Assignee: wine-bugs(a)winehq.org Reporter: blubban(a)gmail.com Distribution: --- $ WINEDEBUG=trace+quartz ./wine dlls/quartz/tests/x86_64-windows/quartz_test.exe mpegvideo 2>&1 | grep NewSegment | head -n2 0024:trace:quartz:sink_NewSegment pin 00007FFFFF225C50 L"MPEG video decoder":L"Input", start 0.001, stop 0.002, rate e. 0024:trace:quartz:sink_NewSegment pin 00007FFFFE2FF8C0 L"sink":L"sink", start 0.001, stop 0.002, rate 1.0000000000000000e+000. The strmbase copy in quartz_test.exe calls msvcrt printf and correctly prints 1.0000000000000000e+000. The strmbase copy in winegstreamer.dll calls ntdll's printf, which does not support float operands and just prints 'e'. I think that can be fixed by adding msvcrt as a dep of winegstreamer (without changing anything else), but I'm not sure, and I'm even less sure if that has any side effects. -- 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 56655] New: Regression: X11 Driver fails to load
by WineHQ Bugzilla 17 May '24

17 May '24

https://bugs.winehq.org/show_bug.cgi?id=56655 Bug ID: 56655 Summary: Regression: X11 Driver fails to load Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: bmcgrath(a)codeweavers.com Regression SHA1: f74900ad1a580eda8fd4923cbd4881b42b042733 Distribution: --- Created attachment 76428 --> https://bugs.winehq.org/attachment.cgi?id=76428 Fix X11 driver Building with the latest from master, I found the X11 driver fails to load. The attempt to load appears to enter a tight loop and Wine becomes unresponsive. A git bisect led me to f74900ad1a580eda8fd4923cbd4881b42b042733. I then further narrowed it down to the changes in xrandr10_get_modes. It looks like the old code used to increment mode_idx, but the new code doesn't. The attached patch fixes this for me. -- 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

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 May 2024