- Wine-Bugs - list.winehq.org

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

Feb. 2, 2024

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 47490] New: GlobalLock different behavior
by wine-bugs＠winehq.org Feb. 1, 2024

Feb. 1, 2024

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 Feb. 1, 2024

Feb. 1, 2024

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 Feb. 1, 2024

Feb. 1, 2024

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 Feb. 1, 2024

Feb. 1, 2024

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

[Bug 55167] New: Spotify crashes when trying to install
by WineHQ Bugzilla Jan. 31, 2024

Jan. 31, 2024

https://bugs.winehq.org/show_bug.cgi?id=55167 Bug ID: 55167 Summary: Spotify crashes when trying to install Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: just4steam778(a)gmail.com Distribution: --- Created attachment 74747 --> https://bugs.winehq.org/attachment.cgi?id=74747 Launch log I'm trying to install the Windows version of Spotify and it immediately crashes when I launch the executable. Wine build: wine-8.11-125-g3d28f9d362e OS: Arch Linux -- 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 5

[Bug 56272] New: Missing axes and buttons from Turtle beach flightstick yoke
by WineHQ Bugzilla Jan. 31, 2024

Jan. 31, 2024

https://bugs.winehq.org/show_bug.cgi?id=56272 Bug ID: 56272 Summary: Missing axes and buttons from Turtle beach flightstick yoke Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: keri24601(a)yahoo.com Distribution: --- Created attachment 75993 --> https://bugs.winehq.org/attachment.cgi?id=75993 screenshot of control.exe and jstest jstest-gtk correctly identifies the yoke as having 10 axes and 34 buttons. Running in wine with control.exe, there's only 4 working axes + 2 of them that overlap, with 10 buttons and, one of the hats work. The wine version is 9.0 -- 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 55470] New: i686-w64-mingw32-gcc assumes wrong stack alignment
by WineHQ Bugzilla Jan. 31, 2024

Jan. 31, 2024

https://bugs.winehq.org/show_bug.cgi?id=55470 Bug ID: 55470 Summary: i686-w64-mingw32-gcc assumes wrong stack alignment Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: stefan(a)codeweavers.com Distribution: --- Created attachment 75028 --> https://bugs.winehq.org/attachment.cgi?id=75028 Example C code to show the issue This is probably not a Wine bug, but something we may want to document and take care of one way or another: i686-w64-mingw32-gcc quietly assumes 16 byte stack alignment, which is wrong for Win32. To see the effect compile and disassemble the attached test.c with i686-w64-mingw32-gcc test.c -c -O2 i686-w64-mingw32-objdump -d test.o The outcome: 0: 81 ec ac 01 00 00 sub $0x1ac,%esp 6: 8d 44 24 10 lea 0x10(%esp),%eax a: 89 04 24 mov %eax,(%esp) d: e8 00 00 00 00 call 12 <_func+0x12> 12: 81 c4 ac 01 00 00 add $0x1ac,%esp 18: c3 ret However, x86_64-w64-mingw32-gcc -m32 properly aligns the stack before placing the aligned structure: x86_64-w64-mingw32-gcc test.c -c -O2 -m32 i686-w64-mingw32-objdump -d test.o 0: 55 push %ebp 1: 89 e5 mov %esp,%ebp 3: 83 e4 f0 and $0xfffffff0,%esp 6: 81 ec a0 01 00 00 sub $0x1a0,%esp c: 8d 44 24 10 lea 0x10(%esp),%eax 10: 89 04 24 mov %eax,(%esp) 13: e8 00 00 00 00 call 18 <_func+0x18> 18: c9 leave 19: c3 ret To my knowledge Wine does not use SSE instructions on purpose, so we should be mostly fine. msvcrt, wined3d or dsound (especially when compiled to use SSE to make Rosetta 2 happy) may be affected. The test.c file is attached. What can we do about it? 1) Ignore it 2) pass -mincoming-stack-boundary=2 to mingw for 32 bit targets 3) Use 64 bit target mingw with -m32 I'll file a bug for mingw too, linking this bug as reference. -- 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 10

[Bug 56216] New: Wine 9.0 Wayland cursor does not hide when holding mouse button on game world to move camera/character
by WineHQ Bugzilla Jan. 31, 2024

Jan. 31, 2024

https://bugs.winehq.org/show_bug.cgi?id=56216 Bug ID: 56216 Summary: Wine 9.0 Wayland cursor does not hide when holding mouse button on game world to move camera/character Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yaomtc(a)protonmail.com Distribution: --- I have tested this with Final Fantasy XIV. In FFXIV, intended behavior is for the cursor to be hidden while holding down the left and/or right mouse button to move the camera and/or your character. It does not, it just locks in place (good, but it should be invisible too). This works correctly with X11 or XWayland, but with the experimental Wayland driver, the cursor does not hide. -- 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 55041] New: QuickTime movie plays but screen is black
by WineHQ Bugzilla Jan. 30, 2024

Jan. 30, 2024

https://bugs.winehq.org/show_bug.cgi?id=55041 Bug ID: 55041 Summary: QuickTime movie plays but screen is black Product: Wine Version: 8.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mildred-bug.winehq(a)mildred.fr Distribution: --- When running "The Wheel of Time" https://appdb.winehq.org/objectManager.php?sClass=version&iId=2154 cutscenes will play but the screen stays black. It uses QuickTime Lite 4.1.0 for movies. Using wayland (SwayWM) During movie playback, I see the following log repeated: 0058:fixme:mountmgr:harddisk_ioctl Unsupported ioctl 70c00 (device=7 access=0 func=300 method=0) There is in a forum someone that had a similar issue and found a solution (translated by me): > I think the problem comes from QuickTime, the software installs version 7.2 > Via wine control, I disabled directx for the video and set up safe move (GDI only) > It seems to hold, I must test again to be sure. > The issue really came from quicktime and my change solved the issue. > > https://forum.ubuntu-fr.org/viewtopic.php?id=389950 I tried winetricks render=nod3d or render=gdi but it does not help. -- 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