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

[Bug 47834] New: Borderlands 1 (version 1.5.0) doesn't capture mouse
by WineHQ Bugzilla 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47834 Bug ID: 47834 Summary: Borderlands 1 (version 1.5.0) doesn't capture mouse Product: Wine-staging Version: 4.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dron2065(a)rambler.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Borderlands 1 (version 1.5.0) doesn't capture mouse - full 360 degree view with mouse is not possible. There is no this problem at previous version of Wine Staging (4.16) and Wine Devel of last version (4.17) -- 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 16

[Bug 42988] New: Pocket Mirror causes heavy flickering in fullscreen mode on wine-staging
by wine-bugs＠winehq.org 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=42988 Bug ID: 42988 Summary: Pocket Mirror causes heavy flickering in fullscreen mode on wine-staging Product: Wine-staging Version: 2.7 Hardware: x86 URL: http://astralshiftpro.tumblr.com/pocket-mirror OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: ArchLinux Created attachment 58125 --> https://bugs.winehq.org/attachment.cgi?id=58125 short video of the issue Running the game Pocket Mirror in fullscreen leads on wine-staging to heavy flickering. About once or twice each second the desktop or some other image from the game is partially visible through the game. However, the issue does not appear in vanilla wine 2.7 I tried to make an apitrace, but it only shows a single frame, so there's something wrong there, too. If you need more info please tell me, I'd make a bisect but I don't know how to apply the staging patches partially since a lot of them depend on each other. Using Arch Linux with KDE 5.9.5-1, running 32bit wine program on 64bit OS. Game URL: http://astralshiftpro.tumblr.com/pocket-mirror Direct download: http://t.umblr.com/redirect?z=https%3A%2F%2Fmega.nz%2F%23%214YBSWIKb%21nbjS… -- 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 47687] New: fail to run winrar installer
by wine-bugs＠winehq.org 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47687 Bug ID: 47687 Summary: fail to run winrar installer Product: Wine-staging Version: 4.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: b1779506(a)trbvn.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Download url: https://www.win-rar.com/download.html?&L=0 -- 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 11

[Bug 48063] New: World of Warcraft, Game Initialization fails, when run from command line
by WineHQ Bugzilla 23 Jan '20

23 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=48063 Bug ID: 48063 Summary: World of Warcraft, Game Initialization fails, when run from command line Product: Wine-staging Version: 4.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: eaglecomputers.ok(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- wine-4.19-158-g88d30985dd (Staging) is the version I just pulled from the git, and compiled. the previous commit that I have is wine-4.19-85-g7f469b689a (Staging) and it worked fine. Hope this helps you start regression testing. -- 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 43250] New: PerfectTUNES cannot access network
by wine-bugs＠winehq.org 22 Jan '20

22 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=43250 Bug ID: 43250 Summary: PerfectTUNES cannot access network Product: Wine Version: 2.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rixasha(a)yahoo.com Distribution: --- Created attachment 58561 --> https://bugs.winehq.org/attachment.cgi?id=58561 running AlbumArt.exe and AccurateRip.exe with +wininet,+winsock PerfectTUNES is set of programs to edit audio metadata on a music collection. Its network features - looking for album art on the internet and the checking of the files against the accuraterip database - do not work. The interfaces report "Could not connect" and "No Art Found". A feature-crippled trial version of PerfectTUNES is available that exhibits the network problems. According to the author the network code does nothing special and the only dependency is winsock. Curiously the related dBpoweramp software does find album arts and has no problems accessing accuraterip. Attaching logs with WINEDEBUG="+wininet,+winsock" made running AlbumArt.exe and AccurateRip.exe with wine-2.11 in a clean WINEPREFIX with just mono, gecko and PerfectTUNES-Unregistered, and one album in My Music. An outside reference: https://forum.dbpoweramp.com/showthread.php?37601-Bug-with-PerfectTunes-und… -- 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 47430] New: RT Se7en Lite installer fails to {modify,repair, remove} product after successful installation, reporting 'Function failed. '
by wine-bugs＠winehq.org 22 Jan '20

