October 2020 - Wine-Bugs - list.winehq.org

[Bug 45124] New: Fortnite: crash when loading battle royal lobby
by wine-bugs＠winehq.org Oct. 10, 2020

Oct. 10, 2020

https://bugs.winehq.org/show_bug.cgi?id=45124 Bug ID: 45124 Summary: Fortnite: crash when loading battle royal lobby Product: Wine Version: 3.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ado92300(a)gmail.com Distribution: --- Created attachment 61306 --> https://bugs.winehq.org/attachment.cgi?id=61306 wine log of launching fortnite As of Fortnite 4.0/for now, battle eye is not required to play fortnite and when run through wine the launcher will set -nobe (no battleeye) and fortnite launches with out this bug https://bugs.winehq.org/show_bug.cgi?id=41670. But once you load the title screen and select battle royal it crashes without a clear error (in wine output). I included the log of wine64 (Wine 3.7 Staging) and the UE4 Log for fortnite the only dll override set is shcore to disabled because the launcher wont load with it note: sometimes i can hear the battle royal intro video but never see it -- 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 5

[Bug 32073] New: Some chars are mapped as dead key
by wine-bugs＠winehq.org Oct. 10, 2020

Oct. 10, 2020

http://bugs.winehq.org/show_bug.cgi?id=32073 Bug #: 32073 Summary: Some chars are mapped as dead key Product: Wine Version: 1.5.16 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: cerebro.alexiel(a)gmail.com Classification: Unclassified When I use TapTouche, a typing training software, it warns me my keyboard is mis-configured and disables automatically some exercices. I installed it in an XP VM, compared with wine and found that exercices using the following chars were not available in wine : é ç à ù â ê û î ô É È Ç À Ù Â Ê Û Î Ô Thanks to +relay and +key,+keyboard, I found that VkKeyScan(0xe7) returns -1 in wine, 0x39 in windows VkKeyScan(0xe8) returns -1 in wine, 0x37 in windows I have a french keyboard and as you may have guessed, the 7 key contains 'è' and '`' while the 9 key contains 'ç' and '^'. For the following, I only focus on the 7 key (keycode 16) as it's the same issue for the 9 key. I played with XkbKeycodeToKeysym(display, 16, 0, [0-4]) and it returns 0xe8 'è' / 0x37 '7' / 0x60 '`' / 0xac6 '⅞'. showing my keyboard is correctly mapped/configured so the issue is on the wine side. I looked at the source code and found the issue was in the loop at http://source.winehq.org/git/wine.git/blob/HEAD:/dlls/winex11.drv/keyboard.… More precisely, line 1728, keycode_to_keysym returns 0xe8 for i=0, XkbTranslateKeySym fails and as 0xe8 > 0x7F (the lastest ascii char), ckey[i] is 0. There is an explicit FIXME but as I don't fully understand it, I prefer filing a bug. If you need any info, testcase or log, just let me know. -- 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 3

[Bug 12443] New: Multi-monitor handling in ddraw/d3d
by wine-bugs＠winehq.org Oct. 10, 2020

Oct. 10, 2020

http://bugs.winehq.org/show_bug.cgi?id=12443 Summary: Multi-monitor handling in ddraw/d3d Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: thestig(a)google.com In bug 1347, I write: I'm guessing slideshows in Picasa with multi-monitors is affected by this as well. When starting the slideshow, the entire screen gets blanked. After the slideshow ends, the screen that showed the slideshow gets restored, but the secondary screen remains blank until it gets drawn over. Stefan replied: This could as well be a bug with multi-monitor handling in ddraw, as ddraw is pretty ignorant to that. Yes, a bug on d3d multi-monitor handling is a good idea I think. Thus this bug serves as a reminder to look at multi-monitor handling issues in ddraw/d3d. -- 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 14

[Bug 7416] Support multiple independent displays for PowerPoint, OpenOffice.org, etc
by WineHQ Bugzilla Oct. 10, 2020

