February 2022 - Wine-Bugs - list.winehq.org

[Bug 52595] Starts with black window

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52595 --- Comment #1 from stefan <k8auf1947(a)cometchaser.de> --- Created attachment 71921 --> https://bugs.winehq.org/attachment.cgi?id=71921 App starts with Wine 7.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.

Feb. 26, 2022

[Bug 52595] New: Starts with black window

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52595 Bug ID: 52595 Summary: Starts with black window Product: Wine Version: 7.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: k8auf1947(a)cometchaser.de Distribution: --- Created attachment 71920 --> https://bugs.winehq.org/attachment.cgi?id=71920 App starts with black window, Wine 7.2 on Bullseye The application starts and shows a black window (application menue is shown). After clicking into the black window, the application draws the window. It worked until Wine 7.1, problem appears with Wine 7.2 on Debian Bullseye. Happens also on Debian Bookworm. File: test-2022-02-25_18.50.43.mp4 Wine 7.1 on Bookworm File: test-2022-02-26_10.40.38.mp4 Wine 7.2 on Bullseye -- 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.

Feb. 26, 2022

[Bug 52585] NtQueryDirectoryObject multiple entries not implemented, breaks shells on Cygwin

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52585 --- Comment #2 from megastallman <megastallman(a)gmail.com> --- Cool! Zebediah, may I try those? -- 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.

Feb. 26, 2022

[Bug 52502] Mupen64-RR-Lua: Title and menu bar are not refreshed properly

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52502 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #8 from Zebediah Figura <z.figura12(a)gmail.com> --- It's not particularly convenient, but you can generally bisect between wine and wine-staging. There are basic instructions here: <https://wiki.winehq.org/Wine-Staging#Reporting_and_debugging_bugs_against_S…> -- 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.

Feb. 26, 2022

[Bug 52502] Mupen64-RR-Lua: Title and menu bar are not refreshed properly

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52502 --- Comment #7 from jackyguo18(a)hotmail.com --- (In reply to Zhiyi Zhang from comment #6) > Working in staging doesn't mean it's fixed. Is the patch upstreamed? Do you > know which staging patch fix this? I don't know which patch it is. Is there a convenient way I could figure it out? -- 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.

Feb. 26, 2022

[Bug 52502] Mupen64-RR-Lua: Title and menu bar are not refreshed properly

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52502 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #6 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Working in staging doesn't mean it's fixed. Is the patch upstreamed? Do you know which staging patch fix 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.

Feb. 26, 2022

