January 2021 - Wine-bugs - list.winehq.org

[Bug 50541] New: Cross Code - screen freezes for a few secs.
by WineHQ Bugzilla 22 Jan '21

22 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=50541 Bug ID: 50541 Summary: Cross Code - screen freezes for a few secs. Product: Wine Version: 6.0 Hardware: x86-64 URL: https://store.steampowered.com/app/368340/CrossCode/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: BOBBLOG(a)protonmail.com Distribution: --- Created attachment 69210 --> https://bugs.winehq.org/attachment.cgi?id=69210 Cross Code Screen Freeze Terminal wine-6.0 With the game Cross Code, the screen freezes for a few secs in wine-6.0 with a clean wine prefix. This issue does not happen right away, you have to play the game for a while to see the issue come up. I saw on the terminal this message just before the screen freeze up for a few seconds. 01b8:fixme:d3d:create_texture_view OpenGL implementation does not support texture views. Not sure if that's the issue but figure i'd mention it. Anyways i'll upload the full terminal messages log. -- 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 46079] New: Support 32-bit ARM hard-float cross-toolchains with GNU binutils assembler that doesn 't implicitly assume '.fpu {vfp,neon}' (Yocto/Poky SDK)
by wine-bugs＠winehq.org 21 Jan '21

21 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=46079 Bug ID: 46079 Summary: Support 32-bit ARM hard-float cross-toolchains with GNU binutils assembler that doesn't implicitly assume '.fpu {vfp,neon}' (Yocto/Poky SDK) Product: Wine Version: 3.19 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, after working around bug 46053 ("Support cross-toolchains that need target sysroot explicitly passed via ' --sysroot' command-line option (Yocto/Poky SDK)") by having 'winegcc' passing the target sysroot to the cross-compiler/linker via '--sysroot', aarch64 Wine now cross compiles successfully with a full target sysroot. -> aarch64-poky-linux ------------------------------------------------------------------------- Build Configuration: BB_VERSION = "1.38.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "fedora-28" TARGET_SYS = "aarch64-poky-linux" MACHINE = "qemuarm64" DISTRO = "poky" DISTRO_VERSION = "2.5.1" TUNE_FEATURES = "aarch64" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "sumo:d240b885f26e9b05c8db0364ab2ace9796709aad" meta-oe = "sumo:2bb21ef27c4b0c9d52d30b3b2c5a0160fd02b966" meta-clang = "sumo:1784b06e6b1a83748438b4bec7e079d735d5b608" ... ------------------------------------------------------------------------- Building for 32-bit ARMv7 hard-float fails (using the same mechanics). -> arm-poky-linux-gnueabi (cortexa9hf-vfpv3-poky-linux-gnueabi) ------------------------------------------------------------------------- Build Configuration: BB_VERSION = "1.38.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "fedora-28" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "qemuarma9" DISTRO = "poky" DISTRO_VERSION = "2.5.1" TUNE_FEATURES = "arm armv7a vfp vfpv3d16 vfpv3 callconvention-hard cortexa9" TARGET_FPU = "hard" meta meta-poky meta-yocto-bsp = "sumo:d240b885f26e9b05c8db0364ab2ace9796709aad" meta-oe = "sumo:2bb21ef27c4b0c9d52d30b3b2c5a0160fd02b966" meta-clang = "sumo:1784b06e6b1a83748438b4bec7e079d735d5b608" ... ------------------------------------------------------------------------- --- snip --- ... /home/focht/projects/wine/mainline-build-x86_64/tools/winegcc/winegcc -o d2d1.dll.so \ -B/home/focht/projects/wine/mainline-build-x86_64/tools/winebuild --sysroot=../.. -b \ arm-poky-linux-gnueabi -marm -mfloat-abi=hard -fasynchronous-unwind-tables -shared /home/focht/projects/wine/mainline-src/dlls/d2d1/d2d1.spec \ bitmap.o bitmap_render_target.o brush.o dc_render_target.o device.o effect.o factory.o geometry.o \ hwnd_render_target.o layer.o mesh.o state_block.o stroke.o wic_render_target.o version.res \ -ldwrite -ld3d10_1 ../../dlls/dxguid/libdxguid.a ../../dlls/uuid/libuuid.a -lgdi32 -luser32 \ -ladvapi32 ../../libs/port/libwine_port.a -Wb,-ddwrite -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed d2d1.IYX82U.s: Assembler messages: d2d1.IYX82U.s:291: Error: selected processor does not support `vpush {s0-s15}' in ARM mode d2d1.IYX82U.s:310: Error: selected processor does not support `vpush {s0-s15}' in ARM mode winebuild: arm-poky-linux-gnueabi-gcc failed with status 1 winegcc: /home/focht/projects/wine/mainline-build-x86_64/tools/winebuild/winebuild failed make[1]: *** [Makefile:1440: d2d1.dll.so] Error 2 make[1]: Leaving directory '/home/focht/projects/wine/mainline-build-arm/dlls/d2d1' make: *** [Makefile:8385: dlls/d2d1] Error 2 --- snip --- Re-executing failing last command with '-v -save-temps': --- snip --- /home/focht/projects/wine/mainline-build-x86_64/tools/winegcc/winegcc -v -save-temps -o d2d1.dll.so -B/home/focht/projects/wine/mainline-build-x86_64/tools/winebuild --sysroot=../.. -b arm-poky-linux-gnueabi -marm -mfloat-abi=hard -fasynchronous-unwind-tables -shared /home/focht/projects/wine/mainline-src/dlls/d2d1/d2d1.spec bitmap.o bitmap_render_target.o brush.o dc_render_target.o device.o effect.o factory.o geometry.o hwnd_render_target.o layer.o mesh.o state_block.o stroke.o wic_render_target.o version.res -ldwrite -ld3d10_1 ../../dlls/dxguid/libdxguid.a ../../dlls/uuid/libuuid.a -lgdi32 -luser32 -ladvapi32 ../../libs/port/libwine_port.a -Wb,-ddwrite -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed /home/focht/projects/wine/mainline-build-x86_64/tools/winebuild/winebuild -v --save-temps --target arm-poky-linux-gnueabi -fasynchronous-unwind-tables --cc-cmd=arm-poky-linux-gnueabi-gcc --ld-cmd=arm-poky-linux-gnueabi-ld -D_REENTRANT -fPIC --dll -o d2d1.dll-IpMxH8.spec.o -E /home/focht/projects/wine/mainline-src/dlls/d2d1/d2d1.spec -L../../dlls -L../../libs/wine -marm -mfloat-abi=hard -ddwrite -rversion.res -- bitmap.o bitmap_render_target.o brush.o dc_render_target.o device.o effect.o factory.o geometry.o hwnd_render_target.o layer.o mesh.o state_block.o stroke.o wic_render_target.o ../../dlls/dwrite/libdwrite.def ../../dlls/d3d10_1/libd3d10_1.def ../../dlls/dxguid/libdxguid.a ../../dlls/uuid/libuuid.a ../../dlls/gdi32/libgdi32.def ../../dlls/user32/libuser32.def ../../dlls/advapi32/libadvapi32.def ../../libs/port/libwine_port.a ../../dlls/winecrt0/libwinecrt0.a ../../dlls/kernel32/libkernel32.def ../../dlls/ntdll/libntdll.def arm-poky-linux-gnueabi-gcc -xassembler -c -o d2d1.nY1v31.o d2d1.CJoop5.s arm-poky-linux-gnueabi-ld -r -o d2d1.KKS2kZ.o d2d1.nY1v31.o bitmap.o bitmap_render_target.o brush.o dc_render_target.o device.o effect.o factory.o geometry.o hwnd_render_target.o layer.o mesh.o state_block.o stroke.o wic_render_target.o ../../dlls/dxguid/libdxguid.a ../../dlls/uuid/libuuid.a ../../libs/port/libwine_port.a ../../dlls/winecrt0/libwinecrt0.a arm-poky-linux-gnueabi-gcc -xassembler -c -o d2d1.dll-IpMxH8.spec.o d2d1.vn7wK8.s d2d1.vn7wK8.s: Assembler messages: d2d1.vn7wK8.s:291: Error: selected processor does not support `vpush {s0-s15}' in ARM mode d2d1.vn7wK8.s:310: Error: selected processor does not support `vpush {s0-s15}' in ARM mode winebuild: arm-poky-linux-gnueabi-gcc failed with status 1 winegcc: /home/focht/projects/wine/mainline-build-x86_64/tools/winebuild/winebuild failed --- snip --- $ cat d2d1.vn7wK8.s /* File generated automatically from /home/focht/projects/wine/mainline-src/dlls/d2d1/d2d1.spec; do not edit! */ /* This file can be copied, modified and distributed without restriction. */ .section ".text","ax" b 1f __wine_spec_pe_header: .skip 69632 1: .data .align 2 .globl __wine_spec_nt_header .hidden __wine_spec_nt_header __wine_spec_nt_header: .L__wine_spec_rva_base: ... .L__wine_spec_exports_funcs: .long D2D1CreateFactory .long D2D1MakeRotateMatrix .long D2D1MakeSkewMatrix .long D2D1IsMatrixInvertible .long D2D1InvertMatrix .long __wine_stub_D2D1ConvertColorSpace .long __wine_stub_D2D1CreateDevice .long __wine_stub_D2D1CreateDeviceContext .long __wine_stub_D2D1SinCos .long __wine_stub_D2D1Tan .long __wine_stub_D2D1Vec3Length ... __wine_spec_relay_entry_points: nop .align 2 .L__wine_spec_relay_entry_point_1: .cfi_startproc push {r0-r3} mov r2, SP push {LR} sub SP, #4 mov r1,#393216 ldr r0, 2f add r0, PC ldr IP, [r0, #4] 1: blx IP ldr IP, [SP, #4] add SP, #24 bx IP 2: .long .L__wine_spec_relay_descr-1b .cfi_endproc .align 2 .L__wine_spec_relay_entry_point_2: .cfi_startproc push {r0-r3} mov r2, SP vpush {s0-s15} push {LR} sub SP, #4 mov r1,#1 add r1,#65536 ldr r0, 2f add r0, PC ldr IP, [r0, #4] 1: blx IP ldr IP, [SP, #4] add SP, #88 bx IP 2: .long .L__wine_spec_relay_descr-1b .cfi_endproc .align 2 --- snip --- https://source.winehq.org/git/wine.git/blob/HEAD:/tools/winebuild/spec32.c#… --- snip --- ... case CPU_ARM: { unsigned int mask, val, count = 0; int j, has_float = 0; if (strcmp( float_abi_option, "soft" )) for (j = 0; j < odp->u.func.nb_args && !has_float; j++) has_float = is_float_arg( odp, j ); val = (odp->u.func.args_str_offset << 16) | (i - spec->base); output( "\tpush {r0-r3}\n" ); output( "\tmov r2, SP\n"); if (has_float) output( "\tvpush {s0-s15}\n" ); output( "\tpush {LR}\n" ); output( "\tsub SP, #4\n"); for (mask = 0xff; mask; mask <<= 8) if (val & mask) output( "\t%s r1,#%u\n", count++ ? "add" : "mov", val & mask ); if (!count) output( "\tmov r1,#0\n" ); output( "\tldr r0, 2f\n"); output( "\tadd r0, PC\n"); output( "\tldr IP, [r0, #4]\n"); output( "1:\tblx IP\n"); output( "\tldr IP, [SP, #4]\n" ); output( "\tadd SP, #%u\n", 24 + (has_float ? 64 : 0) ); output( "\tbx IP\n"); output( "2:\t.long .L__wine_spec_relay_descr-1b\n" ); break; ... --- snip --- The code was introduced by commit https://source.winehq.org/git/wine.git/commitdiff/5e3534ee411a8c5baea502270… ("ntdll: Fix handling of floating point arguments in relay debugging on ARM.") The problem is that Wine makes the assumption that the assembler from hardfloat binutils implicitly assumes '.fpu {vfp,neon}' without any command line options. This isn't necessarily true for most hard-float cross-toolchains but for native toolchains, running on actual targets. Usually this is solved by the cross-toolchain environment by passing the proper '-mfloat-abi=' and/or '-mfpu=' options when cross-compiling. Simple test with .c file: --- snip --- $ cat vfptest.c void foo(void){ __asm__ volatile("fadds s0, s0, s0"); } --- snip --- --- snip --- $ arm-poky-linux-gnueabi-gcc -c vfptest.c /tmp/cc3DpeRI.s: Assembler messages: /tmp/cc3DpeRI.s:27: Error: selected processor does not support `fadds s0,s0,s0' in ARM mode $ arm-poky-linux-gnueabi-gcc -mfloat-abi=hard -c vfptest.c --- snip --- Test to show the available fpu target options: --- snip --- $ arm-poky-linux-gnueabi-gcc -mfpu=? arm-poky-linux-gnueabi-gcc: error: unrecognized argument in option ‘-mfpu=?’ arm-poky-linux-gnueabi-gcc: note: valid arguments to ‘-mfpu=’ are: auto crypto-neon-fp-armv8 fp-armv8 fpv4-sp-d16 fpv5-d16 fpv5-sp-d16 neon neon-fp-armv8 neon-fp16 neon-vfpv3 neon-vfpv4 vfp vfp3 vfpv2 vfpv3 vfpv3-d16 vfpv3-d16-fp16 vfpv3-fp16 vfpv3xd vfpv3xd-fp16 vfpv4 vfpv4-d16 arm-poky-linux-gnueabi-gcc: fatal error: no input files compilation terminated. --- snip --- Simple test with assembly file, illustrating the problem with Wine: --- snip --- $ cat vfptest.S .text test: fadds s0, s0, s0 --- snip --- NOTE: 'vfp' is an alias for 'vfpv2', 'neon' is an alias for 'neon-vfpv3' --- snip --- $ arm-poky-linux-gnueabi-gcc -c vfptest.s vfptest.s: Assembler messages: vfptest.s:3: Error: selected processor does not support `fadds s0,s0,s0' in ARM mode $ arm-poky-linux-gnueabi-gcc -c -mfloat-abi=hard vfptest.s vfptest.s: Assembler messages: vfptest.s:3: Error: selected processor does not support `fadds s0,s0,s0' in ARM mode $ arm-poky-linux-gnueabi-gcc -c -mfpu=vfp vfptest.s $ arm-poky-linux-gnueabi-gcc -c -mfpu=vfpv2 vfptest.s $ arm-poky-linux-gnueabi-gcc -c -mfpu=vfpv3 vfptest.s $ arm-poky-linux-gnueabi-gcc -c -mfpu=vfpv4 vfptest.s $ arm-poky-linux-gnueabi-gcc -c -mfpu=neon vfptest.s ... --- snip --- Unlike using C with inline assembly, real assembly sources need either '.fpu' directive, or '-mfpu=' option provided in the command line. Using CFLAGS, EXTRACFLAGS to set '-mfpu=' doesn't work because of the 'winegcc' wrapper limitation (like bug 46053 it builds a custom command line, not passing these option down). Forcing to a use hardfloat binutils with assembler that implicitly assumes '.fpu vfp' without any command line options is IMHO not feasible. I don't want to change/hack upstream toolchain projects. Changing 'winebuild' to add explicit '.fpu vfp' or '.fpu neon' directives to the assembly sources in case of 32-bit ARM hard-float seems reasonable to me. https://source.winehq.org/git/wine.git/blob/HEAD:/tools/winebuild/spec32.c Simple test: --- snip --- $ cat vfptest.s .fpu vfp .text test: fadds s0, s0, s0 --- snip --- --- snip --- $ arm-poky-linux-gnueabi-gcc -c vfptest.s --- snip --- With that problem fixed, Wine now cross compiles successfully with a full 32-bit ARM hardfloat target sysroot (same x11/freetype/libxml2 etc. deps as for my x86_64 host). Next step would be running apps/tests on my x86_64 host with 'qemuarm64' and 'qemuarma9' using the generic ARM system emulation with the 'virt machine' machine which also supports 'virtio-gpu' for full graphics stack. $ wine --version wine-3.19-117-g4852130c82 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 6