Oct. 10, 2020

https://bugs.winehq.org/show_bug.cgi?id=7416 Marcin Zajaczkowski <mszpak(a)wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mszpak(a)wp.pl -- 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 49973] New: 64-bit Cheat Engine does not properly handle 32-bit processes
by WineHQ Bugzilla Oct. 10, 2020

Oct. 10, 2020

https://bugs.winehq.org/show_bug.cgi?id=49973 Bug ID: 49973 Summary: 64-bit Cheat Engine does not properly handle 32-bit processes Product: Wine Version: 5.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: subgraph93(a)gmail.com Distribution: --- Created attachment 68374 --> https://bugs.winehq.org/attachment.cgi?id=68374 cheatengine-x86_64.exe attaching to Tutorial-i386.exe Distribution: Ubuntu 20.04 Program download: Cheat Engine 7.1, available from https://cheatengine.org/downloads.php (the actual link appears to change on every page refresh) Program source code: available at https://github.com/cheat-engine/cheat-engine/ On Windows 7, 64-bit Cheat Engine (cheatengine-x86_64.exe) works fine for 32-bit processes as well as 64-bit processes. However, when using Wine, 64-bit CE cannot properly attach to 32-bit processes. 32-bit CE works fine for 32-bit processes. Explaining in some more detail below. To attach CE to a program, start CE and the program (in any order), then when CE opens, click the "Open process" icon (it looks like a desktop monitor with a magnifying glass; it's below the "File" menu button) and select the target process from the list. CE comes with its own tutorial programs (32-bit and 64-bit), so installing another, unrelated program shouldn't be needed for testing. A simple way to identify whether the issue exists is to add an address using the executable name. To do this, click the "Add Address Manually" button in CE, enter ["programname.exe"] (with the square brackets; e. g. ["Tutorial-i386.exe"]) in the "Address" box, then click OK. Note the new entry in the address list below and check the value in the "Address" column for that entry. When using 32-bit CE on a 32-bit program, the address column shows the actual address (e. g. 00905A4D) and may show a value, but when using 64-bit CE on a 32-bit program (something that works on Windows), the address column shows the text with the program name – something like (["Tutorial-i386.exe"]), with the parentheses, – and the value is just question marks. The most obvious impact of the issue is that cheat tables and assembly scripts cannot work unless the base address (is this the right term?) of the .exe is hardcoded. Other problems with using 64-bit CE on 32-bit programs are that the code finder does not work (so you can't complete Step 5 of the tutorial, which requires you to overwrite an instruction that changes a value; you can't find that instruction), and that pointer scans do not work. (I'll file other tickets if these turn out to be their own issues; but both features work fine if 32-bit CE is used on a 32-bit process.) I set the version as 5.4 because it's the first version I noticed this issue in. This issue was also present in every newer version up to 5.19 (both devel and staging channels). I don't think it's a regression. I didn't use Cheat Engine with Wine versions before 5.4. Attached the terminal output for the 5.19-staging test with 64-bit CE and the 32-bit tutorial. -- 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 49971] New: LTC2983 demo software Version 1.7.9 adjusting window size is very slow
by WineHQ Bugzilla Oct. 10, 2020

Oct. 10, 2020

