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

[Bug 47084] New: Call of Duty Black Ops 3 doesn't run because of mfplat
by wine-bugs＠winehq.org Jan. 12, 2023

Jan. 12, 2023

https://bugs.winehq.org/show_bug.cgi?id=47084 Bug ID: 47084 Summary: Call of Duty Black Ops 3 doesn't run because of mfplat Product: Wine Version: 4.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mfplat Assignee: wine-bugs(a)winehq.org Reporter: mo78(a)abv.bg Distribution: --- Created attachment 64278 --> https://bugs.winehq.org/attachment.cgi?id=64278 Call of Duty Black Ops 3 Wine log The game doesn't run due to lack of mfplat implementation. When started it warns for missing Windows Media Feature Pack: https://i.imgur.com/HCYDJYe.png When I prepare mfplat prefix in wich Shadows: Awakening runs just fine, Call of Duty Black Ops 3 actually starts and runs very well but it has the following problems: https://bugs.winehq.org/show_bug.cgi?id=45876 -- 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 32

[Bug 50326] New: (Regression) Playing movies broken in Ghostrunner
by WineHQ Bugzilla Jan. 12, 2023

Jan. 12, 2023

https://bugs.winehq.org/show_bug.cgi?id=50326 Bug ID: 50326 Summary: (Regression) Playing movies broken in Ghostrunner Product: Wine-staging Version: 6.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: peter-24(a)o2.pl CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 68910 --> https://bugs.winehq.org/attachment.cgi?id=68910 wine log Playing movies broken in Ghostrunner - none playing(skipped). Working in staging 6.0rc1. -- 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 27

[Bug 44204] New: Slingplayer 2.0 crashes on connect (dsound)
by wine-bugs＠winehq.org Jan. 12, 2023

Jan. 12, 2023

https://bugs.winehq.org/show_bug.cgi?id=44204 Bug ID: 44204 Summary: Slingplayer 2.0 crashes on connect (dsound) Product: Wine Version: 3.0-rc2 Hardware: x86 URL: http://download.slingmedia.com/player/pc/SlingPlayer_2 .0.4522_Setup-Global.exe OS: Linux Status: NEW Keywords: download Severity: minor Priority: P2 Component: directx-dsound Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Created attachment 59972 --> https://bugs.winehq.org/attachment.cgi?id=59972 Wine 3.0-rc2 console output SlingPlayer 2.0.4 crashes when starting the stream under Wine 3.0-rc2. This never used to occur but I haven't been able to complete a bisect. I will try again later but it is a very slow process as it appears that the application has to be fully installed with each test. The clue to the workaround comes from: 003d:trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\dsound.dll" at 0x731c0000: builtin wine: Unhandled illegal instruction at address 0x730073 (thread 003d), starting debugger... Native dsound (winetricks dsound) works around the crash. To get this far, the following overrides are needed: WINEARCH=win32 - Bug 35268 / Bug 35276 quartz - Bug 18556 wmp9 - Bug 28669 (wmp10 + dsound = another crash) mf - Bug 44201 Ignore the installer crash - Bug 17289 With the addition of native dsound, Slingplayer 2.0 can once again be used. -- 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 9

[Bug 43073] New: Cyrillic/ russian characters displays incorrectly in Final Fantasy XIV
by wine-bugs＠winehq.org Jan. 11, 2023

Jan. 11, 2023

https://bugs.winehq.org/show_bug.cgi?id=43073 Bug ID: 43073 Summary: Cyrillic/russian characters displays incorrectly in Final Fantasy XIV Product: Wine Version: 2.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mlang Assignee: wine-bugs(a)winehq.org Reporter: yonnji(a)miqote.com Distribution: --- Created attachment 58256 --> https://bugs.winehq.org/attachment.cgi?id=58256 launcher and UI screenshots Cyrillic/russian characters displays incorrectly in Final Fantasy XIV. It affects a game launcher, in-game UI, and a chat. It's impossible to play, when you can't talk with other people and can't read the chat. The text used as example in screenshots is "привет hello". -- 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 13

[Bug 45116] New: TomTom MyDrive Connect needs implementation of iphlpapi.dll.NotifyAddrChange
by wine-bugs＠winehq.org Jan. 11, 2023

Jan. 11, 2023

https://bugs.winehq.org/show_bug.cgi?id=45116 Bug ID: 45116 Summary: TomTom MyDrive Connect needs implementation of iphlpapi.dll.NotifyAddrChange Product: Wine Version: 3.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: iphlpapi Assignee: wine-bugs(a)winehq.org Reporter: h.mth(a)web.de Distribution: --- Follow up bugreport of bug 41034. Patches and backtraces(vanilla and staging) will be attached. Application crashes shortly after device is attached. To activate device (i.e.: TomTom Via 135), linux needs: CONFIG_USB_NET_CDCETHER=y Wine Staging 3.7 allows to login into TomTom account. -- 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 20

[Bug 11622] New: DejaVu X installation failing at start because of component not found
by wine-bugs＠winehq.org Jan. 10, 2023

Jan. 10, 2023

http://bugs.winehq.org/show_bug.cgi?id=11622 Summary: DejaVu X installation failing at start because of component not found Product: Wine Version: 0.9.55. Platform: HP URL: http://www.atril.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: yolande(a)haneder.biz Created an attachment (id=10825) --> (http://bugs.winehq.org/attachment.cgi?id=10825) log file I extracted the .exe file in the temp directory of Wine as instructed and launched the installation. The missing file is indeed not in the temp and I can't find it on the internet because of deprecated from Microsoft. -- 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 5

