wine-bugs December 2014

wine-bugs@winehq.org

1 participants
9002 discussions

[Bug 32050] New: Running Dragon age 2 with High resolution textures results in GL_OUT_OF_MEMORY errors
by wine-bugs＠winehq.org 26 Jan '20

26 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=32050 Bug #: 32050 Summary: Running Dragon age 2 with High resolution textures results in GL_OUT_OF_MEMORY errors Product: Wine Version: 1.5.15 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: xvachon(a)gmail.com Classification: Unclassified When Dragon Age 2 is run with the high resolution textures pack (http://social.bioware.com/page/da2-patches), I get GL_OUT_OF_MEMORY errors in about 30 seconds in game and it crashes. Some examples include : err:d3d_surface:surface_allocate_surface >>>>>>>>>>>>>>>>> GL_OUT_OF_MEMORY (0x505) from glTexImage2D @ surface.c / 2747 err:d3d_surface:surface_upload_data >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from glCompressedTexSubImage2DARB @ surface.c / 2364 err:d3d_draw:drawStridedFast >>>>>>>>>>>>>>>>> GL_OUT_OF_MEMORY (0x505) from glDrawElementsBaseVertex @ drawprim.c / 48 err:d3d:buffer_create_buffer_object glBufferDataARB failed with error GL_OUT_OF_MEMORY (0x505) err:d3d:buffer_create_buffer_object Failed to create a vertex buffer object. Continuing, but performance issues may occur Running the game with the highest DirectX9 settings (Medium, Anti-aliasing 16x) and High Res textures disabled works well on my system. wine 1.5.15 Dragon age 2 1.04 with all DLC Nvidia 550 Ti 2GB Ram Arch Linux X64 -- 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 17

[Bug 25945] New: C_ASSERT doesn't fail if given non-constant expression
by wine-bugs＠winehq.org 26 Jan '20

26 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=25945 Summary: C_ASSERT doesn't fail if given non-constant expression Product: Wine Version: 1.1.22 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: alexander.scott.johns+winebug(a)googlemail.com In commit wine-1.1.21-63-g5d31eb9 AJ changed the definition of C_ASSERT (in include/winnt.h) to make it compatible with newer versions of GCC. Roughly, the change was: -#define C_ASSERT(e) extern char __C_ASSERT__[(e)?1:-1] __attribute__((unused)) +#define C_ASSERT(e) extern void __C_ASSERT__(int [(e)?1:-1]) Unfortunately, in GCC 4.4.3, the new definition of C_ASSERT doesn't fail when given a non-constant expression. E.g.: C_ASSERT(rand() == -1); /* ignored */ I think this is because GCC (as per C99) is treating the parameter of __C_ASSERT__ as a VLA (variable length array), and so its type is equivalent to int[*]. -- 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 6

[Bug 33065] New: Make it possible to build a winetest executable with a single test
by wine-bugs＠winehq.org 24 Jan '20

24 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=33065 Bug #: 33065 Summary: Make it possible to build a winetest executable with a single test Product: Wine-Testbot Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified Currently WineTestBot runs individual tests through TestLauncher (see testbot/src/TestLauncher). TestLauncher is responsible for checking for potential issues like missing dlls that could cause the test to hang on an error dialog. However that means duplicating a lot of WineTest's code and also that TestLauncher tends to be out of date (see bug 31609 for instance). Building the regular winetest.exe (with all the tests) and just running one test would result in a lot of wasted disk space and bandwidth. So the idea would be to make it possible to build winetest.exe and to only include the one test we want to run in the resources. -- 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 19329] New: Program installs but client fails to connect to server
by wine-bugs＠winehq.org 24 Jan '20

24 Jan '20

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 23 Jan '20

23 Jan '20

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 23 Jan '20

23 Jan '20

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 37789] New: cmd.exe /c cannot handle "(" and ")" characters in a full script path name
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

https://bugs.winehq.org/show_bug.cgi?id=37789 Bug ID: 37789 Summary: cmd.exe /c cannot handle "(" and ")" characters in a full script path name Product: Wine Version: 1.7.33 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: cmd Assignee: wine-bugs(a)winehq.org Reporter: abolte(a)systemsaviour.com Distribution: --- Created attachment 50334 --> https://bugs.winehq.org/attachment.cgi?id=50334 Various cmd executions discussed in the report using WINEDEBUG='+cmd'. Far Cry 4 (which requires at least a 64-bit Windows 7 prefix) fails to call a bash script on launch: Can't recognise 'C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software\GEFirewall.bat /silent' as an internal or external command, or batch script. Sure enough, calling it manually (even without the /silent argument) results in the same error: $ wine cmd.exe /c 'C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software\GEFirewall.bat' Can't recognise 'C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software\GEFirewall.bat' as an internal or external command, or batch script. Suspicious of the ( and ) characters in the URL, I tried copying the GEFirewall.bat to the path 'C:\Program Files\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software\' (which doesn't normally exist but I manually created it). $ wine cmd.exe /c 'C:\Program Files\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software\GEFirewall.bat' fixme:netsh:wmain stub: L"netsh" L"firewall" L"add" L"allowedprogram" L"C:\\Program Files\\Ubisoft\\Ubisoft Game Launcher\\games\\Far Cry 4\\Support\\Software\\..\\..\\bin\\FarCry4.exe" L"FarCry4" L"ENABLE" fixme:netsh:wmain stub: L"netsh" L"firewall" L"add" L"allowedprogram" L"C:\\Program Files\\Ubisoft\\Ubisoft Game Launcher\\games\\Far Cry 4\\Support\\Software\\..\\..\\bin\\IGE_WPF64.exe" L"FarCry4-IGE" L"ENABLE" The script ran perfectly. One more test to confirm my sanity: $ wine explorer.exe 'C:\Program Files (x86)\Ubisoft\Ubisoft Game Launcher\games\Far Cry 4\Support\Software' This opened the directory in explorer fine. Only cmd.exe /c ... seems to show 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.

2 5

[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@raven> wineserver -k wine@raven> wineserver -p wine@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 13863] New: Armed Assault (ArmA) doesn't render any 3D graphics
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=13863 Summary: Armed Assault (ArmA) doesn't render any 3D graphics Product: Wine Version: 1.0-rc4 Platform: PC-x86-64 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: ben(a)atomnet.co.uk Created an attachment (id=13933) --> (http://bugs.winehq.org/attachment.cgi?id=13933) Entire log minus 40000 duplicate lines. The game fails to display any of the in-game graphics whether it's on the menu or inside the game itself. It still renders the HUD and Menu's themselves, but not the actual 3D game graphics. It spits out the errors (the ones which appear many times in the attached log) about 5000 times a second. -- 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 43

[Bug 34146] New: Wings of Prey demo background image in launcher is not shown
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=34146 Bug #: 34146 Summary: Wings of Prey demo background image in launcher is not shown Product: Wine Version: 1.6 Platform: x86 URL: http://www.fileplanet.com/208822/200000/fileinfo/Wings -of-Prey--Demo OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: andrey.goosev(a)gmail.com Classification: Unclassified Created attachment 45421 --> http://bugs.winehq.org/attachment.cgi?id=45421 launcher settings (wine) Launcher hasn't background image. -- 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 14

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs December 2014