https://bugs.winehq.org/show_bug.cgi?id=49971 Bug ID: 49971 Summary: LTC2983 demo software Version 1.7.9 adjusting window size is very slow Product: Wine Version: 5.18 Hardware: x86-64 URL: https://www.analog.com/en/products/ltc2983.html#produc t-requirement OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: ArchLinux Created attachment 68371 --> https://bugs.winehq.org/attachment.cgi?id=68371 console messages Summary LTC2983 demo software Version 1.7.9 adjusting window size is very slow Download location https://www.analog.com/en/products/ltc2983.html#product-requirement http://swdownloads.analog.com/ltc2983/installltc2983.zip $ sha256sum installltc2983.zip b0b4b1ef8447adfdb4cb30dae8742d1ca5458e86bc17cf8e4dafa33978eecd67 installltc2983.zip $ unzip installltc2983.zip $ cd InstallLTC2983/ Steps to reproduce: 1) Install the program: $ wine CDM20824_Setup.exe This does not seem to do anything $ wine start ins2983.msi and accept the defaults. 2) Start the program: $ wine LTC2983.exe 3) Adjust the window size. Now the program redraws the elements on the screen. This takes multiple seconds. My versions $ wine --version wine-5.18 (Staging) $ pacman -Q wine wine-staging 5.18-1 uname -a Linux cedric-p4 5.8.14-arch1-1 #1 SMP PREEMPT Wed, 07 Oct 2020 23:59:46 +0000 x86_64 GNU/Linux -- 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 8051] The Sims 2 demo needs support for software vertex processing
by WineHQ Bugzilla Oct. 10, 2020

Oct. 10, 2020

https://bugs.winehq.org/show_bug.cgi?id=8051 --- Comment #184 from Chebanenko Igor <chebanenkoigor93(a)gmail.com> --- I found this: https://www.braynzarsoft.net/viewtutorial/q16390-07-dx9-index-buffers Quote: Index Buffers are used to speed up or optimize your program. They are pretty much the same thing as Vertex Buffers, but instead of storing vertices, it stores indeces. Is it possible to make logic similar with Index Buffers,but for Vertex Buffer routines? Any ideas? -- 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 14398] New: X3 Reunion crash on opening comm menu
by wine-bugs＠winehq.org Oct. 10, 2020

Oct. 10, 2020

http://bugs.winehq.org/show_bug.cgi?id=14398 Summary: X3 Reunion crash on opening comm menu Product: Wine Version: 1.1.0 Platform: PC URL: http://www.egosoft.com/games/x3/info_en.php OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: pablo.bueti(a)gmail.com Created an attachment (id=14712) --> (http://bugs.winehq.org/attachment.cgi?id=14712) The console outuput when game hangs When selecting a ship and pressing C to open comms dialog the game hangs, there are several fixme:amstream lines in console that don't stop showing while games is hang. After pressing Ctrl-c in console I got the output to report the error here (attached). This was tested on openSuSe 10.3, kernel 2.6.22.18-0.2-default and Wine 1.1.0 without modifications. Also videos and sounds aparently in mp3 format don't play. I found that I'm not the only having this problem and seems to be related to amstream.dll. Also tried using native dll but don't help (game crashes and return to console). -- 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 14

[Bug 49967] New: wine-staging fails to compile
by WineHQ Bugzilla Oct. 10, 2020

Oct. 10, 2020

