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

[Bug 53726] Silent Hill 4: The Room low res videos are not played

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53726 --- Comment #5 from Matheus <matheus.venturini(a)acad.ufsm.br> --- I played the demo again and I discovered there's a much, much easier way to test this: 1. Download the Silent Hill 4: The Room demo 2. Launch the game and wait at the title screen for abound one minute, do not give any input to the game The game should play the trailer for the game, which is a FMV, but on Wine it will fade to black and back again without playing it. The FMV I mentioned in my previous comment (comment) will also not play, but the demo can be played to the end without any other problems. I obtained a log of the title screen FMV problem (I did exactly the same two steps as I mentioned above on a fresh prefix and then quit the game), but it appears to not have revealed anything interesting. I'm also attaching one of me playing through the entire demo, in case it is helpful in any way. -- 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.

Oct. 6, 2022

[Bug 53718] WoW Beta/PTR get "Your 3D accelorator card is not supported"

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53718 --- Comment #28 from Ahmed W. <oneofone(a)gmail.com> --- As of today, the beta runs fine on normal wine and wine-tkg. -- 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.

Oct. 6, 2022

[Bug 49933] Alt+Tab doesn't work with gog installers

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49933 --- Comment #44 from Matheus <matheus.venturini(a)acad.ufsm.br> --- Yes, it still happens in 7.18. When the window receives focus the message I get is WINNLSEnableIME hwnd 00010102 enable -1: stub, and when it loses focus it's WINNLSEnableIME hwnd 00010102 enable -1: stub. The GOG installers are really buggy with Wine, most of the time alt+tab doesn't work with them but sometimes it does work, restoring the window from the task bar sometimes work but most of the time it doesn't, even minimizing the window by clicking on the task bar icon doesn't work all the time, there isn't any obvious logic behind all this weird behavior. -- 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.

Oct. 6, 2022

