February 2024 - Wine-bugs - list.winehq.org

[Bug 56294] New: WineD3D make Hellforce very slow and unstable to play
by WineHQ Bugzilla 03 Feb '24

03 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=56294 Bug ID: 56294 Summary: WineD3D make Hellforce very slow and unstable to play Product: Wine Version: 9.1 Hardware: x86-64 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrdudepedroterra(a)gmail.com I am trying to play the russian game called HellForce with WineD3D, but smiliar with others games, the game is very unstable to play, when looking down the game runs normal but when look everywhere, it beign very slow, and if used in bas way, every model whill be bugged, what i do? -- 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 0

[Bug 56289] New: msi: "Browse" button in installer always enabled
by WineHQ Bugzilla 03 Feb '24

03 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=56289 Bug ID: 56289 Summary: msi: "Browse" button in installer always enabled Product: Wine Version: 9.1 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- You can test with Tortoise Git installer. When selecting a subfeature for example, the "Browse" button should be greyed out. -- 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 2

[Bug 56281] New: String number converted to ascii value instead of parsed value
by WineHQ Bugzilla 02 Feb '24

02 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=56281 Bug ID: 56281 Summary: String number converted to ascii value instead of parsed value Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: francisdb(a)gmail.com Distribution: --- > cat test.vbs Dim x x = "0" If IsNumeric(x) Then WScript.Echo "Numeric" Else WScript.Echo "Not Numeric" End If If x > 30 Then WScript.Echo "> 30" Else WScript.Echo "Not > 30" End If > wine cscript test.vbs 0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0088:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 Numeric > 30 Windows > cscript test.vbs Microsoft (R) Windows Script Host Version 5.812 Copyright (C) Microsoft Corporation. All rights reserved. Numeric Not > 30 -- 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 3

[Bug 46666] New: Al Unser, Jr Arcade Racing has weird colors
by wine-bugs＠winehq.org 02 Feb '24

02 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=46666 Bug ID: 46666 Summary: Al Unser, Jr Arcade Racing has weird colors Product: Wine Version: 4.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: haakobja(a)gmail.com Distribution: --- Created attachment 63612 --> https://bugs.winehq.org/attachment.cgi?id=63612 Screenshot showing wrong colors Hi, I have recently tried Al Unser, Jr. Arcade Racing with Wine, the game itself is from 1995 so its is quite old. I was just curious. I have managed to get the game working, but the colors is not right. The game requires an 8 bit display, otherwise it refuses to start. I followed the recommendations and used the following commands: $ Xephyr :1 -screen 800x600x8 -cc 3 & $ DISPLAY=:1 wine alunser.exe The game starts, but the colors are wrong. As displayed in my attached image. A demo, which displays the same colors, are available at: https://archive.org/details/Alunser. There's also an image displaying the colors as they should be. -- 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 12

[Bug 56232] New: Sega Bug fails to initialize
by WineHQ Bugzilla 01 Feb '24

01 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=56232 Bug ID: 56232 Summary: Sega Bug fails to initialize Product: Wine Version: 3.17 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 75943 --> https://bugs.winehq.org/attachment.cgi?id=75943 WINEDEBUG=+d3d,+ddraw Steps to reproduce: 1. Insert the Sega Bug CD 2. Run `Xephyr :1 -ac -screen 800x600x8 &` 3. Run `DISPLAY=:1 openbox &` 4. Run `DISPLAY=:1 wine 'D:\win95\bug!.exe'` An error dialog titled "Error Initialising" appears that says "A hardware-only DirectDraw object creation was attempted but the driver did not support any hardware." After clicking OK, a second dialog appears that says "Could not initialise DirectDraw". I have a patch that I could apply to Wine < 3.17 to get the game to work, but this error is relatively new. `git bisect` says: 7b2ff904042ee95214b6c5b4a80e51d7f6b24c2b is the first bad commit commit 7b2ff904042ee95214b6c5b4a80e51d7f6b24c2b Author: Józef Kucia <jkucia(a)codeweavers.com> Date: Mon Sep 24 01:09:31 2018 +0200 wined3d: Pass feature levels to wined3d_device_create(). Signed-off-by: Józef Kucia <jkucia(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> Debug traces are attached. I believe the relevant line is: 0024:warn:ddraw:ddraw_surface_create Video memory surfaces not supported without 3D support. -- 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 2

[Bug 47490] New: GlobalLock different behavior
by wine-bugs＠winehq.org 01 Feb '24

