January 2022 - Wine-Bugs - list.winehq.org

[Bug 51890] New: A lot more old games would be so much more usable if wine's virtual desktop had proper resizing
by WineHQ Bugzilla Aug. 29, 2023

Aug. 29, 2023

https://bugs.winehq.org/show_bug.cgi?id=51890 Bug ID: 51890 Summary: A lot more old games would be so much more usable if wine's virtual desktop had proper resizing Product: Wine-staging Version: 6.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: el(a)horse64.org CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- I have a really significant amount of older games around, none of which will launch on this machine without wine's virtual desktop feature because on a widescreen monitor, they determine there is no "expected" fullscreen resolution available and crash. Now I'd just use the virtual desktop, except it feels archaic and not very usable: why is it that for a 800x600 game on a 800x600 virtual desktop, I can't just maximize the virtual desktop window and get the virtual desktop SCALED UP with proper letterboxing so I can play in some other way than a tiny window with zero immersion and everything so small I can barely see it? Funnily enough I can even resize the virtual desktop window except the resizing is fully ignored and I just get black void with no scaling up all around with the game stuck in the top-left, and the maximizing is blocked. Scaling up (with automatic letterboxing), maximizing would seem like such obvious features to make virtual desktop gaming infinitely less clumsy and weird that I am a bit surprised it's not in there yet. Can it please be added?? -- 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 52235] New: Many surfaces in the game Obduction look black
by WineHQ Bugzilla Aug. 25, 2023

Aug. 25, 2023

https://bugs.winehq.org/show_bug.cgi?id=52235 Bug ID: 52235 Summary: Many surfaces in the game Obduction look black Product: Wine Version: 7.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: zerooneo(a)01101001.net Distribution: --- Created attachment 71338 --> https://bugs.winehq.org/attachment.cgi?id=71338 Screenshot When running the game Obduction in wine, an interesting effect occurs where most surfaces are pure black, yet with some lighting etc. applied, leaving the game looking extremely dark. This effect does not occur when running the game with DXVK, meaning there's a very specific difference the two implementations that has a large effect on this game. The log shows a few DirectX and Direct3D-messages initially (counts on the left): 1 03d8:fixme:dxgi:DXGID3D10CreateDevice Ignoring flags 0x1. 1 03d8:fixme:dxgi:DXGID3D10CreateDevice Ignoring flags 0x20. 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0x12d2cad0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d30, modes 0x7fe90cc3ac00 partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0x12d2cad0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d30, modes (nil) partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed354e0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ad0, modes 0x18fa4d80 partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed354e0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ad0, modes (nil) partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed39050, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ab0, modes 0x1aece780 partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xed39050, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8ab0, modes (nil) partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xf0f51c0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d50, modes 0x1af84680 partial stub! 1 03d8:fixme:dxgi:dxgi_output_GetDisplayModeList iface 0xf0f51c0, format DXGI_FORMAT_R8G8B8A8_UNORM, flags 0, mode_count 0x4e8d50, modes (nil) partial stub! 2 04a8:fixme:d3d:create_texture_view Depth slice (0-1) not supported. 10 04a8:fixme:d3d_shader:shader_glsl_handle_instruction Backend can't handle opcode dcl_stream. 46 03d8:fixme:d3d11:d3d11_device_CheckFeatureSupport Unhandled feature 0x3. 432 04a8:fixme:d3d_shader:shader_glsl_interpolation_qualifiers Unhandled interpolation mode 0x3. And then thousands of these: 1080 04a8:err:d3d:wined3d_debug_callback 0x578c00: "GL_INVALID_ENUM in glTexBufferRange(internalFormat GL_RGBA16_SNORM)". 4632 04a8:err:d3d:wined3d_debug_callback 0x578c00: "GL_INVALID_ENUM in glTexBufferRange(internalFormat GL_RGBA8_SNORM Might it be that certain textures or shaders aren't supported, and that that leads to them being rendered as black? This game also requires some other features in order to work fully, but it might be worth it to fix this issue either for the sake of other games, or in case further support for this game is added in the future. -- 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 12

[Bug 51678] New: Avogadro crashes when adding atoms
by WineHQ Bugzilla Aug. 25, 2023

Aug. 25, 2023

