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

[Bug 49599] eventfd-synchronization causes audio glitches in cutscenes in Assassin's Creed Odyssey

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49599 masush755(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |masush755(a)gmail.com --- Comment #3 from masush755(a)gmail.com --- I recorded logs with and without esync and +sync,+esync,+server,+timestamp,+pid with the uplay version of the game and plain wine-staging 5.7: no esync: https://drive.google.com/file/d/1vXZDXtytXJx0Q_OsAq7Q2Eu8mLKbzN0u/view?usp=… esync: https://drive.google.com/file/d/1SdTS5Zmc-2G-_-wtJMYkYZVeuAbV20_C/view?usp=… -- 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, 2020

[Bug 35254] Freemake Video Converter 4.1 installer complains about running Freemake processes (builtin 'findstr' stub app always returns "match")

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=35254 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com --- Comment #8 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- Created attachment 67830 --> https://bugs.winehq.org/attachment.cgi?id=67830 patch Attached a patch which is really copy/paste from find.exe. I only added some code to break up search pattern like "foo | bar" into seperate "foo" and "bar", and print fixme for any given option "/*" (Note: this seems to be a bug in find.exe; giving an option is not invalid... afaict) So with this patch it gives: wine cmd /c echo "foo bar" \| findstr.exe "fo_o | bar" "foo bar" wine cmd /c echo "foo bar" \| findstr.exe "fo_o | ba_r " (no match) Maybe for the time being could this be added to Staging to see if it does not cause any regressions? -- 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, 2020

[Bug 49515] Star Wars: The Old Republic unable to patch on Debian but works on Mint

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49515 --- Comment #38 from SwampRabbit <mx.linux.gamer(a)gmail.com> --- I just want to thank everyone involved with this. Truly amazing amount of "extra mile" effort put into providing a short term solution, figuring ways to identify such issues in the future, and helping to resolve the root cause of the issue for everyone all around. I finally got around to installing all the certs listed and sure enough on MX Linux 19.2 (Debian 10) SWTOR on Steam using Proton gets passed the errors and starts downloading and installing everything for the game. We (MX Linux) have had a user who has wanted to play this game with his son for quite awhile and it looks like he should be able to now thanks to your efforts. Really great work, keep it up, thanks again! SwampRabbit (MX Linux Dev Team) -- 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, 2020

[Bug 49437] Segmentation fault (core dumped) even on winecfg or wineconsole on FreeBSD

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49437 --- Comment #8 from Damjan Jovanovic <damjan.jov(a)gmail.com> --- (In reply to Sean C. Farley from comment #5) > Created attachment 67808 [details] > ktrace of winecfg execution > > I am running 12.1-STABLE r363031 amd64 (r363017 was the last commit within > the tree I am running). This has the patch you submitted to FreeBSD for > #49139. > > Wine was built from ports in an i386 jail using an edited > emulators/i386-wine-devel port to build later versions than currently in > ports for it. It only uses two patches from the emulators/wine-devel port > located here: > https://svnweb.freebsd.org/ports/head/emulators/wine-devel/files/ The only > patch that affects the run of Wine would be patch-dlls_kernel32_Makefile.in. > > This is the only difference between my running system and changes to > anything within libexec/rtld-elf: > https://svnweb.freebsd.org/base/stable/12/libexec/rtld-elf/rtld. > c?r1=363372&r2=363371&pathrev=363372 > > I am attaching the failure at the end of a ktrace when attempting to run > winecfg. There is an "mmap -1 errno 22 Invalid argument" right before > opening ntdll.dll.so. Interestingly, the first ktrace showed > code=SEGV_MAPERR while all other runs (at least 20) showed code=SEGV_ACCERR. > This might be something: 56486 wine CALL mmap(0,0x1000,0<PROT_NONE>,0x1012<MAP_PRIVATE|MAP_FIXED|MAP_ANON>,0xffffffff,0,0) 56486 wine RET mmap -1 errno 22 Invalid argument I can't find such a line in my own ktrace, and MAP_FIXED shouldn't really be getting used much on FreeBSD without MAP_EXCL. > Just checking, are you testing amd64, i386 or i386 on amd64? I had just > noticed that Adrien, who opened this issue, had labeled the hardware as > x86-64 (amd64), so something may be amiss with my setup compared to his. i386 on amd64 -- 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, 2020

[Bug 49437] Segmentation fault (core dumped) even on winecfg or wineconsole on FreeBSD

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49437 --- Comment #7 from Damjan Jovanovic <damjan.jov(a)gmail.com> --- (In reply to Adrien Fernandes from comment #6) > My actual FreeBSD is this one : > FreeBSD 13.0-CURRENT #0 r362292: Thu Jun 18 04:59:33 UTC 2020 amd64 > CURRENT's rtld-elf's behavior changed, so if you run CURRENT, please make sure it's recent enough. This command has to print something; if not, you may on the "bad" patch of CURRENT when Wine mistranslated load addresses (as it had no way to tell what type of address rtld-elf used): nm -D /libexec/ld-elf.so.1 | grep _rtld_version_laddr_offset (This is not an issue for pre-CURRENT versions, despite returning no output.) > I didn't update FreeBSD yet. Still having the same issue on wine-5.13. > > I build wine using a i386 chrooted environment, not building through ports > BUT still applying manually the patches from emulator/wine-devel. > > It builds fine, installs as well but still the same Segmentation fault on > 5-13. So I should update FreeBSD if I want to use >wine-5.8 ? Other than that I am really not sure. Your best bet is probably to "git bisect", but there could be several working and half-working versions in between. I can try provide a change timeline and some specific commits to try, which might give us some preliminary answers? -- 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, 2020

[Bug 49626] ntdll can be loaded multiple times into the same process

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49626 --- Comment #4 from Jactry Zeng <jactry92(a)gmail.com> --- Is this fixed by https://source.winehq.org/git/wine.git/?a=commit;h=b7e51a1653320d06a9c04f53… ? -- 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, 2020

[Bug 49636] Wine does not fill in Vulkan device LUID for more than 1 GPU

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49636 Alexandr Oleynikov <sashok.olen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |loothelion(a)nvidia.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, 2020

[Bug 49636] Wine does not fill in Vulkan device LUID for more than 1 GPU

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49636 Alexandr Oleynikov <sashok.olen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzhang(a)codeweavers.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, 2020

[Bug 49636] New: Wine does not fill in Vulkan device LUID for more than 1 GPU

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49636 Bug ID: 49636 Summary: Wine does not fill in Vulkan device LUID for more than 1 GPU Product: Wine Version: 5.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winevulkan Assignee: wine-bugs(a)winehq.org Reporter: sashok.olen(a)gmail.com Distribution: Mint Created attachment 67829 --> https://bugs.winehq.org/attachment.cgi?id=67829 vulkan_tests_results Hi. When running the Wine's Vulkan test, I've encountered some failures when running on a machine with dual graphics. They appear to be caused by Wine not filling device LUIDs for the discrete GPU, only the primary integrated (Intel) one. This happens even if you set preference for the discrete GPU and filter out other GPUs with some envars (__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only). This causes an issue in World War Z, as it requires device LUID to be filled, and falls back to its inferior DX11 renderer if the LUID is zero-ed out. I've attached a text file with output from the vulkan test running with different combinations of these filtering envars and with none of them. I should note that this is not related to bug 49631, these tests were done on a different machine and during the tests for this bug report virtual desktop was disabled. -- 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, 2020

[Bug 49626] ntdll can be loaded multiple times into the same process

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49626 --- Comment #3 from Esme Povirk <madewokherd(a)gmail.com> --- It seems like loading c:\ntdll.dll actually did succeed earlier, but it returned the same handle already in the process. -- 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, 2020