May 2022 - Wine-bugs - list.winehq.org

[Bug 52694] New: EnumPrintersW crashes on Linux but not on Windows
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=52694 Bug ID: 52694 Summary: EnumPrintersW crashes on Linux but not on Windows Product: Wine Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal(a)protonmail.com Distribution: --- ``` let argument_0 = 10000; let argument_1 = PCWSTR::default(); let argument_2 = 10000; let mut argument_3 = 100; let argument_3 = &mut argument3; let argument_4 = 10000; let mut argument_5 = 10000; let argument_5 = &mut argument5; let mut argument_6 = 10000; let argument_6 = &mut argument6; EnumPrintersW(argument_0,argument_1,argument_2,argument_3,argument_4,argument_5,argument_6); ``` seems to crash app Steps to reproduce - Download Fuzzer - https://github.com/qarmin/Win32Fuzzer/releases/download/1.1.0/win_project_6… - Create `settings.txt` in same folder - Fill it with this content ``` allowed_functions: EnumPrintersW repeating_number: 50 random: false ``` - Run `win_project_64.exe` ``` 01e0:fixme:winspool:WINSPOOL_EnumPrintersW dwType = 00002710 wine: Unhandled page fault on execute access to 0000000000000000 at address 0000000000000000 (thread 01e0), starting debugger... Unhandled exception: page fault on execute access to 0x0000000000000000 in 64-bit code (0x0000000000000000). .... .... System information: Wine build: wine-7.4 Platform: x86_64 Version: Windows 10 Host system: Linux Host version: 5.13.0-35-generic ``` -- 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 52776] New: The issue of internal Wine errors and warnings for creating a new prefix/running built-in applications
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=52776 Bug ID: 52776 Summary: The issue of internal Wine errors and warnings for creating a new prefix/running built-in applications Product: Wine Version: 7.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- It's purely a cosmetics issue but it's really annoying, so I'd love to hear from Wine developers. This is not a bug per se, but I don't know where to ask. It would be really great if Wine was error/warning-free in terms of using internal applications or/and creating a new prefix. Here's an example for Wine 7.5 for a brand new non-existing ~/.wine: $ wine notepad 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0048:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0050:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0048:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002 0048:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 0048:err:ole:apartment_get_local_server_stream Failed: 0x80004002 0050:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002 0050:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 0050:err:ole:apartment_get_local_server_stream Failed: 0x80004002 0048:err:ole:start_rpcss Failed to open RpcSs service 0050:fixme:imm:ImeSetActiveContext (0x25e320, 0): stub 0050:fixme:imm:ImmReleaseContext (00010020, 0025E320): stub 002c:fixme:imm:ImeSetActiveContext (0x257128, 1): stub 002c:fixme:imm:ImmReleaseContext (0001004E, 00257128): stub 0088:err:setupapi:SetupDefaultQueueCallbackW copy error 1812 L"@C:\\windows\\system32\\drivers\\wineusb.sys,-1" -> L"C:\\windows\\inf\\wineusb.inf" wine: configuration in L"/home/birdie/.wine" has been updated. 0104:fixme:imm:ImeSetActiveContext (0x26b460, 1): stub 0104:fixme:imm:ImmReleaseContext (00030048, 0026B460): stub * Three fixme's for actctx. * Seven errors for ole. * Six fixme's for imm. * One error for setupapi. Here's the second run: $ wine notepad 00c4:fixme:imm:ImeSetActiveContext (0x26b460, 1): stub 00c4:fixme:imm:ImmReleaseContext (00010058, 0026B460): stub 00cc:fixme:imm:ImeSetActiveContext (0x26b0a0, 0): stub 00cc:fixme:imm:ImmReleaseContext (00010020, 0026B0A0): stub I'm being nit-picky, apologies, but this all looks quite untidy. -- 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 52830] New: DWRITE.DLL cannot be cross-compiled for WIN32 with freetype
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=52830 Bug ID: 52830 Summary: DWRITE.DLL cannot be cross-compiled for WIN32 with freetype Product: Wine Version: 7.6 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: dwrite Assignee: wine-bugs(a)winehq.org Reporter: svyatpro(a)gmail.com DWRITE.DLL cannot be cross-compiled for WIN32 with freetype delay-load dependency thus fonts are not being rendered on Windows hosts. Steps I used to enable cross-compilation with freetype: 1. Addad freetype headers into "include" folder 2. Changed in config.h.in: #define HAVE_FREETYPE 1 #define HAVE_FT2BUILD_H 1 #define SONAME_LIBFREETYPE "freetype.dll" In order to cross-compile for WIN32 I should use "--without-freetype" key in configure. -- 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 29240] New: Anti-aliasing not working for all fonts
by wine-bugs＠winehq.org 27 Aug '22

27 Aug '22

http://bugs.winehq.org/show_bug.cgi?id=29240 Bug #: 29240 Summary: Anti-aliasing not working for all fonts Product: Wine Version: 1.3.34 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: fonts AssignedTo: wine-bugs(a)winehq.org ReportedBy: A.Fettouhi(a)gmail.com Classification: Unclassified Yesterday I updated wine on my Arch 64 bit system from 1.3.33 to 1.3.34. Since then I've noticed that some now aren't anti-aliased anymore. I've seen it in Steam when looking at the fonts displaying "MAC", "VIDEOS" etc. on the main page and on the install pop-up that appears when you install flash11. These fonts looked fine on 1.3.33 but with 1.3.34 they look "ugly". So some kind of regression happended. -- 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 32

