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

[Bug 52001] HenPri trial: crashes with "Unhandled page fault on read access to 00000000" [possibly video-related]

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52001 Sagawa <sagawa.aki+winebugs(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sagawa.aki+winebugs(a)gmail.c | |om -- 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. 17, 2021

[Bug 52053] start.exe doesn't open .lnk file: application/start menu items don't open

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52053 --- Comment #1 from DonJaime(a)freenet.de --- Created attachment 71065 --> https://bugs.winehq.org/attachment.cgi?id=71065 Console output wine 6.16 -- 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. 17, 2021

[Bug 52053] New: start.exe doesn't open .lnk file: application/start menu items don't open

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52053 Bug ID: 52053 Summary: start.exe doesn't open .lnk file: application/start menu items don't open Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: DonJaime(a)freenet.de Distribution: --- Created attachment 71064 --> https://bugs.winehq.org/attachment.cgi?id=71064 Console output wine 6.21 Since version 18 start menu items fail to open with a dialog saying that no windows program is configured to open this kind of file followed by several file not found dialogs. Updating the prefix and opening files is also much slower. This only happens one computer, I have another installation where everything works. After downgrade to version 16 everything works again. (I don't have a copy of version 17.) Attached console output of WINEPREFIX="<...>" wine start.exe "c:\users\james\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Microsoft Office Word Viewer 2003.lnk" under version 6.21 -- 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. 17, 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 --- Comment #24 from Rémi Bernon <rbernon(a)codeweavers.com> --- (In reply to Ivo Ivanov from comment #23) > (In reply to Rémi Bernon from comment #22) > > Thanks, is the MS PID driver actually using these reports with your device? > > I haven't yet found a way to have them used with the virtual HID driver we > > have for conformance testing. It would be really nice if we could test them > > too. > > Yes, it needs the Create New Effect Report and PID Block Load Report to > function properly, as it is Device Managed. I think most of the modern PID > devices manage their block index on the device side. Those reports are > visible in the usb traffic captures (Simucube_2_logs.tar.gz) attached to > this bug report. > > IMO the virtual HID driver need to implement the PID Pool Feature Report > (look the attached SC2_descr.txt - Usage (7Fh)), and set the Device Managed > Pool usage there. With other words it needs to advertise itself as Device > Managed. > The Linux driver does just this to check if the device is Device Managed. > Ah I see, I'll try that. Thanks! > Here (in Wine) we check for the existence of the Create New Effect Report, > and assume that the device manages its blocks internally, since this and the > other reports are used only by such devices as per specification. > > > I just used the same kind of value range as some sample descriptors from the > > PID spec, or as the SideWinder HID descriptors that can be found on > > internet. This can definitely be modified to better match backend ranges and > > avoid unnecessary rounding (although SDL and evdev may have slightly > > different ranges). > > The ranges in the frontend dinput/joystick_hid.c are OK, IMO. > They are similar to my device's report descriptor. > > I meant the "virtual" HID report descriptors in the UDEV lnxev and the SDL > backends. Their logical ranges are too small, and are being passed without > any rescaling to the ff_effect / SDL_HapticEffect structures. Unless I am > overlooking something :) Oh yeah you're right indeed, there is some scaling for some of the values like direction or magnitude, but I completely missed some others... Duh! -- 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. 17, 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 --- Comment #23 from Ivo Ivanov <logos128(a)gmail.com> --- (In reply to Rémi Bernon from comment #22) > Thanks, is the MS PID driver actually using these reports with your device? > I haven't yet found a way to have them used with the virtual HID driver we > have for conformance testing. It would be really nice if we could test them > too. Yes, it needs the Create New Effect Report and PID Block Load Report to function properly, as it is Device Managed. I think most of the modern PID devices manage their block index on the device side. Those reports are visible in the usb traffic captures (Simucube_2_logs.tar.gz) attached to this bug report. IMO the virtual HID driver need to implement the PID Pool Feature Report (look the attached SC2_descr.txt - Usage (7Fh)), and set the Device Managed Pool usage there. With other words it needs to advertise itself as Device Managed. The Linux driver does just this to check if the device is Device Managed. Here (in Wine) we check for the existence of the Create New Effect Report, and assume that the device manages its blocks internally, since this and the other reports are used only by such devices as per specification. > I just used the same kind of value range as some sample descriptors from the > PID spec, or as the SideWinder HID descriptors that can be found on > internet. This can definitely be modified to better match backend ranges and > avoid unnecessary rounding (although SDL and evdev may have slightly > different ranges). The ranges in the frontend dinput/joystick_hid.c are OK, IMO. They are similar to my device's report descriptor. I meant the "virtual" HID report descriptors in the UDEV lnxev and the SDL backends. Their logical ranges are too small, and are being passed without any rescaling to the ff_effect / SDL_HapticEffect structures. Unless I am overlooking something :) -- 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. 17, 2021

[Bug 52052] New: Wine doesn't show any window while creating/updating 64-bit prefix

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52052 Bug ID: 52052 Summary: Wine doesn't show any window while creating/updating 64-bit prefix Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com CC: julliard(a)winehq.org Regression SHA1: a9b5bb326a1514e2c4185633ab34b22c9bbc9863 Distribution: --- wine: created the configuration directory '/home/andrey/.wine' 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0048:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0050:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 0050:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0050:err:winediag:nodrv_CreateWindow Unknown error (998). 0050:err:systray:initialize_systray Could not create tray window 0050:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002 0050:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002 0050:err:ole:apartment_get_local_server_stream Failed: 0x80004002 0048:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0048:err:winediag:nodrv_CreateWindow Unknown error (998). 0048:err:ole:apartment_createwindowifneeded CreateWindow failed with error 3 002c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 002c:err:winediag:nodrv_CreateWindow Unknown error (998). 0048:err:ole:apartment_createwindowifneeded CreateWindow failed with error 0 0048:err:ole:apartment_createwindowifneeded CreateWindow failed with error 14007 0048:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x800736b7 0048:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x800736b7 0048:err:ole:apartment_get_local_server_stream Failed: 0x800736b7 0048:err:ole:start_rpcss Failed to open RpcSs service 0040:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0040:err:winediag:nodrv_CreateWindow Unknown error (998). wine: Unhandled page fault on read access to 000000000000FF00 at address 00007FA96A418C58 (thread 0070), starting debugger... 0070:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 96 76" (2) Read the Wine Developers Guide on how to set up winedbg or another debugger 0058:err:service:process_send_command service protocol error - failed to read pipe r = 0 count = 0! 007c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 007c:err:winediag:nodrv_CreateWindow Unknown error (998). 007c:fixme:shell:create_link failed to connect to mount manager 007c:fixme:shell:create_link failed to connect to mount manager 007c:fixme:shell:create_link failed to connect to mount manager 007c:fixme:shell:create_link failed to connect to mount manager 007c:fixme:shell:create_link failed to connect to mount manager 007c:fixme:shell:create_link failed to connect to mount manager 007c:fixme:shell:create_link failed to connect to mount manager 0084:fixme:file:NtLockFile I/O completion on lock not implemented yet 0084:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0084:err:mscoree:LoadLibraryShim error reading registry key for installroot 0084:err:mscoree:LoadLibraryShim error reading registry key for installroot 0084:err:mscoree:LoadLibraryShim error reading registry key for installroot 0084:err:mscoree:LoadLibraryShim error reading registry key for installroot 008c:fixme:file:NtLockFile I/O completion on lock not implemented yet 008c:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 008c:err:mscoree:LoadLibraryShim error reading registry key for installroot 008c:err:mscoree:LoadLibraryShim error reading registry key for installroot 008c:err:mscoree:LoadLibraryShim error reading registry key for installroot 008c:err:mscoree:LoadLibraryShim error reading registry key for installroot 008c:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 5) 008c:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 5) 0084:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1) 0084:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1) 00d0:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 00d0:err:winediag:nodrv_CreateWindow Unknown error (998). wine: configuration in L"/home/andrey/.wine" has been updated. 0124:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. 0124:err:winediag:nodrv_CreateWindow Unknown error (998). -- 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. 17, 2021

[Bug 51821] EVE Online Client Crashes Due to differences in how Wine and Windows handle LdrGetDllPath with dwFlags 0x8 and relative path

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51821 g2g591(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |g2g591(a)gmail.com --- Comment #18 from g2g591(a)gmail.com --- still have this issue with wine 6.21 (with staging patchset) , and the attached patch still fixes 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.

Nov. 17, 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 --- Comment #22 from Rémi Bernon <rbernon(a)codeweavers.com> --- (In reply to Ivo Ivanov from comment #21) > Created attachment 71063 [details] > dinput-additions-and-fixes.patch > > Added two new patches to support the PID_USAGE_PARAMETER_BLOCK_OFFSET usage > in the Set Condition Report of dinput and UDEV lnxev + SDL backends. > Added also a patch for the UDEV lnxev and SDL backends, which makes their > behavior similar to the MS PID driver, in relation to the output reports > being sent only when the corresponding flag in SetParameters is set. > The patch also makes those backends compatible with the modified reports > patch. > Thanks, is the MS PID driver actually using these reports with your device? I haven't yet found a way to have them used with the virtual HID driver we have for conformance testing. It would be really nice if we could test them too. > While looking at the backends, noted that the Logical min/max values of > various usages as magnitude, offset, attack/fade level, pos/neg coefficient > and saturation, deadband, ramp start/end, gain, etc., are being set to one > byte max values. Thus the frontend scales them down to those ranges and > sends them to the backends which pass them directly to ff_effect / > SDL_HapticEffect. While those structures expect mostly 16bit signed/unsigned > values in the range of -32767/+32767 or 0/65535. IMO this could be one of > the reasons for non existent FFB in those backends. I'll look further when > the time permits. > I just used the same kind of value range as some sample descriptors from the PID spec, or as the SideWinder HID descriptors that can be found on internet. This can definitely be modified to better match backend ranges and avoid unnecessary rounding (although SDL and evdev may have slightly different ranges). > Rebased the remaining patches to the current master > b65ef71fc0a7044557e0ba530e3b95497644867c > Thanks, I have some of the patches split up locally that I'll send later, mainly about the properties which I instead moved to be handled directly in the base device class. I'll have a look and integrate your changes. -- 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. 17, 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 ---------------------------------------------------------------------------- Attachment #71017|0 |1 is obsolete| | Attachment #71044|0 |1 is obsolete| | --- Comment #21 from Ivo Ivanov <logos128(a)gmail.com> --- Created attachment 71063 --> https://bugs.winehq.org/attachment.cgi?id=71063 dinput-additions-and-fixes.patch Added two new patches to support the PID_USAGE_PARAMETER_BLOCK_OFFSET usage in the Set Condition Report of dinput and UDEV lnxev + SDL backends. Added also a patch for the UDEV lnxev and SDL backends, which makes their behavior similar to the MS PID driver, in relation to the output reports being sent only when the corresponding flag in SetParameters is set. The patch also makes those backends compatible with the modified reports patch. While looking at the backends, noted that the Logical min/max values of various usages as magnitude, offset, attack/fade level, pos/neg coefficient and saturation, deadband, ramp start/end, gain, etc., are being set to one byte max values. Thus the frontend scales them down to those ranges and sends them to the backends which pass them directly to ff_effect / SDL_HapticEffect. While those structures expect mostly 16bit signed/unsigned values in the range of -32767/+32767 or 0/65535. IMO this could be one of the reasons for non existent FFB in those backends. I'll look further when the time permits. Rebased the remaining patches to the current master b65ef71fc0a7044557e0ba530e3b95497644867c P.S. Saw that you already submitted the DIPROP_FFGAIN patch in winehq, so excluded it as well. From the other new reports probably the Block Free Report will need additional implementation in the backends, similar to the Device Gain Report. -- 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. 17, 2021

[Bug 5714] Microsoft Visual C++ 2005 Redistributable Package won't install

by WineHQ Bugzilla

Nov. 17, 2021