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

[Bug 230] winemaker: Extract more information from the source files
by wine-bugs＠winehq.org July 11, 2019

July 11, 2019

https://bugs.winehq.org/show_bug.cgi?id=230 tomplatz <tomplatz567(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomplatz567(a)gmail.com --- Comment #18 from tomplatz <tomplatz567(a)gmail.com> --- Created attachment 64885 --> https://bugs.winehq.org/attachment.cgi?id=64885 132 -- 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 47488] New: Keyboard insertion point interference when running Wine app
by wine-bugs＠winehq.org July 9, 2019

July 9, 2019

https://bugs.winehq.org/show_bug.cgi?id=47488 Bug ID: 47488 Summary: Keyboard insertion point interference when running Wine app Product: Wine Version: 4.0.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: scw189(a)cox.net Distribution: --- When running a Wine app (Legacy9, genealogy program) in the background and then trying to type anything with a word processor or do a Google search, it is difficult to enter text because the insertion point character keeps disappearing after 2-5 second. Then you have to click again in the text field to reset the insertion point and try to type a few characters before it disappears again. This issue stops as soon as the Wine application is terminated. Mouse operation does not seem to be affected, just keyboard character input is impaired because the insertion point is continually being lost. Cannot find any messages or error codes being asserted and system does not 'crash'. OS is Linux Mint 19.1 Cinnamon with all updates applied. Computer is Dell Dimension E521 with 64bit dual core Athlon CPU, 6gb memory. -- 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 3

[Bug 29499] New: Age of Empires II freezes when disconnecting from a multiplayer room/game using native DirectPlay DLL
by wine-bugs＠winehq.org July 9, 2019

July 9, 2019

http://bugs.winehq.org/show_bug.cgi?id=29499 Bug #: 29499 Summary: Age of Empires II freezes when disconnecting from a multiplayer room/game using native DirectPlay DLL Product: Wine Version: 1.3.36 Platform: x86-64 URL: http://download.cnet.com/Age-of-Empires-II-Trial-Versi on/3000-2099_4-10725533.html OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dplay AssignedTo: wine-bugs(a)winehq.org ReportedBy: lapommegolden(a)gmail.com Classification: Unclassified Created attachment 38200 --> http://bugs.winehq.org/attachment.cgi?id=38200 wine log (1.3.36) STEPS TO REPRODUCE THE BUG: 1. Download & Install Age of Empires II Trial: - http://download.cnet.com/Age-of-Empires-II-Trial-Version/3000-2099_4-107255… OR - http://download.microsoft.com/download/aoeaok/Trial/1.0/WIN98/EN-US/AoE2dem… 2. Install "directplay" from winetricks 3. Launch AOE II (You may need to set DirectDrawRenderer to gdi if opengl renderer fails on some platforms, which is another bug: http://bugs.winehq.org/show_bug.cgi?id=29261) http://wiki.winehq.org/UsefulRegistryKeys 4. Attempt to start a multiplayer game (Internet TCP/IP) 5. Click CANCEL now to try to disconnect from a multiplayer room but AOE II will now freeze even the game did not even ever get started. -- 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.

1 40

[Bug 5977] Animations in the menus of Star Trek: Armada do not work
by wine-bugs＠winehq.org July 8, 2019

July 8, 2019

https://bugs.winehq.org/show_bug.cgi?id=5977 Lewis Cowles <lewiscowles(a)me.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lewiscowles(a)me.com --- Comment #32 from Lewis Cowles <lewiscowles(a)me.com> --- To Echo what winetest(a)luukku said, I adjusted the resolution to 800x600x32 in Armada, which led to seeing some the texture for the animation When hovering. This is absolutely an issue with draw order, but enabling "fixes" I assumed would counter this, did nothing useful, and in-fact made the game unusable. Debian 10 buster, winetricks, wine 1386, Quicktime 3 & DX from armada installer installed, directplay activated, virtual desktop forced to 1024x768 (game seems to ignore & go fullscreen) Also needs to be launched from launcher. Game won't run by itself. Odd -- 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 46170] New: Programs that get MIDI data from the "Midi Through" port will crash
by wine-bugs＠winehq.org July 8, 2019

