March 2018 - Wine-Bugs - list.winehq.org

[Bug 44684] New: Shaders fail to compile in Roblox Studio (white window)
by wine-bugs＠winehq.org Jan. 24, 2020

Jan. 24, 2020

https://bugs.winehq.org/show_bug.cgi?id=44684 Bug ID: 44684 Summary: Shaders fail to compile in Roblox Studio (white window) Product: Wine Version: 3.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: and3md(a)gmail.com Distribution: --- Created attachment 60693 --> https://bugs.winehq.org/attachment.cgi?id=60693 Roblox Studio run log The application displays splash screen correctly. Next, the main window is showed which is "empty" (the window is white). The cursor changes its shape in some places so probably it's just a display case. Wine returns a lot of errors: 007d: err: d3dcompiler: compile_shader HLSL shader parsing failed. 007d: fixme: hlsl_parser: declare_vars Complex initializers are not supported yet. Hardware: Geforce GTX 1060 (proprietary linux driver). -- 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 19329] New: Program installs but client fails to connect to server
by wine-bugs＠winehq.org Jan. 23, 2020

Jan. 23, 2020

http://bugs.winehq.org/show_bug.cgi?id=19329 Summary: Program installs but client fails to connect to server Product: Wine Version: 1.1.25 Platform: PC URL: http://www.livezilla.net/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: junk(a)mandd.com Using Wine 1.1.25 and a clean ~/.wine, I had to install dotnet20 and ie6 (I used winetricks) before the installer would complete. After that the Livezilla client will run. But when I try to connect to a Livezilla server, an error window pops up stating: -------------------------------------------------------------------- The underlying connection was closed: The connection was closed unexpectedly. Further information: The underlying connection was closed: The connection was closed unexpectedly. -------------------------------------------------------------------- -- 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 41

[Bug 34865] New: Can't execute mingw toolchain provided by Rtools
by wine-bugs＠winehq.org Jan. 22, 2020

Jan. 22, 2020

http://bugs.winehq.org/show_bug.cgi?id=34865 Bug #: 34865 Summary: Can't execute mingw toolchain provided by Rtools Product: Wine Version: 1.7.4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mail(a)kirill-mueller.de Classification: Unclassified I can't execute "R CMD INSTALL" on an installation of R + Rtools in Wine (latest version from PPA "ppa:ubuntu-wine/ppa"). A reproducible script and console output can be found here: https://gist.github.com/krlmlr/7333242 . The script will set and write to $WINEPREFIX and download to $DOWNLOAD_DIR. Unfortunately, the logs do not show enough detail. After the line `about to run R CMD SHLIB -o kimisc.dll rcpp_hello_world.cpp RcppExports.cpp --debug`, a call to `gcc` is made. (I have added the output of the same call on my Linux system to the Gist.) To me, it seems that the calling process is not notified when the child process has completed, and it stops after a timeout. My hope is that this has been seen before and that there's an easy fix. I'm really new to Wine. -- 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 11

[Bug 35344] New: Cygwin's post-install scripts fail on fork errors
by wine-bugs＠winehq.org Jan. 22, 2020

Jan. 22, 2020

http://bugs.winehq.org/show_bug.cgi?id=35344 Bug ID: 35344 Summary: Cygwin's post-install scripts fail on fork errors Product: Wine Version: 1.7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mail(a)georg.so Classification: Unclassified Executing 'wine setup-x86.exe' seems to work quite well (you can step through the wizard, packages are downloaded and extracted) until the post-installation bash scripts are executed. Then I get for each script a message like: running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/glib2.0.sh" [..] fixme:ntdll:NtQueryInformationProcess (process=0xffffffff) Unimplemented information class: ProcessSessionInformation [..] fixme:ntdll:NtQueryVolumeInformationFile 0xf0: faking attribute info fixme:ntdll:NtQueryVolumeInformationFile 0xec: faking attribute info fixme:ntdll:NtQueryInformationFile Unsupported class (34) [..] fixme:ntdll:NtQueryVolumeInformationFile 0xf4: faking attribute info fixme:ntdll:NtQueryInformationFile Unsupported class (8) [..] fixme:ntdll:NtQueryVolumeInformationFile 0xfc: faking attribute info [..] fixme:ntdll:NtQueryVolumeInformationFile 0x100: faking attribute info fixme:ntdll:NtQueryVolumeInformationFile 0x124: faking attribute info [..] fixme:ntdll:NtQueryVolumeInformationFile 0x128: faking attribute info [..] /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: Resource temporarily unavailable abnormal exit: exit code=254 The fork error message are always displayed after some kind of timeout. Where to get the setup-x86.exe: http://cygwin.com/setup-x86.exe $ md5sum setup-x86.exe c9818d3500e42fd9eb755d424450871a setup-x86.exe Executing Cygwin's setup exe inside wine looks a little bit silly, but I want to create a reference cygwin installation for deployment purposes. see also: http://wiki.winehq.org/CygwinSupport -- 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 41199] New: SW KoTOR: Unhandled page fault on write access
by wine-bugs＠winehq.org Jan. 22, 2020

Jan. 22, 2020

https://bugs.winehq.org/show_bug.cgi?id=41199 Bug ID: 41199 Summary: SW KoTOR: Unhandled page fault on write access Product: Wine Version: 1.9.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bystrzak14(a)gmail.com Distribution: --- Created attachment 55439 --> https://bugs.winehq.org/attachment.cgi?id=55439 Log from gameplay I recently installed KoTOR on Fedora 24. Game starts correctly through Steam and works fluently, but it randomly crashes during loading new area or saved game. I tried tweaking "quartz" to "bultin" as in this thread https://bugs.winehq.org/show_bug.cgi?id=22910 although is kinda old. Anyway, this didn't solve my problem. Those crashes are really annoying and I can't really enjoy the game because of that. I run the game with custom prefix using 32bit. I attach complete log generated throughout my gameplay. -- 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 42988] New: Pocket Mirror causes heavy flickering in fullscreen mode on wine-staging
by wine-bugs＠winehq.org Jan. 22, 2020

Jan. 22, 2020

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 43250] New: PerfectTUNES cannot access network
by wine-bugs＠winehq.org Jan. 22, 2020

Jan. 22, 2020

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 44741] New: Men of War: Assault Squad - water rendering is broken
by wine-bugs＠winehq.org Jan. 21, 2020

Jan. 21, 2020

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 Jan. 21, 2020

Jan. 21, 2020

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 Jan. 21, 2020

Jan. 21, 2020

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