https://bugs.winehq.org/show_bug.cgi?id=49967 Bug ID: 49967 Summary: wine-staging fails to compile Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: --- Since a few days wine-staging fails to compile for me. I don`t know if this is a fault at my end, but i guess not because regular wine compiles fine. This is on debian 10 (Description: Debian GNU/Linux bullseye/sid) Error: gcc -m32 -c -o dlls/bcrypt/gcrypt.o ../wine/dlls/bcrypt/gcrypt.c -Idlls/bcrypt -I../wine/dlls/bcrypt -Iinclude \ -I../wine/include -I/usr/include/p11-kit-1 -D__WINESRC__ -D_UCRT -DWINE_UNIX_LIB -D_REENTRANT \ -fno-PIC -fasynchronous-unwind-tables -Wall -pipe -fcf-protection=none -fno-stack-protector \ -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers \ -Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits \ -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op -gdwarf-2 \ -gstrict-dwarf -fno-omit-frame-pointer -g -O2 In file included from ../wine/dlls/bcrypt/gcrypt.c:280: ../wine/include/windef.h:116:24: error: unknown type name ‘va_list’ 116 | # define __ms_va_list va_list | ^~~~~~~ ../wine/include/winbase.h:2073:84: note: in expansion of macro ‘__ms_va_list’ 2073 | WINBASEAPI DWORD WINAPI FormatMessageA(DWORD,LPCVOID,DWORD,DWORD,LPSTR,DWORD,__ms_va_list*); | ^~~~~~~~~~~~ In file included from ../wine/dlls/bcrypt/gcrypt.c:281: ../wine/include/winbase.h:1613:1: note: ‘va_list’ is defined in header ‘<stdarg.h>’; did you forget to ‘#include <stdarg.h>’? 1612 | #include <poppack.h> +++ |+#include <stdarg.h> 1613 | In file included from ../wine/dlls/bcrypt/gcrypt.c:280: ../wine/include/windef.h:116:24: error: unknown type name ‘va_list’ 116 | # define __ms_va_list va_list | ^~~~~~~ ../wine/include/winbase.h:2074:85: note: in expansion of macro ‘__ms_va_list’ 2074 | WINBASEAPI DWORD WINAPI FormatMessageW(DWORD,LPCVOID,DWORD,DWORD,LPWSTR,DWORD,__ms_va_list*); | ^~~~~~~~~~~~ ../wine/include/windef.h:116:24: note: ‘va_list’ is defined in header ‘<stdarg.h>’; did you forget to ‘#include <stdarg.h>’? 116 | # define __ms_va_list va_list | ^~~~~~~ ../wine/include/winbase.h:2074:85: note: in expansion of macro ‘__ms_va_list’ 2074 | WINBASEAPI DWORD WINAPI FormatMessageW(DWORD,LPCVOID,DWORD,DWORD,LPWSTR,DWORD,__ms_va_list*); | ^~~~~~~~~~~~ ../wine/include/windef.h:116:24: error: unknown type name ‘va_list’ 116 | # define __ms_va_list va_list | ^~~~~~~ ../wine/include/winternl.h:3485:82: note: in expansion of macro ‘__ms_va_list’ 3485 | NTSYSAPI NTSTATUS WINAPI RtlFormatMessage(LPCWSTR,ULONG,BOOLEAN,BOOLEAN,BOOLEAN,__ms_va_list *,LPWSTR,ULONG,ULONG*); | ^~~~~~~~~~~~ In file included from ../wine/dlls/bcrypt/gcrypt.c:282: ../wine/include/winternl.h:27:1: note: ‘va_list’ is defined in header ‘<stdarg.h>’; did you forget to ‘#include <stdarg.h>’? 26 | #include <apiset.h> +++ |+#include <stdarg.h> 27 | In file included from ../wine/dlls/bcrypt/gcrypt.c:280: ../wine/include/windef.h:116:24: error: unknown type name ‘va_list’ 116 | # define __ms_va_list va_list | ^~~~~~~ ../wine/include/winternl.h:3486:84: note: in expansion of macro ‘__ms_va_list’ 3486 | NTSYSAPI NTSTATUS WINAPI RtlFormatMessageEx(LPCWSTR,ULONG,BOOLEAN,BOOLEAN,BOOLEAN,__ms_va_list *,LPWSTR,ULONG,ULONG*,ULONG); | ^~~~~~~~~~~~ ../wine/include/windef.h:116:24: note: ‘va_list’ is defined in header ‘<stdarg.h>’; did you forget to ‘#include <stdarg.h>’? 116 | # define __ms_va_list va_list | ^~~~~~~ ../wine/include/winternl.h:3486:84: note: in expansion of macro ‘__ms_va_list’ 3486 | NTSYSAPI NTSTATUS WINAPI RtlFormatMessageEx(LPCWSTR,ULONG,BOOLEAN,BOOLEAN,BOOLEAN,__ms_va_list *,LPWSTR,ULONG,ULONG*,ULONG); | ^~~~~~~~~~~~ ../wine/include/windef.h:116:24: error: unknown type name ‘va_list’ 116 | # define __ms_va_list va_list | ^~~~~~~ ../wine/include/winternl.h:3716:58: note: in expansion of macro ‘__ms_va_list’ 3716 | NTSYSAPI NTSTATUS WINAPI vDbgPrintEx(ULONG,ULONG,LPCSTR,__ms_va_list); | ^~~~~~~~~~~~ ../wine/include/windef.h:116:24: note: ‘va_list’ is defined in header ‘<stdarg.h>’; did you forget to ‘#include <stdarg.h>’? 116 | # define __ms_va_list va_list | ^~~~~~~ ../wine/include/winternl.h:3716:58: note: in expansion of macro ‘__ms_va_list’ 3716 | NTSYSAPI NTSTATUS WINAPI vDbgPrintEx(ULONG,ULONG,LPCSTR,__ms_va_list); | ^~~~~~~~~~~~ ../wine/include/windef.h:116:24: error: unknown type name ‘va_list’ 116 | # define __ms_va_list va_list | ^~~~~~~ ../wine/include/winternl.h:3717:75: note: in expansion of macro ‘__ms_va_list’ 3717 | NTSYSAPI NTSTATUS WINAPI vDbgPrintExWithPrefix(LPCSTR,ULONG,ULONG,LPCSTR,__ms_va_list); | ^~~~~~~~~~~~ ../wine/include/windef.h:116:24: note: ‘va_list’ is defined in header ‘<stdarg.h>’; did you forget to ‘#include <stdarg.h>’? 116 | # define __ms_va_list va_list | ^~~~~~~ ../wine/include/winternl.h:3717:75: note: in expansion of macro ‘__ms_va_list’ 3717 | NTSYSAPI NTSTATUS WINAPI vDbgPrintExWithPrefix(LPCSTR,ULONG,ULONG,LPCSTR,__ms_va_list); | ^~~~~~~~~~~~ make: *** [Makefile:11624: dlls/bcrypt/gcrypt.o] Error 1 make: *** Waiting for unfinished jobs.... -- 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 49823] New: Wine-staging 5.17 build fails on older Debian/Ubuntu versions
by WineHQ Bugzilla Oct. 9, 2020