[Bug 265] Copy pasting into a wine app works only once
by WineHQ Bugzilla 20 Jan '21

20 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=265 abuy(a)protonmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abuy(a)protonmail.com -- 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 0

[Bug 50532] New: get_timezone_info doing binary search in the wrong way
by WineHQ Bugzilla 20 Jan '21

20 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=50532 Bug ID: 50532 Summary: get_timezone_info doing binary search in the wrong way Product: Wine Version: 6.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: gmascellani(a)codeweavers.com Distribution: --- get_timezone_info in dlls/ntdll/unix/system.c appears to compute the daylight saving time changes for a given year in a smelly if not buggy way. I don't have any specific examples of mistaken computations, but the code seems to basically work by chance. More specifically, the indention of the code seems to be the following: * two time_t values are computed, corresponding to the beginning and the end of the requested year (year_start and year_end); * a binary search procedure is used to narrow down that interval around a DST change event. However, this cannot work in general, because binary searches only work for monotonic data, and DST is not monotonic (each year it switches forth and back, assuming there is DST at all). The algorithm works "by chance", because it first tests the beginning of the interval and then half of the interval, and usually beginning of January and beginning of June are on different DST values; then the algorithm recurses on the first half of the year, and there DST is monotonic (again, usually; I don't know if this is always true). Moreover, year_end is also set to an invalid value (0th day of 12th month, which is a month past December). Doing the "arithmetic" this corresponds to 31st of December, but is that a supported way to specify it? Why not directly setting 31st of December? Anyway, the core of this bug is the issue with binary search. -- 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 0

