wine-bugs

wine-bugs@winehq.org

1 participants
158874 discussions

[Bug 58187] New: page fault during NdrContextHandleUnmarshall when running cpu-z x64 version
by WineHQ Bugzilla 08 May '25

08 May '25

http://bugs.winehq.org/show_bug.cgi?id=58187 Bug ID: 58187 Summary: page fault during NdrContextHandleUnmarshall when running cpu-z x64 version Product: Wine Version: 10.5 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: rpc Assignee: wine-bugs(a)winehq.org Reporter: 2012720421(a)qq.com Distribution: --- Created attachment 78485 --> http://bugs.winehq.org/attachment.cgi?id=78485 the backtrace When running cpu-z on the arm64 platform with arm64ec mode, the rpcrt4 crashed by visiting invalid address. tried build rpcrt4 as arm64ec_x64 mode but failed also. Running on x64 PC seen fine and no crash occurred. -- 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

[Bug 58012] New: DOOM + DOOM II: rsaenh regression
by WineHQ Bugzilla 07 May '25

07 May '25

https://bugs.winehq.org/show_bug.cgi?id=58012 Bug ID: 58012 Summary: DOOM + DOOM II: rsaenh regression Product: Wine Version: 10.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: rsaenh Assignee: wine-bugs(a)winehq.org Reporter: joelh(a)disroot.org Distribution: --- Created attachment 78271 --> https://bugs.winehq.org/attachment.cgi?id=78271 backtrace of doom_gog.exe DOOM + DOOM II by Nightdive Studios released in 2024. I am using the GOG.com version. The game will get past the opening screens, then crash on the main menu. It worked okay in Wine 10.2. I have tracked down the problematic commit to: fd539487b7860ff0a53474aa6fbcbe229f3f42c1 rsaenh: Use the bundled tomcrypt to replace the local copy. -- 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 57570] New: Syntax Error in CMD Batch Parsing
by WineHQ Bugzilla 06 May '25

06 May '25

https://bugs.winehq.org/show_bug.cgi?id=57570 Bug ID: 57570 Summary: Syntax Error in CMD Batch Parsing Product: Wine-staging Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: juan3(a)yandex.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 77673 --> https://bugs.winehq.org/attachment.cgi?id=77673 running wine cmd When attempting to run the `msys2_shell.cmd` script from MSYS2, Wine fails with a syntax error: `Syntax error: unexpected IN`. This issue occurs during the batch file parsing phase. 1. Download the MSYS2 base archive from the following link: ``` https://github.com/msys2/msys2-installer/releases/download/2024-12-08/msys2… ``` 2. Extract the archive to a directory, e.g., `Z:\msys2\msys64`. 3. Navigate to the extracted directory: ``` Z:\msys2\msys64> ``` 4. Run the `msys2_shell.cmd` script with the following arguments: ``` msys2_shell.cmd -here -defterm -no-start ``` 5. Observe the error: ``` Syntaxfehler Syntax error: unexpected IN ``` The `msys2_shell.cmd` script should execute without errors and launch the MSYS2 shell environment. Wine fails with a syntax error: `Syntax error: unexpected IN`. -- 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 57621] New: using glfw with angle doesn't seem to work
by WineHQ Bugzilla 06 May '25

06 May '25

https://bugs.winehq.org/show_bug.cgi?id=57621 Bug ID: 57621 Summary: using glfw with angle doesn't seem to work Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: juan3(a)yandex.com Distribution: --- Created attachment 77741 --> https://bugs.winehq.org/attachment.cgi?id=77741 Wine crashes trying to run red_circle, something to do with not finding symbols on the dlls when building this project under msys2 windows https://github.com/Kreijstal/glfw-example.git and running it under wine, with the non windows dll dependencies copied over. It turns it can't run under wine. It works fine under windows however. -- 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

[Bug 56927] New: msys2-64/cygwin64: rsync fails with 'Socket operation on non-socket'
by WineHQ Bugzilla 06 May '25

06 May '25