22 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47430 Bug ID: 47430 Summary: RT Se7en Lite installer fails to {modify,repair,remove} product after successful installation, reporting 'Function failed.' Product: Wine Version: 4.11 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 27576 Invoking the installer again after successful installation to modify, repair or remove the product etc. leads to failure. Prerequisite: * 32-bit WINEPREFIX (WINEARCH=win32) * .NET Framework 3.5 ('winetricks -q dotnet35') --- snip --- $ WINEDEBUG=+seh,+relay,+msi wine ./rt_7_lite_win7_vista_x86.exe >>log.txt 2>&1 ... 0009:Call KERNEL32.CreateProcessW(00173c70 L"Z:\\home\\focht\\Downloads\\rt_7_lite_win7_vista_x86.exe",00189680 L" /i \"C:\\users\\focht\\Application Data\\Rockers Team\\RT 7 Lite x86\\install\\rt_7_lite_win7_Vista_x86.msi\" AI_SETUPEXEPATH=\"Z:\\home\\focht\\Downloads\\rt_7_lite_win7_vista_x86.exe\" SETUPEXEDIR=\"Z:\\home\\focht\\Downloads\\\"",00000000,00000000,00000000,00000020,00000000,00000000,0034f908,0034f950) ret=0045360b ... 0034:Call KERNEL32.__wine_kernel_init() ret=7bc7ba70 0034:Ret KERNEL32.__wine_kernel_init() retval=7b47b444 ret=7bc7ba70 0009:Ret KERNEL32.CreateProcessW() retval=00000001 ret=0045360b ... 0034:trace:msi:MSI_OpenPackageW ... opening package L"C:\\windows\\Installer\\5809.msi" ... 0034:trace:msi:MSI_OpenDatabaseW Call msvcrt._vsnprintf(0032e760,00000400,714cd469 "%s %s\n",0032eb80) ret=71435caa 0034:Ret msvcrt._vsnprintf() retval=0000002a ret=71435caa L"C:\\windows\\Installer\\5809.msi" #0001 0034:Call ole32.StgOpenStorage(0032f000 L"C:\\windows\\Installer\\5809.msi",00000000,00010022,00000000,00000000,0032ebbc) ret=7143799c 0034:Call KERNEL32.CreateFileW(0032f000 L"C:\\windows\\Installer\\5809.msi",c0000000,00000001,00000000,00000003,10000080,00000000) ret=65264f54 0034:Ret KERNEL32.CreateFileW() retval=000001dc ret=65264f54 0034:Call KERNEL32.GetFileSize(000001dc,00000000) ret=65264f76 0034:Ret KERNEL32.GetFileSize() retval=00166800 ret=65264f76 ... 0034:Call KERNEL32.CreateProcessW(0066de20 L"Z:\\home\\focht\\Downloads\\rt_7_lite_win7_vista_x86.exe",0066e778 L"Z:\\home\\focht\\Downloads\\rt_7_lite_win7_vista_x86.exe /i \"C:\\users\\focht\\Application Data\\Rockers Team\\RT 7 Lite x86\\install\\rt_7_lite_win7_Vista_x86.msi\" EXECUTEACTION=\"INSTALL\" SECONDSEQUENCE=\"1\" CLIENTPROCESSID=\"51\" REMOVE=\"wimmount,MainFeature\" ACTION=\"INSTALL\" C"...,00000000,00000000,00000000,00000000,00000000,00000000,0032f228,0032f28c) ret=0046fa08 ... 0046:Call KERNEL32.__wine_kernel_init() ret=7bc7ba70 0046:Ret KERNEL32.__wine_kernel_init() retval=7b47b444 ret=7bc7ba70 0034:Ret KERNEL32.CreateProcessW() retval=00000001 ret=0046fa08 ... 0046:Call advapi32.RegOpenKeyExW(80000002,0032ea10 L"Software\\Microsoft\\Windows\\CurrentVersion\\Installer\\UserData\\S-1-5-21-0-0-0-1000\\Products\\8AA8552FF60585C4BA460CC5F6767565\\InstallProperties",00000000,000f013f,0032eed4) ret=71487822 ... 0046:Ret advapi32.RegOpenKeyExW() retval=00000000 ret=71487822 ... 0046:Call KERNEL32.GetFileAttributesW(0032f000 L"C:\\windows\\Installer\\5809.msi") ret=71476fa5 0046:Ret KERNEL32.GetFileAttributesW() retval=00000020 ret=71476fa5 ... 0046:trace:msi:MSI_OpenPackageW Call opening package L"C:\\windows\\Installer\\5809.msi" ... 0046:Call ole32.StgOpenStorage(0032f000 L"C:\\windows\\Installer\\5809.msi",00000000,00010022,00000000,00000000,0032ebbc) ret=7143799c 0046:Call KERNEL32.CreateFileW(0032f000 L"C:\\windows\\Installer\\5809.msi",c0000000,00000001,00000000,00000003,10000080,00000000) ret=65264f54 0046:Ret KERNEL32.CreateFileW() retval=ffffffff ret=65264f54 0046:Ret ole32.StgOpenStorage() retval=80030020 ret=7143799c ... 0046:Ret msi.MsiOpenPackageW() retval=0000065b ret=0046e9df ... 0046:Call KERNEL32.FormatMessageW(00001300,00000000,0000065b,00000400,0032f3d0,00000000,00000000) ret=0046fdcd 0046:Ret KERNEL32.FormatMessageW() retval=00000012 ret=0046fdcd ... 0046:Call user32.MessageBoxW(00000000,0065a038 L"Function failed.\r\n",006595a8 L"RT 7 Lite x86",00000010) ret=004079a7 --- snip --- Apparently a sharing violation. The installer package can't be opened a second time with MSIDBOPEN_TRANSACT from the child process (tid=0x0046). The parent installer process (tid=0x0034) still has it open. $ sha1sum rt_7_lite_win7_vista_x86.exe 8afd116c1a524cf1772c972860bc390af713cb6c rt_7_lite_win7_vista_x86.exe $ du -sh rt_7_lite_win7_vista_x86.exe 16M rt_7_lite_win7_vista_x86.exe $ wine --version wine-4.11-192-g90a1e5d943 Regards -- 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 2

