wine-bugs August 2024

wine-bugs@winehq.org

1 participants
1502 discussions

[Bug 57085] New: winebus SDL backend seems to always report force feedback effects as playing on linux, confuses BeamNG.drive 0.32.5.0
by WineHQ Bugzilla 20 Aug '24

20 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=57085 Bug ID: 57085 Summary: winebus SDL backend seems to always report force feedback effects as playing on linux, confuses BeamNG.drive 0.32.5.0 Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: hid Assignee: wine-bugs(a)winehq.org Reporter: katharine.chui(a)gmail.com Distribution: --- Wine/Proton users have not been able to use "Fast" update type on BeamNG.drive. https://www.beamng.com/threads/workaround-to-get-ffb-to-work-on-linux-proto… After reporting the lack of IDirectInputEffect::Start calls on Wine to BeamNG.drive, it seems that they will be force issuing ::Start once after ::CreateEffect in a future update, regardless of the output of ::GetEffectStatus, if the change does not break other wheels on windows. Discussing the issue further with BeamNG.drive developer stenyak on discord, with "Fast" update type for force feedback, current release of BeamNG.drive seems to always query effect status using ::GetEffectStatus, and would only issue ::Start if the effect is not playing. If my tracing is correct, https://gitlab.winehq.org/wine/wine/-/blob/6e15604c48acd63dd8095a4ce2fd011c… always emits effect playing report on hid because on Linux, SDL does not support SDL_HAPTIC_STATUS. Due to ::GetEffectStatus flagging effect playing falsely, ::Start is never issued on Wine, causing effects to never play on the SDL hid backend. While BeamNG.drive seems to be quite open to doing small fixes to help players on Wine/Proton as long as it does not break on windows, is there anything that could be change on this end to make it less confusing for applications that relies on ::GetEffectStatus going forward? -- 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 43146] New: gtkmm hello world program can't show window
by wine-bugs＠winehq.org 20 Aug '24

20 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=43146 Bug ID: 43146 Summary: gtkmm hello world program can't show window Product: Wine Version: 2.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bing(a)nym.hush.com Distribution: --- Created attachment 58373 --> https://bugs.winehq.org/attachment.cgi?id=58373 gtkmm hello world tarball So I tried the gtkmm hello world program: https://developer.gnome.org/gtkmm-tutorial/stable/sec-helloworld.html.en and I put it in a tarball (Attached.) Anyway, I cross-compiled it with mingw and it runs fine in a windows VM. When I run it with wine though, it crashes -- which is surprising because the program does so little! I ran it with GDK_DEBUG=all and I can see that it's crashing on the showing of a window. I guess I should mention that I'm running this in an Xorg session, and not Wayland. Anyway, I'm running wine 2.8 as provided by Fedora 25. Here is the backtrace: https://pastebin.com/yWZkHkDZ I don't know if it's customary to upload executables here, so I won't do that unless asked. -- 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 15

[Bug 56633] New: Version 9.8 source code triggers a virus alert on MacOS Sonoma on M3
by WineHQ Bugzilla 20 Aug '24

20 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=56633 Bug ID: 56633 Summary: Version 9.8 source code triggers a virus alert on MacOS Sonoma on M3 Product: Wine Version: unspecified Hardware: aarch64 OS: MacOS Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: erisi(a)comcast.net When attempting to download source for 9.8, a virus alert is triggered on my MBP. This does not happen with 9.7 source. -- 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 49381] New: Building wine from source on 32 bit Slackware Linux fails since 5.10.
by WineHQ Bugzilla 20 Aug '24

20 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=49381 Bug ID: 49381 Summary: Building wine from source on 32 bit Slackware Linux fails since 5.10. Product: Wine Version: 5.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: studiosg(a)giustetti.net Distribution: --- Created attachment 67441 --> https://bugs.winehq.org/attachment.cgi?id=67441 Archive containing the configure, make dep and make output in 2 files The issue arises while building Wine 5.10 on 32 bit Slackware. Both Slackware 14.2 stable and current (15.0 beta) are affected while The 64 bit version builds just fine. The build procedure exits badly while linking ntdll.so, returning errors like: /usr/bin/ld: unix/server.o: in function `remove_fd_from_cache': server.c:(.text+0x29d): undefined reference to `InterlockedCompareExchange64' /usr/bin/ld: unix/server.o: in function `add_fd_to_cache': server.c:(.text+0x60f): undefined reference to `InterlockedCompareExchange64' The output of the configure, make dep and make command is included into the attached archive. They refer to the 14.2 current environment. Thanks Simone -- 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 9

[Bug 47396] New: Lord of the Rings Mouse Pointer falls back to System-Pointer since wine 4.9
by wine-bugs＠winehq.org 20 Aug '24

