March 2020 - Wine-bugs - list.winehq.org

[Bug 19122] New: MCI mciSendString with repeat as a play flag does not work
by wine-bugs＠winehq.org 30 Mar '20

30 Mar '20

http://bugs.winehq.org/show_bug.cgi?id=19122 Summary: MCI mciSendString with repeat as a play flag does not work Product: Wine Version: 1.1.24 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: emil.jo.andersson(a)gmail.com This works (plays once as expected): _stprintf(command, _T("open \"%s\" alias bgmusic"), szFileName); mciSendString(command, response, (UINT)_tcslen(response), NULL); _stprintf(command, _T("setaudio bgmusicvolume to %i"), settings.MusicVolume * 10); mciSendString(command, response, (UINT)_tcslen(response), NULL); mciSendString(_T("play bgmusic"), response, (UINT)_tcslen(response), NULL); This does not work (doesn't play at all): _stprintf(command, _T("open \"%s\" alias bgmusic"), szFileName); mciSendString(command, response, (UINT)_tcslen(response), NULL); _stprintf(command, _T("setaudio bgmusicvolume to %i"), settings.MusicVolume * 10); mciSendString(command, response, (UINT)_tcslen(response), NULL); mciSendString(_T("play bgmusic repeat"), response, (UINT)_tcslen(response), NULL); I've tried this both in a virtual machine (Virtualbox) and on a non-virtual machine. Both were running Ubuntu 9.04 with version 1.1.24 from the Wine repository. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 12

[Bug 46313] New: Zwift: Crash on startup
by wine-bugs＠winehq.org 29 Mar '20

29 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=46313 Bug ID: 46313 Summary: Zwift: Crash on startup Product: Wine Version: 4.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jamie.magee(a)gmail.com Distribution: --- Created attachment 63045 --> https://bugs.winehq.org/attachment.cgi?id=63045 Install and run attempt I'm trying to run Zwift [1] on wine 4.0-rc2. The minimum requirements [2] are Windows 7, 64-bit, and .NET Framework (Though I'm not 100% sure which version). I've attached my logs from installing ZwiftLauncher.exe in a 64-bit prefix with wine-mono, and subsequently trying to launch it. I've also (unsuccessfully) attempted some other setup attempts with the help of Bob Wya in the forums [3] if those logs are of any use. Please let me know if you need any more information. [1] https://cdn.zwift.com/app/ZwiftSetup.exe [2] https://support.zwift.com/en_us/what-are-the-minimum-device-requirements-fo… [3] https://forum.winehq.org/viewtopic.php?f=2&t=31589 -- 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 21

[Bug 33845] New: Can not update Warframe steam version
by wine-bugs＠winehq.org 29 Mar '20

29 Mar '20

http://bugs.winehq.org/show_bug.cgi?id=33845 Bug #: 33845 Summary: Can not update Warframe steam version Product: Wine Version: 1.6-rc2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: levanchelidze(a)gmail.com Classification: Unclassified So I tried to run Warframe steam version but sadly updating this game fails -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 52

[Bug 48849] New: FIXME logging can be omitted for supported cases of GetCurrentProcessorNumberEx
by WineHQ Bugzilla 29 Mar '20

29 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48849 Bug ID: 48849 Summary: FIXME logging can be omitted for supported cases of GetCurrentProcessorNumberEx Product: Wine Version: 5.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: perchrh-wine(a)pvv.org Distribution: --- Created attachment 66766 --> https://bugs.winehq.org/attachment.cgi?id=66766 Trivial patch A program that uses GetCurrentProcessorNumberEx frequently becomes very verbose under Wine. The reason is the FIXME(..) stub warning of this method in dlls/ntdll/rtl.c. This method is actually fully implemented for most cases, and the verbose message can be thus omitted, while keeping the warning for those cases where there actually is something missing in Wine's implementation. Specifically, this method is fully implemented for systems with less than 64 logical processors. API docs quote: "Processor groups are numbered starting with 0. Systems with fewer than 64 logical processors always have a single group, Group 0." Source: https://docs.microsoft.com/nb-no/windows/win32/procthread/processor-groups The attached patch implements the mentioned 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.

1 1

[Bug 48845] New: Black Mesa has graphics problems
by WineHQ Bugzilla 29 Mar '20

29 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48845 Bug ID: 48845 Summary: Black Mesa has graphics problems Product: Wine Version: 5.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dron2065(a)rambler.ru Distribution: --- There is no blured image at start and game menu at Black Mesa 1.0 Steam Version -- 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 0

[Bug 48830] New: I'm trying to run this game and it doesn't work,
by WineHQ Bugzilla 29 Mar '20

