March 2023 - Wine-Bugs - list.winehq.org

[Bug 53051] New: Kvaser software crashes on unimplemented function ntoskrnl.exe.ExNotifyCallback
by WineHQ Bugzilla March 27, 2023

March 27, 2023

https://bugs.winehq.org/show_bug.cgi?id=53051 Bug ID: 53051 Summary: Kvaser software crashes on unimplemented function ntoskrnl.exe.ExNotifyCallback Product: Wine Version: 7.9 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 72447 --> https://bugs.winehq.org/attachment.cgi?id=72447 Console output Steps to reproduce: 1. Install Kvaser Drivers for Windows 2. Run `wine 'C:\Program Files\Kvaser\Drivers\kcanconf.exe'` A crash dialog appears, but after closing it the Kvaser Device Guide does open. $ sha256sum kvaser_drivers_setup.exe 7519aa9b919ab88a830b2818e03d1311fbc2a0ed569722b0e7170fa5ef11839d -- 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 52972] New: wineusb.sys: add_usb_device erroneously releases critical section on failure path
by WineHQ Bugzilla March 27, 2023

March 27, 2023

https://bugs.winehq.org/show_bug.cgi?id=52972 Bug ID: 52972 Summary: wineusb.sys: add_usb_device erroneously releases critical section on failure path Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: usb Assignee: wine-bugs(a)winehq.org Reporter: jinoh.kang.kr(a)gmail.com CC: z.figura12(a)gmail.com Distribution: --- In wineusb.sys, add_usb_device() erroneously calls "LeaveCriticalSection(&wineusb_cb);" without first having entered the critical section. -- 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 48600] New: Bloomberg Terminal - crashes post installation, cannot run
by WineHQ Bugzilla March 27, 2023

March 27, 2023

https://bugs.winehq.org/show_bug.cgi?id=48600 Bug ID: 48600 Summary: Bloomberg Terminal - crashes post installation, cannot run Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: fusion Assignee: wine-bugs(a)winehq.org Reporter: knez(a)mailbox.org Distribution: --- Created attachment 66437 --> https://bugs.winehq.org/attachment.cgi?id=66437 Bloomberg terminal - crashes post installation Bloomberg Terminal - Client Software for Windows. Download location: https://www.bloomberg.com/professional/support/software-updates/ (https://bdn-ak-ssl.bloomberg.com/software/trv/sotrtLite01072020.exe) Bloomberg Terminal – New Installation (Terminal Software Only). OS: Ubuntu 16.04. Bloomberg terminal is a Windows-only financial professional software. The installation was run under Wine and no problems are reported. On execution of the installed file "wintrv.exe" the attached error appears. Further use of the software fails. -- 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 40444] New: Find doesn't jump to a found item in WinSCP
by wine-bugs＠winehq.org March 27, 2023

March 27, 2023

https://bugs.winehq.org/show_bug.cgi?id=40444 Bug ID: 40444 Summary: Find doesn't jump to a found item in WinSCP Product: Wine Version: 1.9.7 Hardware: x86 URL: http://winscp.net/download/winscp577.zip OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: t.artem(a)mailcity.com Distribution: Red Hat This bug is very easy to reproduce. Run WinSCP and open a session to any host. Open any long enough file (text/html/whatever), hit Find (Ctrl + F) and try to find something at least on the second page of the open document. The cursor will jump, however the screen will remain on the first page. In order to really jump to this position, you have to close the Find dialog (e.g. hit "Escape") and press "Up" and "Down" which is terribly inconvenient. -- 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 26

[Bug 53832] New: wbemprox: where-clause seems to be case-sensitive
by WineHQ Bugzilla March 27, 2023

March 27, 2023

