September 2019 - Wine-bugs - list.winehq.org

[Bug 46616] New: ABBYY FineReader 14 crashes during installation
by wine-bugs＠winehq.org 26 Apr '20

26 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=46616 Bug ID: 46616 Summary: ABBYY FineReader 14 crashes during installation Product: Wine Version: 4.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tinywrkbee(a)gmail.com Distribution: --- Created attachment 63517 --> https://bugs.winehq.org/attachment.cgi?id=63517 ABBYY FineReader 14 default output App: ABBYY FineReader 14, trial version, can be dowloaded freely from https://www.abbyy.com/en-ee/lp/ee-finereader14-download-free-trial/ Wine: Wine: 4.1, WINEARCH=win32, Window 7, winetricks riched20. Behavior: Crashing during installation. Steps to reproduce: Maybe not necessary but I chose the custom installation and disabled everything except the base application. Also, I unchecked the option to download updates and every other option in the same screen. Logs: I'm attaching two logs. One with the default output and the second with WINEDEBUG=+winspool,+localspl,+ntdll,+msi. Be aware the second log size when extracted is 65MB. -- 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 46863] New: If prefix contains "windows" drive information not available in 64-bit prefix
by wine-bugs＠winehq.org 26 Apr '20

26 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=46863 Bug ID: 46863 Summary: If prefix contains "windows" drive information not available in 64-bit prefix Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: darktjm(a)gmail.com Distribution: --- All of my wine prefixes contain a path element called "windows" (actually, I use c:\windows, always). When I try to run installers or anything else that wants drive information, I get weird errors, starting with "Could not find DOS drive for current working directory" and usually ending with installer failures such as "The drive or UNC share you selected does not exist or is not accessible". Usually 64-bit games work fine once I figure out a way to install them anyway, such as direct extraction or 32-bit installs moved over. I think I have traced it to dlls/ntdll/directory.c:lookup_unix_name. If the full unix path has "windows" in it, and redirects are possible (true for 64-bit), the stat is skipped. However, if name_len is 0, it assumes immediately after that the stat took place, and exits with an error ("drive root doesn't exist"). To fix, I changed the redirect test to add !name_len (line 2641 in 4.4): if(!redirect || !name_len || (!strstr(.... A better fix might be to ignore "windows" if it's part of WINEPREFIX, so that the longer version of the search isn't always necessary. Since I don't know the code, I don't know how to skip over WINEPREFIX easily. With this fix, I can finally run installers in 64-bit prefixes, at least. This bug has plagued me since I first got 64-bit prefixes working at all for myself, so around 2.0 or earlier. I only now got around to looking into it because a particular game requires a particular 3rd party installer to work in 64-bit mode, so my usual tricks don't cut it any more. -- 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 10

[Bug 39847] New: Installation ABBYY Aligner2
by wine-bugs＠winehq.org 25 Apr '20

25 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=39847 Bug ID: 39847 Summary: Installation ABBYY Aligner2 Product: Wine Version: 1.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: msrom(a)mail.ru Distribution: --- Created attachment 53196 --> https://bugs.winehq.org/attachment.cgi?id=53196 log Cannot install application ABBYY Aligner2 -- 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 6

[Bug 44077] New: Overwatch: Within the first minute of game play the entire OS stops rendering ( requires hard reboot)
by wine-bugs＠winehq.org 25 Apr '20

25 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=44077 Bug ID: 44077 Summary: Overwatch: Within the first minute of game play the entire OS stops rendering (requires hard reboot) Product: Wine-staging Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sander.smid(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- wine-2.21 (Staging) Linux oribi 4.13.12-1-ARCH #1 SMP PREEMPT Wed Nov 8 11:54:06 CET 2017 x86_64 GNU/Linux Graphics: Card: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] Display Server: x11 (X.Org 1.19.5 ) drivers: nvidia (unloaded: modesetting,fbdev,nv,vesa,nouveau) Resolution: 1920x1200(a)59.95hz OpenGL: renderer: AMD Radeon RX 480 Graphics (AMD POLARIS10 / DRM 3.18.0 / 4.13.12-1-ARCH, LLVM 5.0.0) version: 4.5 Mesa 17.2.5 env WINEPREFIX="/games/BattleNet" /usr/bin/wine /games/BattleNet/drive_c/Program\ Files\ \(x86\)/Overwatch/Overwatch.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.

2 28

[Bug 45899] New: Tray icons don' t react when you left click or right click on them
by wine-bugs＠winehq.org 25 Apr '20

25 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=45899 Bug ID: 45899 Summary: Tray icons don't react when you left click or right click on them Product: Wine-staging Version: 3.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: guih.rox(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- All programs with a tray icon that I've tested so far with Wine Staging 3.16 don't work when you try to interact with it, by trying to left or right clicking on it. This is not reproducible with Vanilla Wine however. There's a small program called TurnFlash (https://www.nirsoft.net/utils/tflash2.html) that can be used to observe this behavior: Download link: https://www.nirsoft.net/utils/tflash210.zip SHA-1 sum for tflash.exe: 15f877867b45d51a2a8257494bb3128f1b0d087f After you run it, you should get no output from wine, but you'll see a blue icon added to the system tray of your Desktop Environment (in my case, it's KDE Plasma 5.13.5). The first thing I tried was checking checked my journal using `journalctl -f`, this is the message I got: Sep 27 03:22:06 arch plasmashell[970]: QQuickItem::stackAfter: Cannot stack StatusNotifierItem_QMLTYPE_345(0x558c6fb48b50, parent=0x558c6caa47b0, geometry=0,0 0x0) after StatusNotifierItem_QMLTYPE_345(0x558c6f972d20), which must be a sibling After that, I tried left clicking the tray icon -- it did nothing at all, and no logs. But right clicking it made the following message show up in the journal: Sep 27 03:24:36 arch plasmashell[970]: Could not find DBusMenu interface, falling back to calling ContextMenu() I should mention that I get the exact same messages using Vanilla Wine, the only difference is that interacting with the tray icon works perfectly fine. -- 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 33

[Bug 45291] New: Dauntless Open Beta : Cant play Intro Video resulting in not responding black screen
by wine-bugs＠winehq.org 25 Apr '20

25 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=45291 Bug ID: 45291 Summary: Dauntless Open Beta : Cant play Intro Video resulting in not responding black screen Product: Wine Version: 3.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winegstreamer Assignee: wine-bugs(a)winehq.org Reporter: asembus(a)gmail.com Distribution: --- Tried to test the open beta version for dauntless with addtional dotnet installation. the launcher works fine but when the game start it doesnt show intro video and ends up with black screen. i've read the log and it seems the error is caused when the video cannot be shown [2018-06-02T11:11:33,434][ 0][LogMediaUtils][Error]Cannot play file://../../../Archon/Content/MoviesPackaged/MediaExample.mp4, because none of the enabled media player plug-ins support 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.

2 6

[Bug 44089] New: Strider crashes after loading screen
by wine-bugs＠winehq.org 25 Apr '20

25 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=44089 Bug ID: 44089 Summary: Strider crashes after loading screen Product: Wine Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: strider(a)strycore.com Distribution: --- Created attachment 59805 --> https://bugs.winehq.org/attachment.cgi?id=59805 backtrace of the crash While the main menu works fine, when starting a game, the game crashes. This is a regression that started in Wine Staging 2.16, when the deferred context patch (https://dev.wine-staging.com/patches/181/) was introduced. I had a build of Wine Staging 2.15 with that patch enabled and I noticed crashes starting with that build and onward until the latest tested, Staging 2.21. -- 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 10

[Bug 46790] New: Witcher 3 hangs shortly after launch; may show ' press space to skip'
by wine-bugs＠winehq.org 25 Apr '20

25 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=46790 Bug ID: 46790 Summary: Witcher 3 hangs shortly after launch; may show 'press space to skip' Product: Wine-staging Version: 4.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: riddervancocagne(a)hotmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 63809 --> https://bugs.winehq.org/attachment.cgi?id=63809 Zip file containing api trace, partial console output and Witcher 3 crash report. If The Witcher 3 is launched using Wine 4.3 Staging, it will grind to a halt almost immediately. This is no ordinary black screen, as the game often does display the text 'Press space to skip'. Pressing space has no effect, however. I have also tried running the game on Wine 3.03 Stable, Wine 4.0 Stable and Wine 4.3 Devel. All three variants launch and run the game. Attached: partial console output, api trace and Witcher 3 crash report generated by the game itself. -- 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 47365] New: jittering caused by mouse input in vkquake
by wine-bugs＠winehq.org 24 Apr '20

24 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=47365 Bug ID: 47365 Summary: jittering caused by mouse input in vkquake Product: Wine Version: 4.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tempel.julian(a)gmail.com Distribution: --- Created attachment 64704 --> https://bugs.winehq.org/attachment.cgi?id=64704 wine log In vkquake, enable vsync (and set an fps limit well above refresh rate via "host_maxfps" command if your using a refreshrate of greater than 60Hz, as the game caps to 72fps by default), start a new game and pan the camera via the keyboard's arrow keys. It should be absolutely smooth. Now, pan the camera by moving the mouse instead -> there is jitter. After alt + Tab to the desktop and back into the game, this jitter usually is gone. Still, it shouldn't occur in the first place, as it doesn't happen on Windows. I made sure this isn't a driver issue by checking with both modesetting and xf86-video-amdgpu DDX and also on xwayland. In xwayland, the issue is less distinct, but still noticeable. Happens with both wine 4.9, wine-staging 4.9 and my custom 4.10 build (4.10 not yet in Arch repository). Get vkquake here: https://github.com/Novum/vkQuake/releases/download/1.01.0/vkquake-1.01.0_wi… You also need the game's free demo content, copy the "id1" folder into the main folder. Since the official servers usually are a mess, you can get it from here as well: https://bugs.freedesktop.org/attachment.cgi?id=143128 -- 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 6

[Bug 46633] New: unimplemented function: kernel32.dll.startthreadpoolio
by wine-bugs＠winehq.org 24 Apr '20

24 Apr '20

https://bugs.winehq.org/show_bug.cgi?id=46633 Bug ID: 46633 Summary: unimplemented function: kernel32.dll.startthreadpoolio Product: Wine Version: 4.0-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: mushipao(a)gmail.com Distribution: --- Created attachment 63542 --> https://bugs.winehq.org/attachment.cgi?id=63542 backtrace of exception 3rd party, proprietary software errors out in Wine. 0157:fixme:thread:CreateThreadpoolIo (0x64, 0x42fca0, 0x5fc2a0, (nil)): stub wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Call from 0x7bc51e39 to unimplemented function KERNEL32.dll.StartThreadpoolIo, aborting wine: Unimplemented function KERNEL32.dll.StartThreadpoolIo called at address 0x7bc51e39 (thread 0157), starting debugger... -- 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 18