[Bug 50531] New: Windows 3D Movie Maker fails to import or save sound recordings
by WineHQ Bugzilla 20 Jan '21

20 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=50531 Bug ID: 50531 Summary: Windows 3D Movie Maker fails to import or save sound recordings Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: zenithgraymgmt(a)gmail.com Distribution: --- Recording your own sounds via microphone or importing WAV files in Windows 3D Movie Maker shows an ingame dialog box stating "Sorry. We can't use that sound file. Try using another sound file or one of the sounds from 3D Movie Maker." 1) Start a new movie. 2) Click the "Sounds" button at the top, then the Speech button (which is represented by a pair of red lips). 3) Click either the microphone or briefcase icon at the bottom left to record or import an audio file, respectively. 4) Either record microphone input or open a WAV file from your computer. After recording microphone input, type in a filename for the recorded sound file and click "OK". The ingame dialog box I mentioned above shows. The application should either import the recording (which plays back correctly after stopping the recording) or the WAV file into the game. Build 2021-01-17 on Arch Linux This bug has been mentioned before in multiple test results on the AppDB page for Windows 3D Movie Maker, but hasn't been reported on Bugzilla prior to now. I think this may have something to do with msacm.dll, as the only useful debug/console output given when this happens is "00ec:fixme:msacm:modSetVolume stub". -- 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 0