Oct. 9, 2020

https://bugs.winehq.org/show_bug.cgi?id=49823 Bug ID: 49823 Summary: Wine-staging 5.17 build fails on older Debian/Ubuntu versions Product: Wine-staging Version: 5.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dimesio(a)earthlink.net CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Building the wine-staging packages failed on Debian 9, Ubuntu 16.04, and Ubuntu 18.04. No problem on newer Debian/Ubuntu versions, Fedora, or the wine-devel packages. [ 846s] unix/file.c: In function 'FILE_CreateSymlink': [ 846s] unix/file.c:6093:48: error: 'RENAME_EXCHANGE' undeclared (first use in this function); did you mean 'SONAME_LIBSANE'? [ 846s] if (!renameat2( -1, tmplink, -1, unix_src, RENAME_EXCHANGE )) [ 846s] ^~~~~~~~~~~~~~~ [ 846s] SONAME_LIBSANE [ 846s] unix/file.c:6093:48: note: each undeclared identifier is reported only once for each function it appears in [ 846s] unix/file.c: In function 'FILE_RemoveSymlink': [ 846s] unix/file.c:6418:49: error: 'RENAME_EXCHANGE' undeclared (first use in this function); did you mean 'SONAME_LIBSANE'? [ 846s] if (!renameat2( -1, tmpfile, -1, unix_name, RENAME_EXCHANGE )) [ 846s] ^~~~~~~~~~~~~~~ [ 846s] SONAME_LIBSANE [ 846s] Makefile:945: recipe for target 'unix/file.o' failed [ 846s] make[2]: *** [unix/file.o] Error 1 [ 846s] make[2]: Leaving directory '/usr/src/packages/BUILD/dlls/ntdll' [ 846s] Makefile:9337: recipe for target 'dlls/ntdll' failed [ 846s] make[1]: *** [dlls/ntdll] Error 2 -- 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