July 8, 2019

https://bugs.winehq.org/show_bug.cgi?id=46170 Bug ID: 46170 Summary: Programs that get MIDI data from the "Midi Through" port will crash Product: Wine Version: 3.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: realnc(a)gmail.com Distribution: --- Created attachment 62822 --> https://bugs.winehq.org/attachment.cgi?id=62822 Example MIDI file that reproduces the crash. Any Windows software that is configured to use the ALSA "Midi Through" port for MIDI input (as provided by the snd-seq-dummy kernel module) will crash with a page fault exception dialog. This only happens with certain MIDI data. It seems to depend on the speed of the MIDI data. The issue was originally discovered by using the Linux version of ScummVM together with the Windows program "Falcosoft Midiplayer" as a means of using a Windows-only VSTi as a software MIDI synth for ScummVM. In such a setup, the Linux program is configured to use the "Midi Through" port as MIDI-out, and the Windows program is configured to use it as MIDI-in. However, after capturing the specific MIDI data that triggers the crash into a *.mid file, playing that file in any MIDI player that uses "Midi Through" for MIDI-out and *any* Windows MIDI program that uses "Midi Through" as MIDI-in, will crash the Windows program. The problem is reproducible by at least two people on two different machines. It is reproducible by building current Wine Git master, without any third-party patches, and on a cleared ~/.wine directory. Example steps to reproduce this are: 1. Make sure the "Midi Through" port is available. aplaymidi -l should list something like: $ aplaymidi -l Port Client name Port name 14:0 Midi Through Midi Through Port-0 "Midi Through" is port 14:0 here. If no such port exists, load the "snd-seq-dummy" kernel module: $ modprobe snd-seq-dummy 2. Download the attached "crash.mid" file. 3. Download the Falcosoft Midiplayer from: http://falcosoft.hu/softwares.html#midiplayer 4. Run MidiPlayer.exe in Wine and click the gear icon to open the settings. Check the "Use Bass (Soundfonts/VSTi)" checkbox (this is only necessary in order to avoid an unrelated Wine crash.) In the "Midi In" group, check the "Active" checkbox. In the "Input Port" drop-down selection list, select "Midi Through Port-0". Click OK. 5. Play the "crash.mid" file using a Linux MIDI player, like aplaymidi, telling it to use the Midi Through port as output: $ aplaymidi -p 14 crash.mid Substitute "14" with the actual port if it differs on your system. It might take a few attempts before the crash occurs. Here, it crashes about 80% of the time. The above steps are just an example. The crash is reproducible with any other Windows MIDI client, not just the Falcosoft one. See: https://www.vogons.org/viewtopic.php?f=24&t=48207&start=760#p714667 -- 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 23

[Bug 47458] New: Sleeping while pthreads mutex held from the driver code in winepulse-PulseAudio_Support
by wine-bugs＠winehq.org July 8, 2019

July 8, 2019

https://bugs.winehq.org/show_bug.cgi?id=47458 Bug ID: 47458 Summary: Sleeping while pthreads mutex held from the driver code in winepulse-PulseAudio_Support Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bill.huey(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- The SetEvent call in the function pulse_timer_cb() sleeps, calls into the wineserver, while a pthread mutex is held. This can cause long delays in releasing the "pulse_lock" mutex, anywhere from 1-2ms to 90ms that I can see with my custom instrumentation. It potentially can cause dropouts and other issues with audio handling. It seems to be in the main core audio processing loop. The general practice here is to avoid sleeping operations within critical sections. -- 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 6

[Bug 47160] New: wine-staging is unable to execute executable which is soft link in linux.
by wine-bugs＠winehq.org July 8, 2019

July 8, 2019

