February 2021 - Wine-Bugs - list.winehq.org

[Bug 43296] New: Ultra VNC back buffer errors
by wine-bugs＠winehq.org April 23, 2021

April 23, 2021

https://bugs.winehq.org/show_bug.cgi?id=43296 Bug ID: 43296 Summary: Ultra VNC back buffer errors Product: Wine-staging Version: 2.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Dear Wine Staging, Would you fix this for me? wine-patched-staging-2.11.tar.gz, 32 bit UltraVNC-1.2.15_X86_Setup.exe http://www.uvnc.com/downloads/ultravnc.html WARNING: Lots of JUNKWARE !! $ env WINEPREFIX="/home/todd/.wine" /usr/local/bin/wine C:\\windows\\command\\start.exe /Unix /home/tony/.wine/dosdevices/c:/users/Public/Start\ Menu/Programs/UltraVNC/UltraVNC\ Viewer.lnk fixme:exec:SHELL_execute flags ignored: 0x00000100 fixme:exec:SHELL_execute flags ignored: 0x00004100 fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) [tony(a)rn4 Desktop]$ fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable. libGL error: unable to load driver: nouveau_dri.so libGL error: driver pointer missing libGL error: failed to load driver: nouveau libGL error: unable to load driver: swrast_dri.so libGL error: failed to load driver: swrast err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most likely your 32-bit OpenGL drivers haven't been installed correctly (using GL renderer "Gallium 0.4 on NVC4", version "1.4 (3.0 Mesa 11.2.2)"). fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16_UNORM needs different render target formats for different resource types. fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported. Please configure the application to use double buffering (1 back buffer) if possible. fixme:ver:GetCurrentPackageId (0xacea28 (nil)): stub fixme:d3d:check_fbo_compat Format WINED3DFMT_R16G16_UNORM needs different render target formats for different resource types. fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported. Please configure the application to use double buffering (1 back buffer) if possible. err:dialog:EndDialog got invalid window handle (0x70374); buggy app !? -- 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 4

[Bug 50557] New: USVFS (Mod Organizer 2) no longer working
by WineHQ Bugzilla April 23, 2021

April 23, 2021

https://bugs.winehq.org/show_bug.cgi?id=50557 Bug ID: 50557 Summary: USVFS (Mod Organizer 2) no longer working Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: joe(a)warhaggis.com Distribution: --- USVFS is a component of Mod Organizer 2. It uses an OverlayFS-style method to overlay mods on to (primarily Bethesda) games at runtime. The patch in #47832 (upstreamed in 4.21) fixed this until at *least* 5.13 when dlls/kernel32/file.c was largely migrated to dlls/kernelbase/file.c. In every Wine version after 5.0 USFVS fails to run. My attached logs are from USVFS's own debug log. The log suffixed wine-5.0 shows the functionality working as expected (if you search it for 'freeside' you will find a mod correctly overlayed). The log suffixed wine-6.0 for comparison shows the function not working. ---- I attempted to replace the applicable section in dlls/kernelbase/file.c to replicate the changes made to kernel32 in 4.21 but had no success, however I believe the problem is here somewhere. -- 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 18

[Bug 50461] New: Wine looking in /usr/bin/../../lib32/wine, should be /usr/bin/../lib32/wine
by WineHQ Bugzilla April 23, 2021

April 23, 2021

https://bugs.winehq.org/show_bug.cgi?id=50461 Bug ID: 50461 Summary: Wine looking in /usr/bin/../../lib32/wine, should be /usr/bin/../lib32/wine Product: Wine Version: 5.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bebing2(a)optimum.net Distribution: --- Previous version I was using, 4.19 staging, builds and installs fine. 5.20 when launching anything, but winecfg will trigger it, gets this: wine: could not load ntdll.so: /usr/bin/../../lib32/wine/ntdll.so: cannot open shared object file: No such file or directory Which resolves to root directory /lib32 but should resolve to /usr/lib32 Looks like it usually is /usr/bin/../lib32 not /usr/bin/../../lib32 I use LFS so it is likely it is not conforming to debian/ubuntu or whatever. I have a thread here where I tried some hacks to workaround to no avail, just in case it's useful: https://forum.winehq.org/viewtopic.php?f=8&t=34780 -- 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 24

[Bug 49684] New: Critical Crash Logos Bible Software Unusable (Regression)
by WineHQ Bugzilla April 23, 2021

April 23, 2021

https://bugs.winehq.org/show_bug.cgi?id=49684 Bug ID: 49684 Summary: Critical Crash Logos Bible Software Unusable (Regression) Product: Wine Version: 5.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: johnpgoodman(a)gmail.com Distribution: --- Created attachment 67925 --> https://bugs.winehq.org/attachment.cgi?id=67925 terminal output from crash Since the latest update from faithlife the app crashes on load and is no longer useable. Terminal output attached. Apologies, I don't understand it. Logos 8.15.0.0004. N.b. I was running winehq stable when this occurred. Updating to Dev 5.14 the crash is still there. -- 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 9

[Bug 34636] New: In Win95/98 mode Earthworm Jim demo reports missing dispdib.dll
by wine-bugs＠winehq.org April 23, 2021

April 23, 2021

http://bugs.winehq.org/show_bug.cgi?id=34636 Bug #: 34636 Summary: In Win95/98 mode Earthworm Jim demo reports missing dispdib.dll Product: Wine Version: 1.7.3 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winebugs140(a)gmail.com Classification: Unclassified The message reads 'Bad or missing dispdib.dll - error 11'. It doesn't show up in WinXP mode, but you need to set Win95/98 mode to get sound working. The problem occurs on Windows Vista too if you use Win95 compatibility mode. I don't get anything in the log. The demo unpacks files in DOS, but then you obtain a normal Windows app. Tested with: Windows Vista (without Wine), GeForce 9600M GS--the program works fine here Ubuntu 13.04, GeForce 9600M GS (NVIDIA driver 313) Mac OS X 10.7.5, ATI HD 2600 Pro, Mac Driver/X11 -- 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 6

[Bug 50198] New: SHMEM_FAILURE on Blizzard products on FAT32
by WineHQ Bugzilla April 23, 2021

April 23, 2021

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 49815] New: e9090e1c903578b30118ce9559c1824361abc6da prevents XBox controller from being mapped
by WineHQ Bugzilla April 23, 2021

April 23, 2021

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 49753] New: server_ioctl_file: Syscall param writev(vector[...]) points to uninitialised byte(s)
by WineHQ Bugzilla April 23, 2021

April 23, 2021

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 45611] New: 64bit prefix: copy file to system32 incorrectly copied to syswow64
by wine-bugs＠winehq.org April 23, 2021

April 23, 2021

https://bugs.winehq.org/show_bug.cgi?id=45611 Bug ID: 45611 Summary: 64bit prefix: copy file to system32 incorrectly copied to syswow64 Product: Wine Version: 3.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tim110011(a)163.com Distribution: --- How to reproduce: wine cmd Z:\home\me\0_wine> C: echo.>00aa.txt copy 00aa.txt c:\windows\system32 dir c:\windows\system32\00aa.txt result: Volume in drive c has no label. Volume Serial Number is 0000-0000 Directory of c:\windows\system32 8/11/2018 4:57 PM 2 00aa.txt 1 file 2 bytes 0 directories 351,430,549,504 bytes free find . -depth -name 00aa.txt result: ./syswow64/00aa.txt wine xcopy is also affected. I think this is the reason why .NET Framework 64bit don't install. System: wine 3.0.2 fedora 28 kernel 4.17.12 -- 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 April 23, 2021

April 23, 2021

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