01 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=47490 Bug ID: 47490 Summary: GlobalLock different behavior Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: ghotik2002(a)yahoo.com Distribution: --- Different behavior of GlobalLock in DxWnd GUI routine. This is an extract of source code: IStream *pStream = 0; CreateStreamOnHGlobal(0, TRUE, &pStream); LONG cbSize = 0; hr = pPicture->SaveAsFile(pStream, TRUE, &cbSize); if(FAILED(hr)) { OutTrace("GrayIcon: SveAsFile error hr=%#x\n", hr); return NULL; } HGLOBAL hBuf = 0; hr = GetHGlobalFromStream(pStream, &hBuf); if(FAILED(hr)) { OutTrace("GrayIcon: GetHGlobalFromStream error hr=%#x\n", hr); return NULL; } buf = (BYTE *)GlobalLock(hBuf); if(buf == NULL) { OutTrace("GrayIcon: GlobalLock error err=%d\n", GetLastError()); return NULL; } the stream holds an icon picture, everything is ok but the GlobalLock call: - in Windows it returns a valid memory address - in Wine/Linux it returns NULL errno 157 ERROR_DISCARDED - The segment is already discarded and cannot be locked. All this is in DxWnd program run on Wine/Linux environment. P.s. my first bug report here - hope everything is more or less ok ... ;) -- 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 7

[Bug 56277] New: Appindicator or statusnotifier support
by WineHQ Bugzilla 01 Feb '24

01 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=56277 Bug ID: 56277 Summary: Appindicator or statusnotifier support Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: marlonn.dev(a)proton.me Distribution: --- Created attachment 75996 --> https://bugs.winehq.org/attachment.cgi?id=75996 Image of deattached system tray I'm trying to run programs from both lutris and steam(via proton) but every time the programs has a tray icon, a new window pops up with that tray icon. For Lutris i'm using Wine-Ge-25 and for steam i'm using proton experimental bleeding edge. As I've understood it wine does not support statusnotifier and/or Appindicator. Wine seems to be using Xembed instead and since that doesnt scale well with modern desktop i propose and update to statusnotifier and/or appindicator support Solus 4.5 Budgie 10.8.2 -- 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 56279] New: Wine fails to build if CC is set to the absolute path for the compiler
by WineHQ Bugzilla 01 Feb '24

01 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=56279 Bug ID: 56279 Summary: Wine fails to build if CC is set to the absolute path for the compiler Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vibhavp(a)gmail.com Distribution: --- At least as of commit e607da943aa (win32u: Only queue a single IME update during ImeProcessKey.), the Wine build fails if any of the [<ARCH>_]CC environment variables are set to an absolute path to GCC/Clang, as opposed to just the executable name. This can be reproduced by configuring and building Wine with the follow environment variables: export CC='/usr/bin/gcc' export CROSSCC='/usr/bin/i686-w64-mingw32-gcc' export i386_CC='/usr/bin/i686-w64-mingw32-gcc' export x86_64_CC='55/usr/bin/x86_64-w64-mingw32-gcc' The failure is specifically due to winebuild being provided an invalid target specification argument (in this case, `/usr/bin/i686-w64-mingw32` instead of `i686-w64-mingw32` ): tools/winebuild/winebuild -w --staticlib -o dlls/winecrt0/i386-windows/libwinecrt0.a -b /usr/bin/i686-w64-mingw32 \ ... winebuild: Unrecognized target '/usr/bin/i686-w64-mingw32' make: *** [Makefile:167493: dlls/winecrt0/i386-windows/libwinecrt0.a] Error 1 -- 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 3

[Bug 56268] New: The XM1 Configuration Software doesn't detect the mouse
by WineHQ Bugzilla 01 Feb '24

01 Feb '24

https://bugs.winehq.org/show_bug.cgi?id=56268 Bug ID: 56268 Summary: The XM1 Configuration Software doesn't detect the mouse Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bq74stlxvkpb(a)opayq.com Distribution: --- Created attachment 75985 --> https://bugs.winehq.org/attachment.cgi?id=75985 XM1 RGB isn't detected by its configuration application When attempting to modify the firmware of an XM1 RGB mouse, the configuration tool fails to detect it. The tool can be freely downloaded at: https://www.endgamegear.com/en-us/downloads/xm1rgb The downloaded file should be XM1_RGB_Configuration_Software_(V1.01).zip The installation goes fine. No mouse is detected, however - see the attachment. Under native Win7, the installation fails, so I cannot use that as a workaround. I had to use native Win10 on my work-issued laptop to modify the firmware. Side note - the reason why I am doing this is that the mouse in question, by default, cycles through colours RAPIDLY. It's almost seizure-inducing. I've changed it to solid white. Additional bug I just found out - while the systray icon for it appears while it is running, right-clicking it opens its context menu... behind the taskbar. Furthermore, clicking elsewhere doesn't close its systray icon context menu. -- 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