https://bugs.winehq.org/show_bug.cgi?id=53832 Bug ID: 53832 Summary: wbemprox: where-clause seems to be case-sensitive Product: Wine Version: 7.19 Hardware: x86-64 URL: https://github.com/PowerShell/PowerShell/releases/down load/v7.0.3/PowerShell-7.0.3-win-x64.msi OS: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com Distribution: Debian Created attachment 73364 --> https://bugs.winehq.org/attachment.cgi?id=73364 script to reproduce the problem prerequisite: winetricks dotnet48 The attached script shows the problem: on windows one can either use 'c:' or 'C:' in the following query: $searcher = [wmisearcher]'Select freespace From win32_logicaldisk where deviceid="c:"' $searcher.scope.path = "\\.\root\cimv2" $searcher.get() On wine only the upper-case 'C:' yields any results. Steps to reproduce: download attached script and do 'wine pwsh -f aaa.ps1' Results on wine: Lower case c: gives: Upper case c: gives: __GENUS : 2 __CLASS : Win32_LogicalDisk __RELPATH : __PROPERTY_COUNT : 1 __DERIVATION : {} __SERVER : __NAMESPACE : __PATH : FreeSpace : 5817585664 PSComputerName : Results on windows: Z:\> .\aaa.ps1 Lower case c: gives: __GENUS : 2 __CLASS : Win32_LogicalDisk __SUPERCLASS : __DYNASTY : __RELPATH : __PROPERTY_COUNT : 1 __DERIVATION : {} __SERVER : __NAMESPACE : __PATH : FreeSpace : 23573446656 PSComputerName : Upper case c: gives: __GENUS : 2 __CLASS : Win32_LogicalDisk __SUPERCLASS : __DYNASTY : __RELPATH : __PROPERTY_COUNT : 1 __DERIVATION : {} __SERVER : __NAMESPACE : __PATH : FreeSpace : 23573446656 PSComputerName : -- 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 53821] New: winbase.h: ReOpenFile declaration missing (and not available in any other header)
by WineHQ Bugzilla March 27, 2023

March 27, 2023

https://bugs.winehq.org/show_bug.cgi?id=53821 Bug ID: 53821 Summary: winbase.h: ReOpenFile declaration missing (and not available in any other header) Product: Wine Version: 7.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: contact(a)ivanchev.net Distribution: --- A declaration for ReOpenFile should be imported with winbase.h (https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-reop…) but is currently missing. In fact, no header in Wine declares that function. -- 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 53706] New: NtDeviceIoControlFile() is quite slow when called with and invalid handle
by WineHQ Bugzilla March 27, 2023

March 27, 2023

https://bugs.winehq.org/show_bug.cgi?id=53706 Bug ID: 53706 Summary: NtDeviceIoControlFile() is quite slow when called with and invalid handle Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: metalcaedes(a)gmail.com Distribution: --- Created attachment 73130 --> https://bugs.winehq.org/attachment.cgi?id=73130 Call DeviceIoControl() with an invalid handle a lot and measure how long it takes I'm running some nonpublic proprietary application that I don't have the source code for in Wine (I attached a simple testprogram though). I noticed severe performance problems (compared with native Windows) and profiling it in perf (is there a better way?) showed a lot of useless memory addresses and also NtDeviceIoControlFile(). I figured out that the application calls DeviceIoControl() *a lot*, and after hooking that function and replacing it with a stub that basically just returns FALSE the application's performance was a lot better (good enough for my purposes). Being the curious type, I added some logging to my stub and realized that the handle that gets passed is 0xFFFFFFFF (INVALID_HANDLE_VALUE) - even on Windows! Specifically, I saw: hDevice: 0xFFFFFFFF code: 0x80010021 inBufSize: 4 outBufSize: 4 overlapped: 0x0 Reimplementing DeviceIoControl() (based on Wine Source) in my (former) stub and adding some time measurements showed that in this specific case (calling it with an invalid handle) the called NtDeviceIoControlFile() often takes around 4 microseconds on Wine (sometimes even over 20!) while it only takes around 0.5 microseconds on Windows 10 (even though that PC is a bit slower). So it takes 8-40 times as long in Wine. Looking into Wine's NtDeviceIoControlFile() implementation, this is probably the case because it calls into wineserver, via `server_ioctl_file()`. So I *think* that this could be relatively easily fixed by checking if the handle is INVALID_HANDLE_VALUE first thing in NtDeviceIoControlFile(), and if that's the case call `SetLastError( ERROR_INVALID_HANDLE );` and `return FALSE;` (Windows returns FALSE and sets that error code). I'm not 100% sure about this though, because I don't know if there are any cases of calling `NtDeviceIoControlFile()` where INVALID_HANDLE_VALUE is OK - if there are, the early-out-check would probably have to take the `code` argument into account (as far as I can tell it specifies the operation that NtDeviceIoControlFile() executes). I attached a simple test program that just calls DeviceIoControl() a lot (with the parameters I've seen in the real program I have issues with) and measures how long that takes. On my Windows machine (i7-4771, Win10) one call takes about 0.48-0.5 microseconds. On my Linux machine (Ryzen 5950X, Kernel 5.15, wine 7.17) one call takes about 4 microseconds on average, though many calls took longer. -- 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 53614] New: KeyPassXC does not open
by WineHQ Bugzilla March 27, 2023