https://bugs.winehq.org/show_bug.cgi?id=51678 Bug ID: 51678 Summary: Avogadro crashes when adding atoms Product: Wine Version: 6.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Just install, open the program (avogadro.exe) and click two times into the black 3D part of the window. Wine crashes with something like "Unhandled page fault on read access to 8010C497 at address 72A562D3" -- 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 45329] New: Fresh steam install will not install games -- error: " content servers unreachable"
by wine-bugs＠winehq.org Aug. 24, 2023

Aug. 24, 2023

https://bugs.winehq.org/show_bug.cgi?id=45329 Bug ID: 45329 Summary: Fresh steam install will not install games -- error: "content servers unreachable" Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alasky(a)codeweavers.com Distribution: --- Created attachment 61617 --> https://bugs.winehq.org/attachment.cgi?id=61617 Steam error dialogue box Ubuntu 18.04 Wine tip (most recent commit is 83f845dfa1bb4a6ec6e8b7f65e9469dc9a8a7787) When attempting to install a game on a fresh Steam install, an error comes up that says "content servers unreachable." The servers are not down and I am able to install games correctly on my steam account not using wine. This issue seems to be caused by an update on Steam's side. -- 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 42

[Bug 48621] New: Civilization 6 crashes on startup.
by WineHQ Bugzilla Aug. 18, 2023

Aug. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=48621 Bug ID: 48621 Summary: Civilization 6 crashes on startup. Product: Wine Version: 5.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: charles2000wang(a)gmail.com Distribution: --- Created attachment 66468 --> https://bugs.winehq.org/attachment.cgi?id=66468 Game Log file Launching the game opens a black window before promptly crashes with the Firaxis Crash Reporter asking to submit a report. Digging around the game files, I found a log file (GameOverlayRenderer.log) with messages about "Aborting HookFunc because pRealFunctionAddr is null" and other errors. -- 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 36564] New: 'Candytron' demo: certain objects are black with GLSL enabled
by wine-bugs＠winehq.org Aug. 18, 2023

Aug. 18, 2023

http://bugs.winehq.org/show_bug.cgi?id=36564 Bug ID: 36564 Summary: 'Candytron' demo: certain objects are black with GLSL enabled Product: Wine Version: 1.6-rc1 Hardware: x86 URL: http://www.pouet.net/prod.php?which=9424 OS: Linux Status: NEW Keywords: download, regression Severity: trivial Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: hverbeet(a)gmail.com Regression SHA1: 2014141a253a791fc9c79aae3c8ef3c35b73e658 Created attachment 48657 --> http://bugs.winehq.org/attachment.cgi?id=48657 screenshot (comparison) Some of the rectangles that appear in the demo nearly at 00:30 and at 01:10 are black. They should appear as glowing green rectangles as can be seen in the attached screenshot. Terminal output doesn't reveal anything interesting. Disabling GLSL is a workaround. This is a regression from Wine 1.6-rc1: 2014141a253a791fc9c79aae3c8ef3c35b73e658 is the first bad commit commit 2014141a253a791fc9c79aae3c8ef3c35b73e658 Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Wed May 29 09:45:35 2013 +0200 wined3d: Add support for GLSL based fixed function vertex shaders. :040000 040000 d1b4b75f643d4851d4f51454aa47740261f7857f c46794f61b1952b1e78746272d838574c0948010 M dlls Fedora 20 Nvidia 250 gfx card / Nvidia binary drivers 337.19 wine-1.7.19-70-gd6a59f7 -- 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 52474] New: ws2_32:sock fails intermittently - 'Test failed: expected timeout'
by WineHQ Bugzilla Aug. 18, 2023

Aug. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=52474 Bug ID: 52474 Summary: ws2_32:sock fails intermittently - 'Test failed: expected timeout' Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com Distribution: --- The test_connect_events() function contains the following checks, where the check (2) fails intermittently: 1. check_events(ctx, FD_CONNECT, FD_WRITE, 200); 2. check_events(ctx, 0, 0, 0); A hypothesis for the cause of the test failure is that the WSAEnumNetworkEvents() call inside the check (1) races with the server setting the event. Note that WSAEnumNetworkEvents performs the following steps: a. It calls ResetEvent on the given event. b. It issues IOCTL_AFD_GET_EVENTS command on the socket to retrieve the events so far. It's possible that the event may be set by the server between (a) and (b), which lingers until the next call to WSAEnumNetworkEvents(). This explains why the event wait in check (2) is satisfied immediately but subsequent tests report no events. -- 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 34678] New: Not all serial port work in wine
by wine-bugs＠winehq.org Aug. 18, 2023

