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

[Bug 50198] New: SHMEM_FAILURE on Blizzard products on FAT32
by WineHQ Bugzilla 23 Apr '21

23 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=50198 Bug ID: 50198 Summary: SHMEM_FAILURE on Blizzard products on FAT32 Product: Wine-staging Version: 5.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blc+wine(a)mail.vanade.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68712 --> https://bugs.winehq.org/attachment.cgi?id=68712 Battle.net application log showing failure near end. I noticed that WoW and Battle.net applications have stopped working properly when running off of FAT32 formatted partitions in Linux. The application logfiles seem to indicate that the software was unable to create and access shared memory files which had been working in the past, at least with older versions of Wine. Attached is from battle.net application when it's trying to update WoW. WoW also gives an apparently similar error when it tries top open the CAS datafiles. I had not upgraded the kernel so supposedly shared memory files that worked in the past on FAT32 should still work. I don't know if this was a deliberate change because of security issues where anyone can open files on FAT32 and thus invade shared memory. Windows 7 does not exhibit this problem on the same disk and Battle.net updates fine. As this is on a limited space SSD, I don't have enough disk space to try this on ext4fs to see if the problem goes away or not. I do have another machine that does not exhibit this problem on ext4fs. The WoW installation is on FAT32 so I could easily test on Windows 7 with limited disk space. -- 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 49753] New: server_ioctl_file: Syscall param writev(vector[...]) points to uninitialised byte(s)
by WineHQ Bugzilla 23 Apr '21

23 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=49753 Bug ID: 49753 Summary: server_ioctl_file: Syscall param writev(vector[...]) points to uninitialised byte(s) Product: Wine Version: 5.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: jeffersoncarpenter2(a)gmail.com Distribution: --- Created attachment 68056 --> https://bugs.winehq.org/attachment.cgi?id=68056 Valgrind output. Occurs as of commit 5bb27d1edb2. Valgrind output attached. Full valgrind trace: ==26644== Syscall param writev(vector[...]) points to uninitialised byte(s) ==26644== at 0x4322F07: writev (writev.c:26) ==26644== by 0x48530E2: send_request (server.c:213) ==26644== by 0x4853224: server_call_unlocked (server.c:273) ==26644== by 0x48722CF: virtual_locked_server_call (virtual.c:3015) ==26644== by 0x483F666: server_ioctl_file (file.c:4730) ==26644== by 0x484143A: NtDeviceIoControlFile (file.c:5561) ==26644== by 0x4838F6E: get_mountmgr_fs_info (file.c:1975) ==26644== by 0x4842E3A: NtQueryVolumeInformationFile (file.c:6380) ==26644== by 0x482F1BD: __wine_syscall_dispatcher (in /home/rofl/wine32-build-debug-nomingw/dlls/ntdll/ntdll.so) ==26644== by 0x7BC32F9B: NtQueryVolumeInformationFile (in /home/rofl/wine32-build-debug-nomingw/dlls/ntdll/ntdll.dll.so) ==26644== by 0x7B0403EB: GetFileInformationByHandle (file.c:2930) ==26644== by 0x536D262: MSVCRT__fstat64 (file.c:1781) ==26644== by 0x536D4B5: MSVCRT__fstat32 (file.c:1839) ==26644== by 0x512498B: fstat (stat.h:222) ==26644== by 0x5128EC5: update_wineprefix (wineboot.c:1437) ==26644== by 0x5129BF7: main (wineboot.c:1671) -- 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 49815] New: e9090e1c903578b30118ce9559c1824361abc6da prevents XBox controller from being mapped
by WineHQ Bugzilla 23 Apr '21

23 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=49815 Bug ID: 49815 Summary: e9090e1c903578b30118ce9559c1824361abc6da prevents XBox controller from being mapped Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: kyle.devir(a)mykolab.com Distribution: --- First bad commit prevents XBox controller buttons from being mapped. I first noticed this after it stopped being detected in Bayonetta. This is the first bad commit: https://github.com/wine-mirror/wine/commit/e9090e1c903578b30118ce9559c18243… Last good commit should be: https://github.com/wine-mirror/wine/commit/ec02224941eedf16b8b043964519f636… -- 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 19

[Bug 50909] New: Horizon Zero Dawn: Complete Edition (GOG.com version) - Installer Will Not Run
by WineHQ Bugzilla 23 Apr '21

23 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=50909 Bug ID: 50909 Summary: Horizon Zero Dawn: Complete Edition (GOG.com version) - Installer Will Not Run Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gregory(a)opera.id.au Distribution: --- After downloading all of the respective files for an "offline" (NOT "GOG Galaxy") installation, and launching "setup_horizon_zero_dawntm_complete_edition_6278995_(64bit)_(44600).exe" with "WINE Windows Program Loader", the cursor animates to show that "something" is happening... After approximately fifteen (15) seconds, the cursor returns to normal and it becomes evident that the installer has failed to run. This was tested and replicated with "version 6278995" of the GOG.com version of "Horizon Zero Dawn: Complete Edition". -- 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 50870] New: game 'rise of agon' lobby crashes repeatedly during updating
by WineHQ Bugzilla 23 Apr '21

