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

[Bug 49856] ShareX can't open settings window

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49856 CamnJB(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |CamnJB(a)gmail.com --- Comment #9 from CamnJB(a)gmail.com --- Been messing with sharex after getting the same error. Installing dotnet48 did initially stop me from staring sharex after it would at least start without it. After I tried installing dotnet48 sharex wouldn't start and would say I need the .net framework 4.8 which was already installed however I did a repair and now I can access sharex settings fine. Havent managed to get screen capture to work properly though -- 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.

Nov. 25, 2021

[Bug 51873] Joy.cpl crashes on the FFB tab when the FFB device is selected in the drop down list

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51873 Ivo Ivanov <logos128(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |c2235c44c5f8fedaad775c69b9a | |475725874bbc7 -- 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.

Nov. 25, 2021

[Bug 52101] In UDEV lnxev mode the winedevice.exe process of winebus.sys crashes on a keypress from the keyboard.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52101 --- Comment #1 from Ivo Ivanov <logos128(a)gmail.com> --- Created attachment 71123 --> https://bugs.winehq.org/attachment.cgi?id=71123 0001-winebus.sys-Prevent-processing-empty-Input-Reports.patch Attached a patch with a possible fix. Based on the current master 5e42498e634abda051aa59a3faeb2cf10469b1a6 -- 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.

Nov. 25, 2021

[Bug 52102] outSPOKEN 3.0 demo crashes after error "Accessing unknown VxD 3167"

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52102 Alex Henrie <alexhenrie24(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|x86-64 |x86 Keywords| |download URL| |https://allinaccess.com/hap | |p/files/osw30demo.exe -- 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.

Nov. 25, 2021

[Bug 52102] New: outSPOKEN 3.0 demo crashes after error "Accessing unknown VxD 3167"

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52102 Bug ID: 52102 Summary: outSPOKEN 3.0 demo crashes after error "Accessing unknown VxD 3167" Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 71122 --> https://bugs.winehq.org/attachment.cgi?id=71122 Console output Steps to reproduce: 1. Delete ~/.wine or move it to another location. 2. Create a new Wine bottle with the command `WINEARCH=win32 wine winecfg` and set the Windows version to 95 or 98. 3. Run `wine osw30demo.exe` to install outSPOKEN. The setup wizard will not complete until you select a speech synthesizer from the list. When the wizard asks which COM port the speech synthesizer is connected to, select "Internal". 4. Run `wine 'C:\Osw\OSW.EXE'` to start outSPOKEN. outSPOKEN crashes immediately. Console output is attached. $ sha256sum osw30demo.exe 89ae45e689e35b0618b1b4fa27fb0c3e5b854461391100e2dc1742395ffa77b6 -- 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.

Nov. 25, 2021

[Bug 52101] New: In UDEV lnxev mode the winedevice.exe process of winebus.sys crashes on a keypress from the keyboard.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52101 Bug ID: 52101 Summary: In UDEV lnxev mode the winedevice.exe process of winebus.sys crashes on a keypress from the keyboard. Product: Wine Version: 6.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: logos128(a)gmail.com CC: rbernon(a)codeweavers.com Distribution: ArchLinux Created attachment 71121 --> https://bugs.winehq.org/attachment.cgi?id=71121 winebus_crash_v6.22.log.tar.gz It happens only on an user account with administrator rights (superuser, etc.). As it crashes on a keypress, this makes pretty difficult attaching a debugger to the crashing process :) Found out that lnxev backend doesn't add normal keys to the staged report descriptor, which makes any usb keyboard appear with an empty Input report. The actual crash happens in winebus.sys/main.c process_hid_report(), when it tries to resolve the ext->collection_desc.ReportIDs[0].ReportID. -- 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.

Nov. 25, 2021

[Bug 52091] Loading dll from ntfs disk (sometimes) fails.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52091 Ptr <peter-24(a)o2.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter-24(a)o2.pl --- Comment #4 from Ptr <peter-24(a)o2.pl> --- No problems when game is installed on ext4 disk. -- 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.

Nov. 25, 2021

[Bug 51210] winediag:nodrv_CreateWindow Unknown error (998)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51210 --- Comment #12 from Vasily Galkin <galkin-vv(a)ya.ru> --- Also this may be related to the fix that nvidia done in https://bugs.winehq.org/show_bug.cgi?id=49407 The origin of the SIGSEGV is inside NVidia libs. Calling to nullptr-function (according to a stacktrace I presented above) instead of returning an error MAY be a sign of a bug inside nvidia driver. -- 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.

Nov. 25, 2021

[Bug 51210] winediag:nodrv_CreateWindow Unknown error (998)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51210 Vasily Galkin <galkin-vv(a)ya.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |galkin-vv(a)ya.ru --- Comment #11 from Vasily Galkin <galkin-vv(a)ya.ru> --- Created attachment 71120 --> https://bugs.winehq.org/attachment.cgi?id=71120 Minimal crash repoducer TLDR: if wrong vulkan ICD is loaded pvkGetRandROutputDisplayEXT may crash. I ran into the same problem in a multiseat system with one seat on NVidia gpu and the other seat on AMD gpu (both sessions X11). Trying to run wine or even winedbg on the X11 DISPLAY on the amd gots this error. thread log with a part near the crash: > 172488.042:0078:007c:trace:vulkan:X11DRV_vkCreateInstance create_info 0x6ace50, allocator (nil), instance 0x6ace40 > 172488.042:0078:007c:trace:heap:RtlAllocateHeap (0000000000020000,7000006a,00000030): returning 0000000000070BF0 > 172488.097:0078:007c:trace:heap:RtlFreeHeap (0000000000020000,70000062,0000000000070BF0): returning TRUE > 172488.097:0078:007c:trace:vulkan:X11DRV_vkGetInstanceProcAddr 0x7e61ed10, "vkEnumeratePhysicalDevices" > 172488.097:0078:007c:trace:vulkan:X11DRV_vkGetInstanceProcAddr 0x7e61ed10, "vkGetPhysicalDeviceProperties2KHR" > 172488.097:0078:007c:trace:vulkan:X11DRV_vkGetInstanceProcAddr 0x7e61ed10, "vkGetRandROutputDisplayEXT" > 172488.099:0078:007c:trace:heap:RtlAllocateHeap (0000000000020000,7000006a,00000018): returning 0000000000070C40 > 172488.115:0078:007c:trace:seh:dispatch_exception code=c0000005 flags=0 addr=0000000000000000 ip=0000000000000000 tid=007c > 172488.115:0078:007c:trace:unwind:dispatch_exception info[0]=0000000000000008 > 172488.115:0078:007c:trace:unwind:dispatch_exception info[1]=0000000000000000 > 172488.115:0078:007c:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised > 172488.115:0078:007c:trace:seh:dispatch_exception rax=00007f24aff77340 rbx=00000000006ace48 rcx=00000000006acd60 rdx=00000000006acd2c > 172488.115:0078:007c:trace:seh:dispatch_exception rsi=0000000000000055 rdi=000000007e5ebb40 rbp=000000007e8b4420 rsp=00000000006acd18 > 172488.115:0078:007c:trace:seh:dispatch_exception r8=00000000006ace48 r9=0000000000000004 r10=00007ffdd5f46080 r11=0000000000000246 > 172488.115:0078:007c:trace:seh:dispatch_exception r12=0000000000000055 r13=000000007e5ebb40 r14=00000000006ace48 r15=00007f24bb1a3870 > 172488.115:0078:007c:trace:unwind:dwarf_virtual_unwind function 7f24ae851ca0 base 0x7f24ae851c70 cie 0x7f24af0744f8 len 14 id 0 version 3 aug 'zR' code_align 1 data_align -8 retaddr %rip I investigated it further and found the reason: for DISPLAY containing all AMD-related the NVidia vulkan ICD is loaded, and pvkGetRandROutputDisplayEXT calls into libnvidia-glcore.so.470.86 that crashes for that AMD display. Attached file is a minimal C source that reproduces the problem. It runs fine with nvidia DISPLAY=:0 and segfaults with amd DISPLAY=:1 > % DISPLAY=:0 ./wine-vk-randr-crash > 0x7fadf49c4870 0x7fadf49e3750 0x7fadf49e4210 > device_count 3 > pvkGetRandROutputDisplayEXT 0x55ce42baf750 > pvkGetRandROutputDisplayEXT 0x55ce42baad20 > pvkGetRandROutputDisplayEXT 0x55ce42baf5b0 > % DISPLAY=:1 ./wine-vk-randr-crash > 0x7fb9ee250870 0x7fb9ee26f750 0x7fb9ee270210 > device_count 3 > pvkGetRandROutputDisplayEXT 0x564206a0bd00 > zsh: segmentation fault Dircet specifying VK_ICD_FILENAMES helps > % VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json DISPLAY=:1 > ./wine-vk-randr-crash > 0x7fc07c50c870 0x7fc07c52b750 0x7fc07c52c210 > device_count 1 > pvkGetRandROutputDisplayEXT 0x556edbb1c320 > % So this minimal representer has behaviour identical to wine. running DISPLAY=:1 ./wine-vk-randr-crash under gdb gives the stacktrace into libnvidia-glcore.so.470.86 ending with NULL instruction pointer: > pvkGetRandROutputDisplayEXT 0x557c6aba4cf0 > > Thread 1 "wine-vk-randr-c" received signal SIGSEGV, Segmentation fault. > 0x0000000000000000 in ?? () > (gdb) bt > #0 0x0000000000000000 in ?? () > #1 0x00007f86799ddca0 in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.470.86 > #2 0x00007f86799d8afd in ?? () from /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.470.86 > #3 0x0000557c68a124d8 in main () at wine-vk-randr-crash.c:83 If anyone know how vkCreateInstance can be called in a way that returns ICD that is compatible with specific X11 disaply, this maybe can be used to fix the issue. -- 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.

Nov. 25, 2021

[Bug 51873] Joy.cpl crashes on the FFB tab when the FFB device is selected in the drop down list

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51873 Ivo Ivanov <logos128(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #28 from Ivo Ivanov <logos128(a)gmail.com> --- (In reply to Rémi Bernon from comment #27) > I believe this specific issue has been fixed since > c2235c44c5f8fedaad775c69b9a475725874bbc7, could you confirm? > > Regarding effect state report and the way IOCTL_HID_GET_INPUT_REPORT is > supposed to work I suggest moving the discussion to > https://bugs.winehq.org/show_bug.cgi?id=52062. I can confirm it is fixed. I was going to change the bug status, just wanted to write my report from the weekend :) I am happy to say that on the UDEV hidraw backend everything works as expected. With the games I tested the FFB is pretty much equal to Windows. I compared some captured usb traffic and the sent commands are similar in frequency and sequence. There are some small differences mostly around the RESET command, but I'll have to confirm that further with some conformance testing. The direction used by WheelCheck and the most games is 0x2d on both Windows and Wine. I tested also the other backends. The SDL backend works very well now. The FFB is functional, although seems somewhat smoother with less details in comparison to Windows / Wine (hidraw). The characteristic is the same, just with less 'punch'. My first thought was that it could be higher frequency of the FFB rate, which in theory could provide a smoother force curve. As these direct drive devices are capable of playing very small changes of the forces on almost ms level. The frequencies were similar, though, ~560Hz on Wine (hidraw / SDL) and ~400Hz on Windows (Automobilista 2). So I compared some usb traffic and the first noticeable thing is a difference in the direction value, 0x2d on Windows / Wine (hidraw) and 0x5a on SDL. IMO this seems like a candidate for such slight difference in the FFB behavior. I plan to compare it with proton's joystick_sdl behavior. The UDEV lnxev backend doesn't produce FFB, though. It manages to turn off the bump stops of the wheel, which can be resolved normally with a power-cycle of the device. There is a Reset FFB command in the TrueDrive software (Simucube 2's controlling app), which also resolves the normal behavior. That leads me to think it just turns off the actuators with an FFB command. Probably this will need another bug report. I have also a strange crash of the winebus.sys process when using the UDEV bus. It occurs only when using an administrator account (with superuser rights). I will post a bug report with a patch, since finally had some time and found the issue. -- 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.

Nov. 25, 2021