March 27, 2023

https://bugs.winehq.org/show_bug.cgi?id=53614 Bug ID: 53614 Summary: KeyPassXC does not open Product: Wine Version: 7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: dstwine(a)mailinator.com Distribution: --- Created attachment 73012 --> https://bugs.winehq.org/attachment.cgi?id=73012 Log from console As in the title. Impossible to run KeyPassXC on Ubuntu 20.04 and Winehq 7.16 (but also 7.0 stable). A console is returned with error 5 because windbg cannot attach to obtain a backtrace. I attached the log in the console that concern the process related to KeyPassXC. Best 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.

1 7

[Bug 53455] New: shell32:recyclebin - test_query_recyclebin() gets unexpected recyclebin size in Wine
by WineHQ Bugzilla March 27, 2023

March 27, 2023

https://bugs.winehq.org/show_bug.cgi?id=53455 Bug ID: 53455 Summary: shell32:recyclebin - test_query_recyclebin() gets unexpected recyclebin size in Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- shell32:recyclebin - test_query_recyclebin() gets unexpected recyclebin size: recyclebin.c:79: Test failed: Expected recycle bin to have 0x22 bytes recyclebin.c:80: Test failed: Expected recycle bin to have 0x1 items https://test.winehq.org/data/patterns.html#shell32:recyclebin The expected size in bytes can also be 0x20 or 0x21 which can cause false positives. -- 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 53003] New: XM6 TypeG: some MIDI note-on messages aren't sent to MIDI devices (MIDI running status isn't supported in the MIDI mapper)
by WineHQ Bugzilla March 27, 2023

March 27, 2023

https://bugs.winehq.org/show_bug.cgi?id=53003 Bug ID: 53003 Summary: XM6 TypeG: some MIDI note-on messages aren't sent to MIDI devices (MIDI running status isn't supported in the MIDI mapper) Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winmm&mci Assignee: wine-bugs(a)winehq.org Reporter: sagawa.aki+winebugs(a)gmail.com Distribution: Ubuntu Created attachment 72371 --> https://bugs.winehq.org/attachment.cgi?id=72371 minimal reproducible example XM6 TypeG[1] is a SHARP X68000 Emulator. When I use STed2[2] inside XM6 TypeG, some MIDI note-on messages aren't sent to MIDI devices (e.g. Timidity++). @honda_ken, an original reporter on Twitter, tweeted XM6 TypeG sounds strange on Wine. He also informed me that Wine outputs the following message on his console: 0338:fixme:midi:modData ooch 3c 0338:fixme:midi:modData ooch 403e 0338:fixme:midi:modData ooch 3e 0338:fixme:midi:modData ooch 4040 0338:fixme:midi:modData ooch 40 0338:fixme:midi:modData ooch 4041 0338:fixme:midi:modData ooch 41 0338:fixme:midi:modData ooch 4043 0338:fixme:midi:modData ooch 43 I setup XM6 TypeG environment on my PC and I can reproduce the issue. Preparing the environment is a bit difficult, I wrote a minimal reproducible example (shortmsg.c). Steps to reproduce: 1. Compile the source code. % i686-w64-mingw32-gcc -o shortmsg.exe shortmsg.c -lwinmm 2. Setup your favorite MIDI device, e.g. Timidity++. % timidity -iA & 3. Run the executable (argument -1 means we use the MIDI mapper). % wine shortmsg.exe -1 Expected result: We can hear the piano voice, C, D, E and F. Actual result: We can hear the piano voice, only C. [1] http://retropc.net/pi/xm6/index.html [2] http://retropc.net/x68000/software/sound/rc/sted2/ -- 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