[Bug 44741] New: Men of War: Assault Squad - water rendering is broken
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=44741 Bug ID: 44741 Summary: Men of War: Assault Squad - water rendering is broken Product: Wine Version: 3.3 Hardware: x86-64 URL: http://download.nvidia.com/downloads/GeForcecom/gamede mos/MoWAS_SPDemo.zip OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 60749 --> https://bugs.winehq.org/attachment.cgi?id=60749 comparison Looks like a mirror. wine-3.3-235-g1c8c9308e7 -- 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 2

[Bug 39338] New: Unreal Tournament 2004 - inaccurate shadows
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=39338 Bug ID: 39338 Summary: Unreal Tournament 2004 - inaccurate shadows Product: Wine Version: 1.7.51 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: DanBrake0819(a)freenet.de Distribution: --- Created attachment 52420 --> https://bugs.winehq.org/attachment.cgi?id=52420 inaccurate shadows Using the Direct3D renderer the game sometimes produces inaccurate shadows from the character models, they are darker than in the windows version. Also sometimes there are not correctly projected. -- 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 11

[Bug 35561] New: Some MSYS2 commands generate a stackdump
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=35561 Bug ID: 35561 Summary: Some MSYS2 commands generate a stackdump Product: Wine Version: 1.7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: irwin(a)beluga.phys.uvic.ca Classification: Unclassified Created attachment 47484 --> http://bugs.winehq.org/attachment.cgi?id=47484 strace log of execution of mintty The general problem is I cannot start MSYS2 (the successor to MSYS) using its msys2_shell.bat startup batch file (see directions at http://sourceforge.net/p/msys2/wiki/MSYS2 installation/ concerning how to start MSYS2). That batch file (which executes a number of different MSYS2 commands) exits almost immediately with a stack dump. Alexey Pavlov, the developer of MSYS2, suggested I narrow down the problem by attempting to execute the MSYS2 version of mintty.exe directly, and if that did not work (which was the case) then run that app via the MSYS2 strace.exe facility to help figure out what the exact problem is. MSYS2 strace.exe did appear to work and I attach its log (and also the associated stackdump for mintty.exe). Here are some additional details in case there are any difficulties replicating this issue. I have used 3 different versions of 32-bit Wine which I built myself on my Debian Wheezy system. Those are Unpatched Wine-1.6.1, patched Wine-1.6.1, and patched Wine-1.7.12. The patch used was "Hackish patch to fix APC problem" taken from http://bugs.winehq.org/show_bug.cgi?id=24018. The reason why that extremely small patch is relevant is MSYS2 is essentially a simplified modern Cygwin (as opposed to MSYS which is essentially a simplified ancient version of Cygwin). Because the patched versions give improved results (see below), apparently the modern bits of Cygwin that are still part of MSYS2 trigger at least the APC Wine bug for modern Cygwin that did not occur for older Cygwin versions. The version of MSYS2 I am using is msys2-base-i686-20140205.tar.xz. Unpacking that created a top-level directory name of msys32 which I have changed to MSYS2-20140205 to help keep better track of which version of MSYS2 I am trying. I ran the MSYS2 version of strace with the patched versions of Wine as follows: wine(a)raven> wineserver -k wine(a)raven> wineserver -p wine(a)raven> wineconsole --backend=curses cmd Microsoft Windows 5.1.2600 (1.7.12) Z:\home\wine\newstart>PATH=Z:\home\wine\newstart\MSYS2-20140205\bin;%PATH% Z:\home\wine\newstart>MSYS2-20140205\bin\strace.exe MSYS2-0140205\bin\mintty.exe > strace.log 1069046 [main] mintty 44 cygwin_exception::open_stackdumpfile: Dumping stack trace to mintty.exe.stackdump The mintty terminal momentarily appeared before the stackdump occurred. After that stack dump strace did not return (i.e., everything was hung), and the last line in strace.log at that point was 616 1255194 [main] mintty 44 pinfo::exit: Calling ExitProcess n 0x8B, exitcode 0x8B00 I exited the combination of mintty, strace, cmd, and wineconsole the brute-force way by typing "wineserver -k" in a different Linux xterm which added nothing else to strace.log. The strace and stackdump results for patched wine-1.6.1 and patched wine-1.7.12 were virtually identical (except for numerical data like PID numbers). I have attached the wine-1.7.12 versions. When initially investigating this issue I was using unpatched wine-1.6.1. The result of everything I tried was Wine error boxes concerning dll problems. Those error boxes reminded me very much of my troubles in trying to run modern Cygwin from Wine so I applied the APC-related patch, and sure enough, that got rid of the error boxes, and I could get a lot further before I ran into a different problem which is what I have described above. -- 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 47890] New: Conqueror's Blade - Launcher won't launch the game
by WineHQ Bugzilla 21 Jan '20

