June 2025 - Wine-Bugs - list.winehq.org

[Bug 56593] The program winevdm.exe has encountered a serious problem ...

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=56593 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Abandoned? -- 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.

June 5, 2025

[Bug 56946] Include fixes for mmsystem.dll16 and user.dll16 from WineVDM project

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=56946 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement -- 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.

June 5, 2025

[Bug 58301] SendInput(MOUSEEVENTF_MOVE) does nothing

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58301 --- Comment #4 from Nikita <mornickmylo(a)gmail.com> --- Just asked a friend to test the example program. He's got Fedora 42 and the behaviour is the same, pointer does not move -- 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.

June 5, 2025

Solar Powered GPS Tracking devices

by Mark

June 5, 2025

[Bug 58326] SetupDiGetClassDevs does not enumerate USB devices

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58326 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com Component|setupapi |usb --- Comment #3 from Zeb Figura <z.figura12(a)gmail.com> --- What is your end goal? -- 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.

June 5, 2025

[Bug 58332] ntdll: Session shared memory gets mapped with MAP_PRIVATE, which causes rr-debugger to fail.

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58332 Bernhard Übelacker <bernhardu(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Debian Version|unspecified |10.4 Keywords| |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.

June 5, 2025

[Bug 58332] New: ntdll: Session shared memory gets mapped with MAP_PRIVATE, which causes rr-debugger to fail.

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58332 Bug ID: 58332 Summary: ntdll: Session shared memory gets mapped with MAP_PRIVATE, which causes rr-debugger to fail. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Debugging Wine with rr-debugger allows to record whole wine process trees, and debug later different processes, e.g. wineserver and the .exe process, debug early startup or exception code, debug in reverse and multiple times. Therefore I asked for inclusion of [1] "spurious short writes", which got accepted at 2025-04-25. Thank you very much for it. Unfortunately short after it I found there is still an issue, which was a few months not there. So I started bisecting and arrived at [2] d9d012965de, "ntdll: Always map files as writable and adjust permissions.", committed at 2025-03-25. Unfortuntately this can not be cleanly reverted at current git, but with three more commits reverted it makes a wine tree, which can be used with rr-debugger [2]. I could reduce the changes of this 4 commits to a few lines which, are also able to produce a wine tree usable with rr-debugger [3]. This patch is only changing behaviour once for each .exe process, when the session shared memory gets mapped in via the fd received from wineserver. With unmodified Wine this is currently done with a MAP_PRIVATE flag, which turns out is currently just mapping the file content into the process, but does not receive the updates from wineserver. To investigate if this can be fixed in rr I opened [4]. Unfortunately this would be expected to create a overall slowdown for rr. Therefore I wonder if this change was intentional, to map the session shared memory with mmap(MAP_PRIVATE)? When looking at virtual_map_user_shared_data the shared memory gets mapped with mmap(MAP_SHARED). Would something like [3] be acceptable for inclusion? Kind regards, Bernhard [1] https://gitlab.winehq.org/wine/wine/-/commit/cd197f8588b [2] https://gitlab.winehq.org/wine/wine/-/commit/07160a23fa2 https://gitlab.winehq.org/wine/wine/-/commit/9e006e94c9c https://gitlab.winehq.org/wine/wine/-/commit/8fd49c4d8e9 https://gitlab.winehq.org/wine/wine/-/commit/d9d012965de [3] https://gitlab.winehq.org/bernhardu/wine/-/commit/658e56801a7 [4] https://github.com/rr-debugger/rr/issues/3972 -- 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.

June 5, 2025

[Bug 58331] New: Wait cursor does not display

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58331 Bug ID: 58331 Summary: Wait cursor does not display Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: win32u Assignee: wine-bugs(a)winehq.org Reporter: rikul(a)inbox.ru Distribution: --- Created attachment 78705 --> http://bugs.winehq.org/attachment.cgi?id=78705 Example Starting from Wine version 9.0, the waiting cursor no longer appears when attempting to set it to indicate a long-running operation in MFC applications or other programs. The issue appears to have started after the commit on June 13, 2023. Steps to Reproduce: 1. Run the attached simple MFC application. 2. Click the button "Start Long Operation" Expected Result: The waiting cursor should appear for the duration of the 3-second sleep. Actual Result: The waiting cursor does not appear during the Sleep call. The cursor remains the default arrow. Example Application: The example application has been attached. It uses the most basic implementation of the CWaitCursor class, as described in the official Microsoft documentation: https://learn.microsoft.com/en-us/cpp/mfc/reference/cwaitcursor-class?view=… Regression Commit: The issue seems to have started with the commits made on June 13, 2023: https://github.com/wine-mirror/wine/commits/master/dlls?author=rbernon&sinc… Notes: This issue does not occur in Windows, where the waiting cursor appears as expected. Environment: Wine version: 9.0+ (possibly Wine 8.x, but not 8.0) Operating System: RHEL 7.9, RHEL 8.10 -- 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.

June 5, 2025

[Bug 58327] Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R. Anomaly when using a scope

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58327 --- Comment #4 from tactica <tactica.os4(a)gmail.com> --- Created attachment 78704 --> http://bugs.winehq.org/attachment.cgi?id=78704 Console output from Wine 10.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.

June 5, 2025

[Bug 58327] Crash from d3d11 (assertion failed) in S.T.A.L.K.E.R. Anomaly when using a scope

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58327 --- Comment #3 from tactica <tactica.os4(a)gmail.com> --- 10.8. 10.7 and 10.1 all fail the same way I'm afraid. These are the only cached binaries I have. I didn't bother removing and re-applying d3d11 with winecfg between each downgrade, hopefully that's OK. The console output doesn't seem to show anything relevant but I'll attach what I get from 10.1 just in case. In the meantime I also tried maximizing the visual settings for the game, which eventually resulted in the same crash being triggered out of nowhere while moving around at a very high location, with plenty of distant places to look at. -- 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.

June 5, 2025