[Bug 48334] New: Cannot instal Forza Horizon 3
by WineHQ Bugzilla 19 Jan '21

19 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=48334 Bug ID: 48334 Summary: Cannot instal Forza Horizon 3 Product: Wine Version: 5.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Atempts to instal game results in a window pop-up that says: Runtime error at (-1:0): Cannot import dll:<utf8>kernelbase.dll This error occurs with winetricks corefonts installed and also when not installed. -- 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 46174] New: Fix for Bug 46066 in Wine 3.20 Breaks Voice Chat Feature in Halo Online
by wine-bugs＠winehq.org 19 Jan '21

19 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=46174 Bug ID: 46174 Summary: Fix for Bug 46066 in Wine 3.20 Breaks Voice Chat Feature in Halo Online Product: Wine-staging Version: 3.20 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rstrube(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 62832 --> https://bugs.winehq.org/attachment.cgi?id=62832 Output when running Halo Online and crash occurs. After upgrading to Wine Staging 3.20 I noticed that Halo Online would hang as soon as a I joined any multiplayer match. After some investigation, I noticed that disabling the voice chat feature would cause the game to function correctly. With Wine Staging 3.19 the voice chat feature worked correctly. I noticed in the release notes for 3.20 a stub DLL (qwave.dll) was added. This was to fix Bug 46066. I believe this is causing the crash / hang with Halo Online. It might also affect other games with in game voice chat functionality. I've attached the output from wine when running the game and when the crash occurs. The key line is: wine: Call from 0x7b43e10c to unimplemented function qwave.dll.QOSCreateHandle, aborting Which then calls Audio Read timeouts, which cause the entire game to crash. Thanks! Rob -- 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 28

[Bug 41212] New: Alt-Tab in full-screen on resolutions other than native causes a crash
by wine-bugs＠winehq.org 19 Jan '21

19 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=41212 Bug ID: 41212 Summary: Alt-Tab in full-screen on resolutions other than native causes a crash Product: Wine Version: 1.9.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mackle9(a)hotmail.com Distribution: --- In Starcraft II, an Alt-Tab in full-screen mode on a resolution lower than native will cause the application to crash. Apparently Warcraft is also affected (unconfirmed). -- 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 11

[Bug 48239] New: MTGA Launcher fails to download the game (regression)
by WineHQ Bugzilla 19 Jan '21

19 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=48239 Bug ID: 48239 Summary: MTGA Launcher fails to download the game (regression) Product: Wine Version: 4.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: --- How to reproduce: - create a 32-bit prefix - download winetricks with new powershell verb (https://github.com/Winetricks/winetricks/pull/1440) - install these verbs into the prefix: powershell arial d3dcompiler_47 dotnet472 - set Windows version to 10 - install Magic: The Gathering Arena - Launch MTGALauncher.exe The launcher will try to download the game but then return "Oops! Something went wrong while updating". Seeing how this wasn't an issue before, I've run a bisect and found that 2c68c530afbe704698f5a38674e7c72806c7c07a (kernel32: Move file time functions to kernelbase.) was the cause of the regression. Reverting that commit against Wine 4.17 fixes the issue. Should note that this doesn't happen with version set to "Windows 7". Let me know if any logs will be needed from me with any specific debug channels. -- 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 7

[Bug 50523] New: The LinkSoft Secret! Desktop fails to sync after update to version 6.0
by WineHQ Bugzilla 18 Jan '21

18 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=50523 Bug ID: 50523 Summary: The LinkSoft Secret! Desktop fails to sync after update to version 6.0 Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq.org(a)wombatz.com Distribution: --- This is in regard to the desktop application for the LinkSoft "Secret!" program. https://www.linkesoft.com/secret/download.html There is a sync function that opens TCP port 8800 on the windows desktop side which the Android application then connects to for sync'ing changes in the underlying database. The symptom is an error from the Android application that it can not sync and to check your wifi connection. This first happened while I was using the version of Wine supplied by Fedora, while on Fedora 32. I found that they were providing a more "bleeding edge" version compared to what WineHQ was providing so I un-installed the Fedora version and installed winehq-stable using the WineHQ repository. That did fix the issue. A few days ago winehq-stable updated to version 6.0.0-2.1.x86_64 and the problem returned. My solution was to un-install wine, disable the repo and do a local dnf install of the three rpms for 5.0.3-2.2.x86_64 from your download page. This did fix the problem but I figure that I should open a bug report to see if the issue can be resolved. I had a VirtualBox Fedora 33 install that still had the 5 version, so I have used that to replicate the issue... Test with: winehq-stable-5.0.3-2.2.x86_64 wine-stable64-5.0.3-2.2.x86_64 wine-stable-common-5.0.3-2.2.i686 Secret! Desktop 6.5.4.22 Works! Did: full dnf upgrade New version: winehq-stable-6.0.0-2.1.x86_64 wine-stable64-6.0.0-2.1.x86_64 wine-stable-common-6.0.0-2.1.i686 Sync fails. Let me know what sort of debugging info I can provide. -- 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 0