23 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=50870 Bug ID: 50870 Summary: game 'rise of agon' lobby crashes repeatedly during updating Product: Wine Version: 5.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: vascoman10(a)hotmail.com Distribution: --- download and install game 'rise of agon' works fine. once starting the lobby, the game crashes repeatedly during updating. https://www.riseofagon.com/ worked fine upto wine version 5.11, crashes repeatedly from wine 5.12, through wine 6.4 (current). regression testing reveals this: 7161dcd42653452a2373a7595a7020d0a59722f4 is the first bad commit commit 7161dcd42653452a2373a7595a7020d0a59722f4 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Jun 25 12:30:00 2020 +0200 ntdll: Return the current time and timezone bias in NtQuerySystemInformation(SystemTimeOfDayInformation). Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> dlls/ntdll/time.c | 50 ++++++--------------------------------------- dlls/ntdll/unix/system.c | 12 +++++++++-- dlls/wbemprox/builtin.c | 2 +- include/winternl.h | 8 ++++---- programs/taskmgr/perfdata.c | 4 ++-- 5 files changed, 23 insertions(+), 53 deletions(-) -- 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 35748] New: Blazing Angels 2: cannot initialize 3D engine
by wine-bugs＠winehq.org 23 Apr '21

23 Apr '21

http://bugs.winehq.org/show_bug.cgi?id=35748 Bug ID: 35748 Summary: Blazing Angels 2: cannot initialize 3D engine Product: Wine Version: 1.7.12 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: amlopezalonso(a)gmail.com Created attachment 47739 --> http://bugs.winehq.org/attachment.cgi?id=47739 BA2 start log in desktop mode. Installing and updating Blazing Angels 2 are OK. However, trying to start the game fails: 1) In fullscreen mode I only get a black screen. 2) In desktop mode (800x600) I get a popup: "Cannot initialize 3D engine". Other 3D games run fine. Attaching log. Regards, Antonio -- 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 50312] New: Cannot change settings of PSPad where requirement to write to program folder is needed
by WineHQ Bugzilla 23 Apr '21

23 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=50312 Bug ID: 50312 Summary: Cannot change settings of PSPad where requirement to write to program folder is needed Product: Wine Version: 5.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: juozaspo(a)gmail.com Distribution: --- Created attachment 68892 --> https://bugs.winehq.org/attachment.cgi?id=68892 Screenshot of Settings dialog I'm unable to change some settings of PSPad editor where it is required to write to program folder to change them. To program it appears as if it's been run as non-administrator user or contents of it's folder were read only. The affected settings are "Show Splash Screen" in "Program (part 2)", "Multi User Environment" and "Only One Program Instance" in "System integration" as shown in it's "Program Settings" dialog. They have a marker with a meaning of "write to PSPad folder" and all are greyed out. Also the program does not run for me while using wine devel/staging/etc version, as wine crash on startup as described in bug #50271, it works fine while using stable build. To reproduce: 1. Install PSPad using installer or extract zip archive to new folder 2. If program loads w/o problems (assuming you're using stable or any other working wine version) open program settings dialog (accessible via "Settings"->"Program Settings..." menu) Screenshots attached. -- 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 49760] New: World of Warcraft: stub NtQueryDirectoryObject
by WineHQ Bugzilla 23 Apr '21

23 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=49760 Bug ID: 49760 Summary: World of Warcraft: stub NtQueryDirectoryObject Product: Wine-staging Version: 5.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: loic.blot(a)unix-experience.fr CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hello, since recent wow build & wine 5.16 upgrade it seems some stub have been fixed but a new one appear which can be useful for the game i think, regarding to the call 04f4:fixme:sync:NtQueryDirectoryObject multiple entries not implemented I don't know in which context they call it, but it's when we are in game world map, while moving. Can you take a look/fix it ? Thanks -- 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 49579] New: Running .exe from programs with GUI uses wrong prefix in Wine 5.0
by WineHQ Bugzilla 23 Apr '21

23 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=49579 Bug ID: 49579 Summary: Running .exe from programs with GUI uses wrong prefix in Wine 5.0 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: charivari(a)online.de Distribution: --- When running an *.exe by doubleclicking on it in the fileexplorer (Thunar), Wine 5.0 will not run it in the standard prefix ~/.wine as it should, but instead in another existing prefix in ~/.local/share/wineprefixes/wine32. Winetricks shows the same behaviour, opening wine32 when told to open the standardprefix - though for some reason, it also shows wine32 among the secondary prefixes, while not showing wine at all. Running from console will produce the expected outcome of running in ~/.wine. This did not happen in Wine 4.0, and started happening immediately after the update to Wine 5.0, without any configuration changes. I've already checked .bash-rc and .profile and made sure there's no value set for $WINEPREFIX. While not exactly a major bug, it's a bother to work around for every single program. OS: Linux Mint 20 Xfce Wine: 5.0-3 -- 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 50797] New: Please sandbox all Wine applications on launch
by WineHQ Bugzilla 23 Apr '21

23 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=50797 Bug ID: 50797 Summary: Please sandbox all Wine applications on launch Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: luke.hutch(a)gmail.com Distribution: --- I had a Windows virus, running in WINE, wipe a large chunk of one of my Linux hard drives before I realized it and stopped the damage. Windows antivirus software is too complex to run in WINE, so all Windows applications run in WINE may damage a user's home directory. This leads to a very uneasy feeling whenever I launch any Windows application in WINE on Linux. There are now many ways to sandbox Linux applications, via a series of fairly new Linux kernel features, and also due to some libraries and systems built on top of these new isolation mechanisms. Please see my request here in the RedHat bug tracker: https://bugzilla.redhat.com/show_bug.cgi?id=1179507 It would actually be much better to fix this upstream in Wine than have just one vendor (RedHat) fix this in their distribution. -- 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