https://bugs.winehq.org/show_bug.cgi?id=56927 Bug ID: 56927 Summary: msys2-64/cygwin64: rsync fails with 'Socket operation on non-socket' Product: Wine Version: 9.12 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- Created attachment 76749 --> https://bugs.winehq.org/attachment.cgi?id=76749 Notes to reproduce, a backtrace in cygwin/wine. I tried to check if bug #19858 is still an issue. Unfortunately I hit a rsync call which fails: $ rsync -aq --delete-before dir-a dir-b rsync: [Receiver] Failed to dup/close: Socket operation on non-socket (108) rsync error: error in IPC code (code 14) at pipe.c(157) [Receiver=3.2.7] rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(231) It looks like rsync forks a child process, and the child tries then to close the derived socket, which cannot be found in closesocket/socket_list_remove. This seems kind of similar to bug #54995. -- 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 53574] New: MSYS2 "pacman -Sy" fails key lookup
by WineHQ Bugzilla 06 May '25

06 May '25

https://bugs.winehq.org/show_bug.cgi?id=53574 Bug ID: 53574 Summary: MSYS2 "pacman -Sy" fails key lookup Product: Wine Version: 7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joel(a)airwebreathe.org.uk Distribution: --- Created attachment 72951 --> https://bugs.winehq.org/attachment.cgi?id=72951 Log of console interaction With a fresh Msys2 installation, pacman fails to run, because it keeps producing "key lookup failed" errors. The user is prompted to with the following message: error: mingw32: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown :: Import PGP key 5F944B027F7FE2091985AA2EFA11531AA0AA7F57? [Y/n] Y However, if the user selects "yes", pacman simply asks the same question again after a short delay, in an infinite loop. -- 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 58144] New: Wordpad: garbage in dialog when opening Edit>Advanced>Complete Text
by WineHQ Bugzilla 05 May '25

05 May '25

http://bugs.winehq.org/show_bug.cgi?id=58144 Bug ID: 58144 Summary: Wordpad: garbage in dialog when opening Edit>Advanced>Complete Text Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Distribution: --- As logged in ReactOS https://jira.reactos.org/browse/CORE-19868 with possible fix in https://github.com/reactos/reactos/pull/7922 Open Wordpad Do NOT enter any content Edit>Advanced>Complete Text Shows a first "empty" dialog (expected, as no content) then shows a second dialog with some garbage ==> Should not happen. -- 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 53121] New: IrfanView: In full screen mode the image title is not correctly repainted when switching between images
by WineHQ Bugzilla 05 May '25

05 May '25

https://bugs.winehq.org/show_bug.cgi?id=53121 Bug ID: 53121 Summary: IrfanView: In full screen mode the image title is not correctly repainted when switching between images Product: Wine Version: 7.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aros(a)gmx.com Distribution: --- Created attachment 72576 --> https://bugs.winehq.org/attachment.cgi?id=72576 Example Steps to reproduce: 1. Download IrfanView 2. File -> Open an image file (which matches or exceeds your display resolution) 3. Press Enter (goes in full screen mode) 4. Press right arrow or left arrow (alternatively "Space" and "Back Space") to browse through images forward or backward. The area where the image path and name are being rendered starts to look bad (i.e. it's not correctly repainted). It's in the left top corner. The example is attached. -- 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 1

[Bug 42284] New: Enable using Wine with Wayland and without X on Linux
by wine-bugs＠winehq.org 05 May '25

05 May '25

https://bugs.winehq.org/show_bug.cgi?id=42284 Bug ID: 42284 Summary: Enable using Wine with Wayland and without X on Linux Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com Distribution: --- Currently, Wine on Linux is strongly dependent on X, and when used with the desktop environment with new Wayland display server, Wine is forced to run through XWayland, which so far remains a poor experience. The whole Linux desktop is now strongly pushing the switch from X to Wayland, and many major applications are now in the process of enabling this switch. Is there some plan for such effort in Wine? Is it even feasible? I couldn't find any bugs opened for it, so I'm opening one here to track this. -- 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 77

[Bug 58106] New: PrintDialog (System.Windows.Controls): does not set PageRange and PageRangeSelection
by WineHQ Bugzilla 05 May '25

05 May '25

http://bugs.winehq.org/show_bug.cgi?id=58106 Bug ID: 58106 Summary: PrintDialog (System.Windows.Controls): does not set PageRange and PageRangeSelection Product: Wine Version: 10.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: igor.ivanov.0501(a)gmail.com Distribution: --- Created attachment 78364 --> http://bugs.winehq.org/attachment.cgi?id=78364 Sample App for VS22 with executable After opening PrintDialog and manually setting PageRange returned result will be unchanged. See sample in attachment -- 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 8

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