20 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=47396 Bug ID: 47396 Summary: Lord of the Rings Mouse Pointer falls back to System-Pointer since wine 4.9 Product: Wine Version: 4.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wasti2k(a)gmail.com Distribution: --- Mouse Pointer falls back to System-Pointer since wine 4.9 Mouse Pointer changes to System Pointer, by moving the pointer over an enemy. Last working Version was Wine 4.6 -- 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 56842] New: Run the absolute path exe file and use the current process to retrieve the working directory as Linux working directory, not Windows working directory. ( GetCurrentDirectoryW -->NtCurrentTeb() -->Peb -->ProcessParameters -->CurrentDirectory DosPath）
by WineHQ Bugzilla 20 Aug '24

20 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=56842 Bug ID: 56842 Summary: Run the absolute path exe file and use the current process to retrieve the working directory as Linux working directory, not Windows working directory. ( GetCurrentDirectoryW -->NtCurrentTeb() -->Peb -->ProcessParameters -->CurrentDirectory DosPath） Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: zmtong1988(a)gmail.com Distribution: --- 1. Running the desktop lnk file will use SetCurrentDirectoryW() to set the current entry working directory, while GetCurrentDirectoryW() obtains the normal Windows working directory. 1) While processing the lnk file, parse the shell: IPersistStream_fnLoad Working Dir ->L "C: \ \ Program Files (x86) \ \ test \\" 2) SHELL_execute -->dir=L "C: \ \ Program Files (x86) \ \ test \\" 3) Set working directory: SetCurrentDirectoryW() -->L "C: \ \ Program Files (x86) \ \ test \\" 4) Get working directory GetCurrentDirectoryW() ->us=&NtCurrentTeb() ->Peb ->ProcessParameters ->CurrentDirectory DosPath The working directory obtained is L "C: \ \ Program Files (x86) \ \ test \ \". At this point, the application obtains the working directory of the current process through GetCurrentDirectoryW(), which is the normal windwos working directory. 2. Run the absolute path exe and use GetCurrentDirectoryW() to obtain the current process directory, which is the working directory for running Linux. 1) SHELL_execute -->dir=(null) 2) GetCurrentDirectoryW() -->L "Z: \ \ home \ \ work \ \ desktop\\ Retrieve the working directory of a running command process (for example, when I open a terminal on the desktop to run a command, the working directory obtained is: L "Z: \ \ home \ \ work \ \ desktop \ \). At this point, the application obtains the working directory of the current process as the Linux working directory through GetCurrentDirectoryW(). The file we need to load is in the Windows working directory, not in the current process's working directory, which prevents us from finding the corresponding file in the working directory. -- 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 9

[Bug 56773] New: PES 2014 lags a lot during gameplay, sound gets choppy
by WineHQ Bugzilla 20 Aug '24

20 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=56773 Bug ID: 56773 Summary: PES 2014 lags a lot during gameplay, sound gets choppy Product: Wine Version: 9.0 Hardware: arm OS: MacOS Status: UNCONFIRMED Severity: major Priority: P1 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Tanvirmahtab1(a)outlook.com The in-game menu works great but whenever launching a match, game starts to lag and sound gets broken. I use crossover 24. -- 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 45244] New: MapleStory: screen freezes with certain audio files
by wine-bugs＠winehq.org 20 Aug '24

20 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=45244 Bug ID: 45244 Summary: MapleStory: screen freezes with certain audio files Product: Wine Version: 3.8 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alpha.s3r(a)gmail.com Created attachment 61485 --> https://bugs.winehq.org/attachment.cgi?id=61485 Trimmed bug report. Frame Sync failed repeated indefinitely (but file size was 125 MB), so I erased most of those lines. Wine screen freezes when playing certain audio files. It seems to be either non-MPEG2 files or audio files that don't conform to 24k bps or 22050 Hz (any audio under this classification seems to be fine). The specific audio file that was used to replicate the crash was: MPEG 2.5 / 8k bps / 8000 Hz. I've tested out other Wine versions, and Wine Stable 3.0 has the same error, along Wine Staging 3.6, 3.7, 3.8. However, if you use Wine 2.22 or Wine 1.4.1, the app runs fine and doesn't freeze at these sound effects. -- 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 9

[Bug 39276] New: Resizing window in TellTale games does not resize active area
by wine-bugs＠winehq.org 20 Aug '24

20 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=39276 Bug ID: 39276 Summary: Resizing window in TellTale games does not resize active area Product: Wine Version: 1.7.50 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: robertc(a)gmail.com Distribution: --- In recent Telltale games (Walking Dead Season 2, Tales from the Borderlands) resizing the display leads to some areas of the screen becoming hidden. The games start in 1024x768 resolution by default, if you change that in the game settings to, for instance, match your desktop resolution then you end up with a 1024x768 panel showing the top left of game in the middle of a blank/broken area. It is possible to interact with things outside the 1024x768 panel but you have to guess where they are. I've attached a screenshot of the issue on my 1366x768 laptop. This doesn't happen with The Walking Dead Season 1 so I assume this is some update that Telltale have made to their game engine which is now broken in WINE. -- 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 6

[Bug 56629] New: PCK-Studio: Freezes computer when run.
by WineHQ Bugzilla 20 Aug '24

20 Aug '24

https://bugs.winehq.org/show_bug.cgi?id=56629 Bug ID: 56629 Summary: PCK-Studio: Freezes computer when run. 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: TIMenderslime(a)gmail.com Distribution: --- Error when running PCK-Studio.exe from https://github.com/PhoenixARC/-PCK-Studio . Steps to reproduce 1. Download any release or Beta (I tried https://github.com/PhoenixARC/-PCK-Studio/releases/tag/Release_v5.8) 2. Extract the archive 3. Run "PCK-Studio.exe" Results After 10-60 seconds the system freezes and inputs from the mouse and keyboard do nothing (the mouse cursor will still move around, but it does not interact with anything). If I have a video or music playing in the background, they will continue to play normally untill either I press and hold power button to turn off my computer or my computer restarts from "something unexpected" occurring. -- 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 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs August 2024