https://bugs.winehq.org/show_bug.cgi?id=47160 Bug ID: 47160 Summary: wine-staging is unable to execute executable which is soft link in linux. Product: Wine-staging Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l12436(a)yahoo.com.tw CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Since recently wine-staging version, wine-staging is no longer able to successful recognize soft link directory or executable. I have many directory is soft link to save disk space. I can not found which patch cause this issue. -- 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 45

[Bug 47319] New: Wine 4.9 does not dereference symlinks
by wine-bugs＠winehq.org July 8, 2019

July 8, 2019

https://bugs.winehq.org/show_bug.cgi?id=47319 Bug ID: 47319 Summary: Wine 4.9 does not dereference symlinks Product: Wine-staging Version: 4.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kanakkshetri(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- I have a symbolic link ~/Audio/hello.flac that is pointing /mnt/audio/hello.flac . I have also set ~/Audio to be Y: in wine. Prior to the 4.9 release, windows applications, such as Wine File Manager or foobar2000 version 1.4.4 ( http://foobar2000.org) would dereference that symlink and see that it is a 30Mb file that is a valid flac audio file. With 4.9, file manager shows the size as 0 and foobar2000 cannot read the file at all. I am on Fedora 30, where a dnf downgrade took me back to 4.5-1, where this works as expected. I have verified this on two different machines, using Wine File Manager as well as foobar2000. I have also seen the same behavior in Fedora 29 (with Wine 4.9), so I don't think it is OS specific. Additional context: - my data is on an XFS file system - the symlinks are present because the data is managed by git annex ( https://git-annex.branchable.com/ ) - However, i can repro the problem without involving git annex merely by creating symlinks. Please let me know if there is any additional details I can provide or experiments I can run locally. Thank you for the great work on wine. -- 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 47472] New: aarch64 compile fails with 4.12 rebase in setupapi patch
by wine-bugs＠winehq.org July 8, 2019

July 8, 2019

https://bugs.winehq.org/show_bug.cgi?id=47472 Bug ID: 47472 Summary: aarch64 compile fails with 4.12 rebase in setupapi patch Product: Wine-staging Version: 4.12 Hardware: aarch64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mike(a)cchtml.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- https://github.com/wine-staging/wine-staging/commit/eba1e9b28a07fea4f823346… The move from snprintfW() to snwprintf() causes the aarch64 compile to fail. /usr/bin/ld: dialog.o: in function `SetupPromptForDiskW':/builddir/build/BUILD/wine-4.12/dlls/setupapi/dialog.c:252: undefined reference to `snwprintf' clang-8: error: linker command failed with exit code 1 (use -v to see invocation) winegcc: /usr/bin/clang failed make[1]: *** [Makefile:500: setupapi.dll.so] Error 2 make: *** [Makefile:8350: dlls/setupapi] Error 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.

1 3

[Bug 47346] New: [Epic Games Launcher]Crashes when Winecfg is set to Win10
by wine-bugs＠winehq.org July 8, 2019

July 8, 2019

https://bugs.winehq.org/show_bug.cgi?id=47346 Bug ID: 47346 Summary: [Epic Games Launcher]Crashes when Winecfg is set to Win10 Product: Wine-staging Version: 4.9 Hardware: x86 URL: https://epicgames-download1.akamaized.net/Builds/Unrea lEngineLauncher/Installers/Win32/EpicInstaller-9.13.0. msi?launcherfilename=EpicInstaller-9.13.0.msi OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: Gentoo Hello, Bug easy to reproduce : 1- Download EGS 2- Install Arial fonts with winetricks 3- Install EGS and wait the update crash. 4- Launch EGS with "-SkipBuildPatchPrereq -opengl" arguments + Win7/Win8/Win8.1 = works 5- Launch EGS with "-SkipBuildPatchPrereq -opengl" arguments + Win10 = crashes With Win7 and/or Win10, the login screen works correctly, it's the launcher itself which does not work with Win10, see screenshots attachment. I added output log for Win7 + Win10 too. -- 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