[Bug 53763] eSword crashes when changing fonts, throws Text Control error on newer bible modules

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53763 Rodney Barnes <thegamemaster(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://www.e-sword.net/fil | |es/e-sword_1220_setup.exe -- 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.

Oct. 6, 2022

[Bug 53763] New: eSword crashes when changing fonts, throws Text Control error on newer bible modules

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53763 Bug ID: 53763 Summary: eSword crashes when changing fonts, throws Text Control error on newer bible modules Product: Wine Version: 7.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: thegamemaster(a)hotmail.com Distribution: --- eSword found here: https://www.e-sword.net/files/e-sword_1220_setup.exe Using Wine 7.18 on Fedora 36 KDE Spin. This behavior is observed on several different machines including high end AMD 3900XT gaming system and low end Dell 1540 laptop. eSword 12.2.0 works fine under Wine 6.0.4 and does not exhibit these behaviors. When you click on certain newer bible modules it throws an error; "Error: 20058 Unexpected Text Control error. (1-1d03) This only happens on newer bible modules: LSB, LSB+, NASB, NASB+, ESV, ESV+,CSB, and TPT. If you click OK on the error message, the font colors change to black on gray, hard to see, and none of the "Perascope" links work, but the greek/hebrew Strongs Number links still work. Older bible modules work fine, including some with Parascope links such as NASB95, NASB95+. On the menu bar, if you click on Options, then on Font Settings... the program crashes. On the menu bar, if you click on Options, then on App Theme, and select any Theme the program locks up and must be forced to Terminate. -- 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.

Oct. 6, 2022

[Bug 48209] Ignore random parts of test failure messages

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=48209 Bug 48209 depends on bug 48912, which changed state. Bug 48912 Summary: Allow blacklisting unreliable and always new failures https://bugs.winehq.org/show_bug.cgi?id=48912 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- 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.

Oct. 6, 2022

[Bug 48912] Allow blacklisting unreliable and always new failures

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=48912 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from François Gouget <fgouget(a)codeweavers.com> --- This is done and an initial list of known bugs has been populated. >From the patchset cover: https://www.winehq.org/mailman3/hyperkitty/list/wine-devel(a)winehq.org/thr… This patchset provides support for tracking known failures in the TestBot results. The main goal is to avoid false positives but there are some side benefits as well: * The job reports sent to developers link to the relevant WineHQ bugs which gives them more exposure and may help get them fixed faster. * The failure details pages will eventually link to all the tasks where the failure happened, which could be valuable to find patterns. * The failure page tracks when it was last seen. This simplifies spotting bugs which are fixed and could be closed. (Or failures where the regular expression needs to be updated / fixed) The patchset mostly follows the scheme described in bug 48912: https://bugs.winehq.org/show_bug.cgi?id=48912 There are some differences though: * The bug envisionned this scheme purely as a blacklist to avoid false positives. The implementation can certainly be used in this way but it is not limited to failures that cause false positives. Tracking other failures can provide the side benefits mentionned above. The only limit is the maintenance work required to track more failures. * As a consequence the FailureBlacklist class was renamed to Failure, and the FailureBlacklistUses was renamed to TaskFailures since it links Tasks with the related Failures. * The FailureBlacklistVMs purpose is not really described in the bug but I think the goal was to provide a way to deckare that the failure is expected to only happen on specific test configurations. Instead the Failures class has a ConfigRegExp regular expression which specifies which test configurations the failure applies to. The test 'configuration name' is of the form 'VM:logfile' which allows matching specific Windows versions (thanks to the TestBot VM naming scheme), specific Windows locales (part of the VM name), specific bitnesses (part of the log filename), or specific Wine locales (part of the log filename). For instance: ^w8 -> all Windows 8 VMs :exe -> all Windows tests (exe32.report and exe64.report) ^w10.*_ja.*: -> all Windows 10 Japanese test configurations win|wow -> all Wine test configurations (win32.report, ...) (win|wow).*_fr -> French Wine test configurations * Changes in FailureBlacklists -> Failures - Primary key: (Bug, TestModule, TestUnit) -> Id Some issues generate quite a few failures. So in case trying to match them all results in a regular expression that's too long (either because of the database limit or for readability), this change makes it possible to add multiple Failure objects to track them all. - TestModule -> ErrorGroup The .errors files split the errors in groups. Each group corresponds to a test module, but extra errors (too much output, missing summary lines, etc) are in a separate group. So I renamed TestModule to ErrorGroup as a reminder to the coder that this is meant to match the .errors group names, not just test modules. - Name -> (BugStatus, BugDescription) Instead of having a name describing the failure, this patchset uses the corresponding WineHQ bug description. The TestBot also retrieves the bug status which allows checking that closed bugs dont happen anymore, or open bugs that should be closed. - LastUsed -> (LastNew, LastOld) The LastUse field was split into LastNew and LastOld to track whether the failure would cause false positives without the known failures support. * Changes in FailureBlacklistUses -> TaskFailures - (Bug, TestModule, TestUnit) -> FailureId This is a consequence of the Failure primary key change described above. - () -> (TaskLog) This allows tracking which task log the failure was found in. This is quite important for Wine tasks since they run all the test configurations in just one task. - () -> (NewCount, OldCount) This provides a count of matching failures and whether they would have been tagged as old or new without this patchset. This provides a quick way to know whether there is the same number of failures every time or whether the number of failures changes from one run to the next. It also provides a quick way to know how many failures to look for when jumping to the log. -- 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.

Oct. 6, 2022

[Bug 46392] Commandos: Behind Enemy Walls videos aren't played

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=46392 Benjamin Legendre <legendre.benjamin(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |legendre.benjamin(a)gmail.com --- Comment #13 from Benjamin Legendre <legendre.benjamin(a)gmail.com> --- @joaopa when you said "bug is fixed in 7.0), are you saying with or without DLL overrides? In my tests with wine 7.15 and 7.18, videos still doesn't play without amstream and quartz overrides (which i install using winetricks). As a side note, commando can't be installed with Wine 7.18 because of https://bugs.winehq.org/show_bug.cgi?id=53646 But works in 7.18 if installed using <= 7.15 -- 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.

Oct. 6, 2022

[Bug 53718] WoW Beta/PTR get "Your 3D accelorator card is not supported"

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53718 --- Comment #27 from nerzhul <loic.blot(a)unix-experience.fr> --- i didn't tested yet with all wine but i work again with Proton with this weekly build (proton-ge-custom 7.37), then as it was the worst situation compared to vanilla wine, i think it should re-work with all wine versions -- 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.

Oct. 6, 2022

[Bug 53759] FPGA Programmer can't open port

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=53759 Samega 7Cattac <7Cattac(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |7Cattac(a)gmail.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.

Oct. 6, 2022