Aug. 18, 2023

http://bugs.winehq.org/show_bug.cgi?id=34678 Bug #: 34678 Summary: Not all serial port work in wine Product: Wine Version: 1.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: rewineland(a)gmail.com Classification: Unclassified I have wine 1.6 install on Ubuntu 12.04 with kernel 3.8.0-31-generial. I have 2 serial ports on board and an add-on card with 8 more.I can get the the on board and 7 of the add-on to work as 1 though 9 comports but com10 I can not get any data though. the port is listed as ttyCTI7, when I connect to that I have data going back and forth. It just wont go into the windows program. Any ideas on what to do. I need to have all 10 ports. -- 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 10

[Bug 52492] New: stack overflow from GdipFlattenPath
by WineHQ Bugzilla Aug. 18, 2023

Aug. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=52492 Bug ID: 52492 Summary: stack overflow from GdipFlattenPath Product: Wine Version: 7.1 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdiplus Assignee: wine-bugs(a)winehq.org Reporter: rjfeuerbach(a)gmail.com Created attachment 71787 --> https://bugs.winehq.org/attachment.cgi?id=71787 test patch to replicate the curves and stack overflow I have a third party application, unfortunately not available for download, that is generating a virtual stack overflow error. Using +replay and eventually +gdiplus messages, the cause was narrowed down to be due to calls to GdipFlattenPath. Attached is a patch to gdiplus/test/graphicspath.c to include the precise curves that cause the stack overflow. I believe the problem is due to the comparison of REALs with == in the flatten_bezier helper function. -- 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 22

[Bug 44816] New: Cygwin/ MSYS2 `script -e` exit status forwarding randomly returns zero for non zero child process
by wine-bugs＠winehq.org Aug. 18, 2023

Aug. 18, 2023

https://bugs.winehq.org/show_bug.cgi?id=44816 Bug ID: 44816 Summary: Cygwin/MSYS2 `script -e` exit status forwarding randomly returns zero for non zero child process Product: Wine Version: 3.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, to track https://github.com/wine-staging/wine-staging/tree/master/patches/ntdll-Deal… Mentioned here: https://wine-staging.com/news/2015-08-23-release-1.7.50.html --- quote --- Do not allow to deallocate thread stack for current thread (MSYS2, Wine Staging Bug #241) --- quote --- After some archaeology I found the Cygwin mailing list discussion here: https://cygwin.com/ml/cygwin/2015-09/msg00114.html --- quote --- > Ah, ok. What OS does Wine emulate here? Have a look at > https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/cygt… > > The terminate_thread_frees_stack flag is set to false for XP/2003 and to > true for any newer OS. I guess this is a double-free because Wine's > TerminateThread already freed the stack and Cygwin got the info it's > supposedly running under XP/2003, so it tries to workaround the fact > that TerminateThread on these systems didn't free the stack by themselves. > Wine emulates Windows XP here, I double checked Wine source code and I can confirm Wine doesn't free the stack: NtTerminateThread() -> abort_thread() -> terminate_thread() https://github.com/wine-compholio/wine-patched/blob/8b3a785e97a7e28ff58731b… Cygwin reports wincap as wincap_xpsp2 which is also correct here. > we need to know what address ret=61005767 is refering to. addr2line would help. As you point out, ret=61005767 is the call to VirtualFree() inside cygthread::terminate_thread () https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=winsup/cygwin/cygt… After combine the information we have so far, I think the problem is clear now. It's not Cygwin's fault, it's Wine's fault. Wine's WaitForSingleObject() needs to wait long enough after the TerminateThread() call, so the target thread has enough time to finish the system cleanup and return correct exit_code before Cygwin call VirtualFree to free the stack. But in our current implementation Wine's WaitForSingleObject returns too early, it shouldn't return before the system thread cleanup done, as a result there is a race here. We are thinking of a solution in Wine. Thanks again for the great help! --- quote --- $ wine --version wine-3.4 Regards -- 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