[Bug 29937] New: File selection dialog view shows Favorites when you click elsewhere
by wine-bugs＠winehq.org Jan. 10, 2023

Jan. 10, 2023

http://bugs.winehq.org/show_bug.cgi?id=29937 Bug #: 29937 Summary: File selection dialog view shows Favorites when you click elsewhere Product: Wine Version: 1.4-rc1 Platform: x86-64 URL: http://www.winuae.net/files/InstallWinUAE2330.exe OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: markk(a)clara.co.uk Classification: Unclassified There is a small issue with file selection dialogs which some programs use. When the dialog opens, it shows the files in some directory in the right pane, and a tree view of the directory hierarchy in the left pane. The tree view shows Favorites and Desktop (which is expanded to show My Computer, My Documents, Trash, /). If you then click on any of the + or - symbols in the tree view, the view in the right pane jumps to Favorites. For example, click the + next to My Computer and the view on the right changes to Favorites (which may be empty). The directory shown in the right pane should probably not change when the user clicks a + or - symbol in the left pane. WinUAE is one program which uses that type of file dialog. To show the problem, download and run the WinUAE installer, check the box to run the program at the end. When the WinUAE Properties window appears, click "Select image file" to open a file selection dialog. -- 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 8

[Bug 49882] New: Overdrive audio book app will not start. Worked fine in WINE version 5.0.1
by WineHQ Bugzilla Jan. 10, 2023

Jan. 10, 2023

https://bugs.winehq.org/show_bug.cgi?id=49882 Bug ID: 49882 Summary: Overdrive audio book app will not start. Worked fine in WINE version 5.0.1 Product: Wine Version: 5.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ben.miller.5150(a)gmail.com Distribution: --- Created attachment 68225 --> https://bugs.winehq.org/attachment.cgi?id=68225 backtrace.txt produced when Overdrive fails Overdrive app is no longer working in WINE 5.0.2. It has only stopped working since upgrading WINE from 5.0.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.

1 7

[Bug 51234] New: user32:clipboard test_ClipboardOwner() has a race condition with clipboard managers
by WineHQ Bugzilla Jan. 9, 2023

Jan. 9, 2023

https://bugs.winehq.org/show_bug.cgi?id=51234 Bug ID: 51234 Summary: user32:clipboard test_ClipboardOwner() has a race condition with clipboard managers Product: Wine Version: 6.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- test_ClipboardOwner() has a race condition with clipboard managers that causes this set of failures: clipboard.c:404: Test failed: SetClipboardData succeeded clipboard.c:406: Test failed: wrong error 3735928559 clipboard.c:407: Test failed: SetClipboardData succeeded Fortunately(?) this failure is pretty rare. What happens is this: * test_ClipboardOwner() does this: OpenClibpoard(NULL) EmptyClipboard() // take ownership CloseClipboard() * Then the clipboard manager starts checking the content of the clipboard: OpenClipboard(manager_hwnd) ... * And then the next test_ClipboardOwner() test happens: SetClipboardData(CF_WAVE, ...) ok(GetLastError() == ERROR_CLIPBOARD_NOT_OPEN, ...) ok(!IsClipboardFormatAvailable(CF_WAVE), ... Because test_ClipboardOwner() opened the clipboard with a NULL windows handle, EmptyClipboard() used that as the clipboard owner. But when the owner is NULL a process can place data in the clipboard as long as any process opened it. This is actually the whole point of the run_process("set_clipboard_data 4") test. So the problem is that user32:clipboard assumes that no other process is going to open the clipboard after it called CloseClipboard(). Yet that's precisely when clipboard manager would receive a WM_CLIPBOARDUPDATE message and open it. -- 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 48911] New: Check for compilation warnings
by WineHQ Bugzilla Jan. 9, 2023

Jan. 9, 2023

https://bugs.winehq.org/show_bug.cgi?id=48911 Bug ID: 48911 Summary: Check for compilation warnings Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Compiling Wine with -Werror is troublesome because it applies blindly to both wine-devel patches and patches submitted manually via the website. The sole purpose of the latter is often to just clarify some point for the development of another patch and are not meant to be submitted. Thus failing on warnings just makes running these quick tests more cumbersome. So the best way forward would be for the TestBot to identify and report warnings but not fail the compilation and abort the tests when they occur. So: 1. The builds should happen without -Werror. 2. GetLogLineCategory() should identify the warnings and add them to LogInfo but distinguish them from errors (replace IsNew with a Category field?). 3. Compare task.log to the reference build log to distinguish new warnings from old ones. This is necessary in case the compiler used by the TestBot produces warnings on the unpatched Wine tree. It will require storing the build logs in latest/ just like the TestBot already does for the reference WineTest reports. 4. LogInfo's will need to keep track of the number of new warnings which really means renaming the 'NewCount' field to avoid confusion. 5. The warnings should be saved in the errors files. The new line types could be 'w' and 'W' for old and new warnings respectively (then it would make sense to use e and E for errors). 6. This will let the WineRun*() scripts know about both warnings and errors. They can then decide what to do depending on the type of job and whether the warnings are new or not. - Old warnings would always be ignored. - If a build task has new warnings, instead of marking it as 'badbuild' it could be marked as 'completed' as usual but with a non-zero number of failures. This would probably allow running the tests on Windows but the patch would still be considered bad since the job would end up with a non-zero number of failures. - For Wine tasks the number of warnings would be added to the Failures field for the same overall result. - So in both cases the non-zero number of failures would only impact wine-devel patches. 7. The JobDetails page should show the warnings in summary mode and highlight them in the full build log. That would make it easy for developers to see the warnings on web-submitted jobs, and thus fix them before submitting the patch to wine-devel. -- 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 2