[Bug 52502] Mupen64-RR-Lua: Title and menu bar are not refreshed properly

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52502 jackyguo18(a)hotmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from jackyguo18(a)hotmail.com --- This bug has been fixed in Wine staging (version 7.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.

Feb. 26, 2022

[Bug 52037] MaiDenSnow Eve trial crashes upon entering load menu (use after free ?)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52037 --- Comment #11 from Rafał Mużyło <galtgendo(a)o2.pl> --- I've made no progress since - still crashes with 7.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.

Feb. 26, 2022

[Bug 52593] RPG Maker MV: Crash in bundled qt5webenginecore on project open

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52593 --- Comment #1 from Zoë Sparks <zoe(a)milky.flowers> --- The following rough and hacky procedure doesn't prevent the crash, but it does delay it for a significant amount of time in my environment (maybe a couple minutes?). I found it on "accident" while trying to get more detailed logs around the crash. 1. From a fresh installation of MV, start it up with `WINEPREFIX=[PREFIX] wine 'C:\\Program Files\\KADOKAWA\\RPGMV\\RPGMV.exe'`. 2. Press "Continue" when you see the registration screen and wait. 3. Once you can use the program, create a new project. MV will crash a few seconds after the project is finished. The project itself will still be there; the crash occurs after project creation fully completes. 4. Make a FIFO (e.g. `mknod /tmp/wine_rpgmv_debug p`). 5. Edit the `projectFileUrl` registry key in `[Software\\KADOKAWA\\RPGMV]` and give it a blank string value. 6. Start the program with `WINEPREFIX=[PREFIX] WINEDEBUG=+seh,+relay wine 'C:\\Program Files\\KADOKAWA\\RPGMV\\RPGMV.exe' &>/tmp/wine_rpgmv_debug`. 7. Attach the read end of the FIFO to /dev/null (i.e. `cat /tmp/debug_log > /dev/null`). 8. Press "Continue" when you see the registration screen and wait for MV to start up. 9. Once it's up, open up the project open dialog to open your just-created project, but don't actually open it yet. 10. Stop sending the wine/MV output to /dev/null and instead redirect it to a file, ideally a file on a slow HDD with a lot of space as it will write several GB of text quickly. The point is just to slow the wine process down as much as possible. There are certainly more elegant ways of slowing Wine down than this if it's truly needed (patching Wine with some time-wasting junk code in the right place for example)—I'm mainly recording this process for the sake of having a record. 11. Actually open the project. 12. Once it's open, wait a bit, then stop sending the wine/MV output to your scratch file and instead send it back into /dev/null. 13. You should have a couple of minutes in which you can actually use MV almost-normally before the same type of crash occurs (the backtrace is identical etc.). It's pretty responsive with the output sent to /dev/null and everything seems to work properly during that time. The only thing that was a bit wonky is I found that if I tried to launch the project, nothing happened at first, but after the main editor crashed the game process would actually start up, perhaps just because of the extensive overhead introduced into the project start routines by all the logging. The game ran fine though after that point. I wish I could say whether or not this is due to some periodic qt5webenginecore thread that's launched every so often by MV, such that the earlier crash shortly after opening a project is "dodged" by this procedure, or if it's the "same" crash that's merely delayed by the logging overhead. I have yet to actually see the crash with +relay on, which is unfortunate. It may occur eventually, but if I'm actually redirecting the output to a file I run out of hard drive space before I see a crash. It's possible that the extreme slowness induced by +relay and output to a file on disk prevents the crash somehow, but also that it would still occur eventually if I waited long enough. The best logs I've gotten so far are with `WINEDEBUG=+seh,+tid,warn+all`, but although I can see the crash I have yet to make much heads or tails of them beyond that. You still end up with around 8G or so of log. One idea I had was to try to cross-compile a debug build of the same version of Qt5 MV is using and drop in the relevant libraries from that, but (a) I'm not quite sure which Qt5 it's using yet and (b) cross-compiling Qt5 is its own wacky adventure, as I found out. Still, this strategy may yet yield fruit. -- 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.

Feb. 26, 2022

[Bug 52594] New: rustup-init.exe panic in reqwest failed to park thread

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=52594 Bug ID: 52594 Summary: rustup-init.exe panic in reqwest failed to park thread Product: Wine Version: 7.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lorenzofer(a)live.it Distribution: ArchLinux The rustup executable (rustup-init.exe) panic with thread 'reqwest-internal-sync-runtime' panicked at 'failed to park', C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\tokio-1.4.0\src\runtime\basic_scheduler.rs:224:56 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace This is from wine 7.0rc1 Wine 6.23 give another issue: error: could not download file from 'https://static.rust-lang.org/dist/channel-rust-stable.toml.sha256' to 'C:\users\lorenzo\.rustup\tmp\atqc1z0zr2x8cjfz_file': failed to make network request: error sending request for ur l (https://static.rust-lang.org/dist/channel-rust-stable.toml.sha256) error trying to connect: OS Error -2146762482 (FormatMessageW() returned error 317) (os error -2146762482): error trying to connect: OS Error -2146762482 (FormatMess ageW() returned error 317) (os error -2146762482): OS Error -2146762482 (FormatMessageW() returned error 317) (os error -2146762482) Not sure if this is a regression, or in 7.0rc1 there was a patch the solved an error before I'm going to bisect -- 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.

Feb. 25, 2022