July 2024 - Wine-Bugs - list.winehq.org

[Bug 57013] Unable to install metastock 19 on m2 studio, however I was able to install notepad++

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57013 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Installer Severity|blocker |normal -- 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.

July 30, 2024

[Bug 57014] New: WINE may have turned into a system killer

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57014 Bug ID: 57014 Summary: WINE may have turned into a system killer Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine_bugzilla(a)sctb.ch Distribution: --- 1. I use a WIN32 text editor, PFE, which I run under WINE. 2. There has always been a bug in that after closing the laptop lid and then opening it again (which does not even send the laptop to sleep, but will turn the screen off), all PFE windows are now almost complete off-screen, with only the very bottom-right corner of the PFE window being visible in the very top-left corner of the screen. 3. To get out of this, I go to the running-applications bar (Debian, XFCE), right click on PFE, select "move" and then I can drag the window, and I put it back where I can see it. 4. I also play Vanilla WoW, 32 bit client. Recently, last month or so, a new bug has turned up, in that at busy times, occasionally, the client will freeze up *graphically*. Closing the laptop lid, and opening it again, fixes the freeze up. 5. For WoW, unlike PFE, closing the lid simply makes the WoW client minimize, so I can return to the game by clicking on its icon in the running-applications bar. 6. Now the kicker - PFE sometimes opens up a Yes/No dialog. It's modal. PFE had just opened such a dialog when the screen froze up, as it does with WoW. I closed the lid and opened it again - now PFE is as usual off-screen way up to the top-left. 7. Only problem now is all mouse clicks and key presses no longer have any effect. My guess is the modal dialog is absorbing them - but I can't see it to operate it correctly, and I can't right click on "Move" to drag PFE back on screen, and the dialog has no icon of its own in the running-applications bar, so I can't reach it. In the end, I had to hard reboot via the power button. -- 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.

July 30, 2024

[Bug 57013] Unable to install metastock 19 on m2 studio, however I was able to install notepad++

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57013 --- Comment #1 from bprakg(a)hotmail.com --- Mac M2 studio of 2023 running sonoma 14.5 -- 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.

July 30, 2024

[Bug 57013] New: Unable to install metastock 19 on m2 studio, however I was able to install notepad++

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57013 Bug ID: 57013 Summary: Unable to install metastock 19 on m2 studio, however I was able to install notepad++ Product: Wine Version: 9.0 Hardware: Other OS: MacOS Status: UNCONFIRMED Severity: blocker Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: bprakg(a)hotmail.com Created attachment 76857 --> https://bugs.winehq.org/attachment.cgi?id=76857 log of the error Hi, I am unable to install metastock 19 on m2 studio, however I was able to install notepad++ I get this error; "0128:err:d3d:wined3d_check_gl_call >>>>>>> GL_INVALID_FRAMEBUFFER_OPERATION (0x506) from glClear @ /private/tmp/wine-9.0/dlls/wined3d/context_gl.c / 2339" I installed wine-stable running 9.0 I am using Mac m2 studio running sonoma 14.5. Full log of the error 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.

July 30, 2024