21 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=47890 Bug ID: 47890 Summary: Conqueror's Blade - Launcher won't launch the game Product: Wine Version: 4.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: werifGX(a)gmail.com Distribution: --- Created attachment 65381 --> https://bugs.winehq.org/attachment.cgi?id=65381 aptli (list of installed packages) Game Conqueror's Blade (https://store.steampowered.com/app/905370 not present in winehq database 10/05/2019) using wine-4.17 and game installed using https://github.com/Winetricks/winetricks/pull/1360 If the "Play" button (https://imgur.com/a/IRdfcdz) is pressed wine with WINEDEBUG="fixme-all" outputs: wine: Call from 0x7104ea8d to unimplemented function ntoskrnl.exe.MmGetPhysicalAddress, aborting wine: Unimplemented function ntoskrnl.exe.MmGetPhysicalAddress called at address 000000007104EA8D (thread 0222), starting debugger... Assuming `ntoskrnl` related issue == system info == kreyren(a)dreamon --------------- OS: Debian GNU/Linux bullseye/sid x86_64 Host: Z68A-D3-B3 Kernel: 5.2.0-2-amd64 Uptime: 2 days, 38 mins Packages: 1465 (dpkg) Shell: bash 5.0.3 Resolution: 3840x2160 WM: Openbox WM Theme: Onyx Theme: Adwaita-dark [GTK2/3] Icons: oxygen [GTK2/3] Terminal: xfce4-terminal Terminal Font: Monospace 20 CPU: Intel i7-2600K (8) @ 3.800GHz GPU: AMD ATI Radeon HD 7870 GHz Edition Memory: 8683MiB / 16025MiB -- 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 9