[Bug 49913] New: Can't play Maro Kart DX12 (ThICC_Engine.exe) in Wine 5.18 using RADV on AMD GPU
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=49913 Bug ID: 49913 Summary: Can't play Maro Kart DX12 (ThICC_Engine.exe) in Wine 5.18 using RADV on AMD GPU Product: vkd3d Version: 1.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: yuri(a)linuxreviews.org Distribution: --- Created attachment 68283 --> https://bugs.winehq.org/attachment.cgi?id=68283 Wine backtrace of Mario Kart DX12 The game Mario Kart DX12 using something called "ThICC_Engine" fails to run in Wine 5.18 with vkd3d-1.2. It is a freeware game from Itch, https://mattfiler.itch.io/mario-kart-dx12 I also filed a Mesa bug at https://gitlab.freedesktop.org/mesa/mesa/-/issues/3567 It may be a Wine/vkd3d bug not a Mesa bug. Odd thing is that if you start it and leave it alone it starts racing on it's own and that works, see screenshots at https://linuxreviews.org/Vkd3d_1.2_Is_Released but if you start a game to play it the game just crashes. It should be easy to reproduce since the game is freeware. -- 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 4

[Bug 51048] New: wine explorer /desktop=default,<resolution> does not render a virtual desktop
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=51048 Bug ID: 51048 Summary: wine explorer /desktop=default,<resolution> does not render a virtual desktop Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: geoff.pvgn1(a)gmail.com Distribution: --- When executing any program through wine, and using the command line to generate a virtual desktop, no virtual desktop will be created if it is named "default". For example, wine explorer /desktop=default,1920x1080 control yields the control panel without a bordering desktop. wine explorer /desktop=foo,1920x1080 control creates the virtual desktop with the control panel within it correctly, and names the virtual desktop "foo". Capitalizations of "default" do not seem to make a difference. Tested in Gentoo Linux, 2021, with vanilla wine 6.6 -- 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 4

[Bug 51275] New: Many programs don't work with gtk theming enabled.
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=51275 Bug ID: 51275 Summary: Many programs don't work with gtk theming enabled. Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: toadfield(a)tutanota.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- When I use the gtk3 theming,then it doesn't work for many programs,for example cemu and xdelta ui. -- 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 51289] New: ws2_32:sock has siocatmark failures on wvistau64
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=51289 Bug ID: 51289 Summary: ws2_32:sock has siocatmark failures on wvistau64 Product: Wine Version: 6.10 Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ws2_32:sock fails quite consistently on wvistau64: https://test.winehq.org/data/patterns.html#ws2_32:sock sock.c:3838: Test failed: FIONBIO returned 0 sock.c:3838: Test failed: SIOCATMARK returned 1 sock.c:3848: Test failed: FIONBIO returned 0 These failures happen consistently for both 32- and 64-bit tests on wvistau64 but only the 64-bit WineTest is run daily. They don't happen at all on wvista though so there must be some difference between these two VMs. wvista has the older ws2_32 dll (6.0.6001.18000 vs. 6.0.6002.18005 for wvistau64), which means the failures happen on the more recent ws2_32. This makes no sense so the root cause is probably elsewhere. The failures look like they might be timing related but while adding a Sleep(50) before the failing lines avoid the first 3838 failure, it's not reliable and does nothing for the 3848 failure. The failing tests were introduced in this commit: commit 2795fa9c00338bfff6304c1b756d1a58f9f6ca60 Author: Zebediah Figura <z.figura12(a)gmail.com> Date: Thu May 27 18:57:31 2021 -0500 ws2_32/tests: Separate and expand tests for FIONREAD and SIOCATMARK. Signed-off-by: Zebediah Figura <z.figura12(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> But the TestBot only reported the failures for the next patch in the series: https://www.winehq.org/pipermail/wine-devel/2021-May/187782.html -- 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 48851] New: WinSCP file transfer "The specified data could not be decrypted"
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=48851 Bug ID: 48851 Summary: WinSCP file transfer "The specified data could not be decrypted" Product: Wine Version: 4.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tim.c.quinn(a)gmail.com Distribution: --- Created attachment 66775 --> https://bugs.winehq.org/attachment.cgi?id=66775 This is the file that failes. Its from the Apache log4net project I've been using WinSCP on wine for years and just hit my first big issue and it appears to be a wine issue. I was trying to transfer an xml file to an IIS server on Windows Server 2019 and it fails on the client side with the error: - Copying files to remote side failed. - The specified data could not be decrypted. The version of WinSCP I am using is 5.17.2 portable. The same issue occurs with WinSCP 5.11.3 portable. The error on 5.11.3 is a bit more verbose: - Using TLSv1.2, cipher TLSv1/SSLv3: ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA, ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA Enc=AESGCM(256) Mac=AEAD - Copying files to remote side failed. - The specified data could not be decrypted. To isolate if this is a WinSCP issue or a Windows issue, I deployed the exact same WinSCP 5.17.2 on Windows Server 2008R2 and the file transferred ok with no errors. I suspect this issue is related to TLS libraries deployed with 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 6

[Bug 52316] New: Windows Error
by WineHQ Bugzilla 27 Aug '22

27 Aug '22

https://bugs.winehq.org/show_bug.cgi?id=52316 Bug ID: 52316 Summary: Windows Error Product: Wine Version: 7.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: api-ms-win-* Assignee: wine-bugs(a)winehq.org Reporter: liaolllll5(a)iCloud.com Distribution: --- Created attachment 71477 --> https://bugs.winehq.org/attachment.cgi?id=71477 The record $winecfg open a window in a strange shape -- 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