[Bug 57011] GameStudio 3D program freezes on fflush since wine-9.5

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57011 --- Comment #2 from Paul Gofman <pgofman(a)codeweavers.com> --- I've debugged this and it looks like the attached script bug (not even the app's one) and this script executes without errors on Windows by chance only. > fhandle_n = file_open_write ("bubu.txt"); > xhandle_n = fhandle_n; > diag_var("\nfhandle_n: %6.3f",fhandle_n); > > file_str_write(fhandle_n, "bubu\n\r"); > diag("\ncomes"); > diag_var("\nfhandle_n: %6.3f",fhandle_n); > fflush(xhandle_n); // stucks here.. Here the engine executing the script calls msvcrt.fflush(pointer). msvcrt.fflush() assumes it is FILE structure but it is not. It is some internal engine's structure returned by file_open_write(), no msvcrt / else MS CRT functions are called to execute those other engine's function, the engine works with kernel32.CreateFile() etc. directly. msvcrt has the logic to lock with EnterCriticalSection. If FILE structure was created by msvcrt itself it finds the critical section in the own data, if it was not then it assumes CRITICAL_SECTION follows FILE structure (that matches Windows behaviour). That data (along with the other FILE fields) fflush() receives are nonsensual. It is only a matter of random that it doesn't crash in msvcrt trying to do actual fflush (probably not entirely on random, a bit more on that below). But the random data for "critical section" are so that after the blamed commit our implementation decides first that it should wait (depends on CRITICAL_SECTION.LockCount) and then that the WaitSemaphore is semaphore which yields observed behaviour. I tested that on Windows under similar conditions EnterCriticalSection doesn't lockup but throws an exception. Doing so in Wine (I sent the patch for that upstream: https://gitlab.winehq.org/wine/wine/-/merge_requests/6175) results in the message box pop up when trying to execute this script. On Windows there is no such message box, this script in its exact form executes silently. But it is only a matter of semi-random data on stack (the address passed to fflush points to stack and apparently contains some unrelated other data). This random data happens to be a bit different on Windows with LockCount such as it doesn't tries to wait on this "would be" critical section, only updates critical section's field (probably corrupting unrelated data on stack). Note that in this repro script fhandle_n is copied to xhandle_n before file_str_write and fflush. Changing that to a straightforward way (just fflush(fhandle_n)) causes access violation in this fflush() both on Windows and Wine and results in a message box complaining about invalid access. That's probably why the script author "worked around" this issue by copying that to another object, but fflush() still doesn't work and just doesn't do anything as best, it gets not a msvcrt's FILE strcuture. So I think the current behaviour with my MR is better than on Windows in a sense that it doesn't result in a silent successful execution of a broken script. But that can change anytime of course because depends on something unrelated in stack data. So this is a script bug and the app's script engine just doesn't perform any sort of validation on what passed to native (msvcrt in this case) functions, so what happens if the script does that is random. I sent the MR upstream (https://gitlab.winehq.org/wine/wine/-/merge_requests/6175) because that looks like a correct change to me and makes EnterCriticalSection sort of more robust and behaving like on Windows. But broadly it seems to me there is nothing to fix here and this change also doesn't guarantee that such things work anyhow predictable on such script bugs (that's basically the same on Windows, even if in the present case the semi-random app's on-stack data are a bit different resulting in a different behaviour). Unless there will be some considerations why this would be wrong, I'd probably suggest closing this bug as invalid regardless of whether my patch goes in or not. -- 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.

July 30, 2024

[Bug 53297] Issue when launching DX11 game (FFXIV) on FreeBSD

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53297 Gerald Pfeifer <gerald(a)pfeifer.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gerald(a)pfeifer.com -- 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.

July 29, 2024

[Bug 57005] Wine segfaults on macOS when run from install

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57005 --- Comment #1 from Brendan Shanks <bshanks(a)codeweavers.com> --- Thanks for the report, I'm able to reproduce this crash. It's something related to environment variables. -- 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.

July 29, 2024

[Bug 56701] Ubisoft Connect - Missing tex2Dbias support

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56701 --- Comment #6 from Nikolay Sivov <bunglehead(a)gmail.com> --- You'll have to wait for wine's copy of vkd3d to be updated first, that will happen after next vkd3d release. -- 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.

July 29, 2024

[Bug 56701] Ubisoft Connect - Missing tex2Dbias support

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56701 --- Comment #5 from claytmp+foj0w(a)gmail.com --- Sorry, this issue still present on Wine devel 9.13 on my mac running Sonoma 14.5. Ubisoft has changed the login screen layout so it will show the black window instead invisible. See attachment "Logs+Screenshots 29-7-2024" -- 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.

July 29, 2024

[Bug 56701] Ubisoft Connect - Missing tex2Dbias support

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56701 --- Comment #4 from claytmp+foj0w(a)gmail.com --- Created attachment 76856 --> https://bugs.winehq.org/attachment.cgi?id=76856 Logs+Screenshots 29-7-2024 -- 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.

July 29, 2024