29 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48830 Bug ID: 48830 Summary: I'm trying to run this game and it doesn't work, Product: Wine Version: unspecified Hardware: arm OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: schneideroscar2(a)gmail.com Distribution: --- Created attachment 66747 --> https://bugs.winehq.org/attachment.cgi?id=66747 I don't understand code, promise you I don't. Trying to run this game and with several launchers, the first launcher says that I need steam to run it but when I have steam running it still doesn't work and the second one gives me this error. -- 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 48373] New: WriteProcessMemory? - Project Reality fails linking Launcher and Game Executable
by WineHQ Bugzilla 28 Mar '20

28 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48373 Bug ID: 48373 Summary: WriteProcessMemory? - Project Reality fails linking Launcher and Game Executable Product: Wine Version: 5.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: consolelogger(a)rhyta.com Distribution: --- When running Project Reality, past the game menu and the loading in, an error shows up where it says: "Failed linking to the Launcher" https://old.reddit.com/r/ProjectReality/comments/eg3xfu/lets_try_to_get_pr_… We have the luxury of being able to ask the devs about what might be going on there: "If he joined a server, the Launcher has succeeded in opening the process and writing to it. These sort of issues are usually an anti virus not liking this kind of cross-process communication. In your case wine is probably incapable of WriteProcessMemory [...] Wine has both ReadProcessMemory and WriteProcessMemory, not sure what exactly the issue is but it shouldn't be that unless an odd bug has been hit [...] I suspect that or PR is triggering an unandlhed edge case or the failure reason is actually another one." I was hoping to post a report with logs here, but couldn't find out what arguments are needed on WINEDEBUG= to have instances of ReadProcessMemory and WriteProcessMemory and adjacant "stuff" show up in the logs. How would I go about optaining a log that contains info helpful for solving this? I will do so as soon as I can and am happy to do testing and further research. Cheers. -- 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 7

[Bug 28884] New: keyboard input does not work properly for Sculptris
by wine-bugs＠winehq.org 28 Mar '20

28 Mar '20

http://bugs.winehq.org/show_bug.cgi?id=28884 Bug #: 28884 Summary: keyboard input does not work properly for Sculptris Product: Wine Version: 1.3.31 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: peter(a)light-bg.com Classification: Unclassified Created attachment 37113 --> http://bugs.winehq.org/attachment.cgi?id=37113 console output The application runs flawlessly while controlled with the mouse only or with a combination of keyboard and mouse input simultaneously. But upon pressing any button on the keyboard alone, with the only exception of the F* keys and the NumLock, the application freezes until focus is changed to another window and returned to the application window. After returning focus to the application window Sculptris continues to work as if no keyboard shortcut was pressed. The only exception to this are the square brackets and the numpad Del keys, which have the effect of increasing/decreasing the brush size. They too do freeze the app, but the brush is larger/smaller after returning to the app. No other keyboard shortcuts (most notably ctrl-z - undo) are not working. This makes the application unusable for serious work, because many things are controlled only via keyboard and are not present in the UI. There is nothing on the console, except the following three lines: --attached-- -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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 19

[Bug 48700] New: Wolcen: Lords of Mayhem - there's a blob around the character's head.
by WineHQ Bugzilla 28 Mar '20

28 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48700 Bug ID: 48700 Summary: Wolcen: Lords of Mayhem - there's a blob around the character's head. Product: Wine Version: 5.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mo78(a)abv.bg Distribution: --- Created attachment 66575 --> https://bugs.winehq.org/attachment.cgi?id=66575 Wolcen Lords of Mayhem Wine log There's an "afro" blob around the character's head. I tried different settings and different Wine versions, with or without DXVK to no avail. Please tell me what kind of logs do you need and I'll provide them. Thank you. https://i.imgur.com/0dhoxKt.png https://i.imgur.com/mTz2PPL.png https://i.imgur.com/525jisv.png https://i.imgur.com/zYObSAU.png https://i.imgur.com/qTXGVeu.png -- 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 26

[Bug 48667] New: full screen in games doesn't work
by WineHQ Bugzilla 28 Mar '20

28 Mar '20

https://bugs.winehq.org/show_bug.cgi?id=48667 Bug ID: 48667 Summary: full screen in games doesn't work Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gucio321(a)protonmail.com Distribution: --- Created attachment 66523 --> https://bugs.winehq.org/attachment.cgi?id=66523 output from terminal full screen mode does not work in several games (the game starts in a small area of the screen) the problem appeared after upgrading fedora 30 to fedora 31 (installing older wine does not help) -- 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