[PATCH v3 0/1] MR7158: wine.inf.in: Add UBR key

[Etaash Mathamsetty (＠etaash.mathamsetty)]

Required by Logitech G Hub

--
  v3: wine.inf.in: Add UBR key.

https://gitlab.winehq.org/wine/wine/-/merge_requests/7158

[PATCH v3 1/1] wine.inf.in: Add UBR key.

[Etaash Mathamsetty]

From: Etaash Mathamsetty

---
 loader/wine.inf.in | 1 +
 1 file changed, 1 insertion(+)

diff --git a/loader/wine.inf.in b/loader/wine.inf.in
index e3426b7ec95..165e20b30c6 100644
--- a/loader/wine.inf.in
+++ b/loader/wine.inf.in
@@ -2529,6 +2529,7 @@ HKLM,%CurrentVersionNT%,"CurrentMajorVersionNumber",0x10003,10
 HKLM,%CurrentVersionNT%,"CurrentMinorVersionNumber",0x10003,0
 HKLM,%CurrentVersionNT%,"CurrentBuild",2,"19043"
 HKLM,%CurrentVersionNT%,"CurrentBuildNumber",2,"19043"
+HKLM,%CurrentVersionNT%,"UBR",0x10001,1165
 HKLM,%CurrentVersionNT%,"CurrentType",2,"Multiprocessor Free"
 HKLM,%CurrentVersionNT%,"DigitalProductId",1,00,00,00,00,00,00,00,00,00,00,00,\
 00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

[PATCH v3 1/1] wine.inf.in: Add UBR key.

[Marvin]

Hi,

It looks like your patch introduced the new failures shown below.
Please investigate and fix them before resubmitting your patch.
If they are not new, fixing them anyway would help a lot. Otherwise
please ask for the known failures list to be updated.

The tests also ran into some preexisting test failures. If you know how
to fix them that would be helpful. See the TestBot job for the details:

The full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=150941

Your paranoid android.

=== debian11b (64 bit WoW report) ===

user32:
input.c:4305: Test succeeded inside todo block: button_down_hwnd_todo 1: got MSG_TEST_WIN hwnd 0000000000C800F4, msg WM_LBUTTONDOWN, wparam 0x1, lparam 0x320032

Report validation errors:
d3d11:d3d11 crashed (c0000005)

[Alexandre Julliard (＠julliard)]

On Mon Jan 20 22:36:24 2025 +0000, Etaash Mathamsetty wrote:
> changed this line in [version 3 of the diff](/wine/wine/-/merge_requests/7158/diffs?diff_id=153116&start_sha=46240c3b0c3cf4677a2627d6fcd585b9668f0074#dcea097491aea5c674c4bd70c05f7ab7b0278e18_2532_2532)

It seems to me that it makes more sense to keep it in sync with the rest of the version info, which means it shouldn't get clobbered on updates (and ideally the version setting code would set this field as well).