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

[Bug 34070] New: 'fixme:win:alloc_winproc too many winprocs' prevents simutronics StormFront.exe from updating widgets
by wine-bugs＠winehq.org 16 Jun '16

16 Jun '16

http://bugs.winehq.org/show_bug.cgi?id=34070 Bug #: 34070 Summary: 'fixme:win:alloc_winproc too many winprocs' prevents simutronics StormFront.exe from updating widgets Product: Wine Version: unspecified Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: matt(a)tolton.com Classification: Unclassified Created attachment 45293 --> http://bugs.winehq.org/attachment.cgi?id=45293 Debug log This bug is about StormFront.exe from Simutronics. The application works fine for awhile, but at some point certain widgets in the app stop updating. I believe this is due to the message I'm seeing in the debug log (see attached): fixme:win:alloc_winproc too many winprocs The time it starts appearing coincides with the widgets not updating. The longer that the application runs, the more messages that are emitted. I ran it for about 4 hours and saw around 20k messages. I did some code spelunking and tracked it down to this file: https://github.com/mirrors/wine/blob/master/dlls/user32/winproc.c#L298 It seems like MAX_WINPROCS could be increased, and it might alleviate the problem, but would probably just make it take longer to manifest. (Since it only manifests after using the app for a little while, now). I am using Crossover Mac 12.2.0 (I am not sure which version of wine this is). My question is twofold: 1) How hard would it be to actually reclaim these winprocs rather than leak them? 2) If that doesn't work, is there some way for me to increase the MAX_WINPROCS constant and recompile user32.dll to use for just one bottle in CrossOver? -- 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 23

[Bug 35711] New: Winelib: compile error in wincon.h if NOGDI is defined before #include <windows.h>
by wine-bugs＠winehq.org 16 Jun '16

16 Jun '16

http://bugs.winehq.org/show_bug.cgi?id=35711 Bug ID: 35711 Summary: Winelib: compile error in wincon.h if NOGDI is defined before #include <windows.h> Product: Wine Version: 1.4.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: matteo(a)mitalia.net As described in the summary; if I try to compile the following file #define NOGDI #include <windows.h> int main() { return 0; } with winegcc (wine-dev package 1.4.1 from Ubuntu 13.10) I get In file included from /usr/include/wine/windows/windows.h:42:0, from test.c:2: /usr/include/wine/windows/wincon.h:337:62: error: unknown type name ‘LPCONSOLE_FONT_INFOEX’ WINBASEAPI BOOL WINAPI GetCurrentConsoleFontEx(HANDLE,BOOL,LPCONSOLE_FONT_INFOEX); ^ /usr/include/wine/windows/wincon.h:375:62: error: unknown type name ‘LPCONSOLE_FONT_INFOEX’ WINBASEAPI BOOL WINAPI SetCurrentConsoleFontEx(HANDLE,BOOL,LPCONSOLE_FONT_INFOEX); ^ winegcc: gcc failed This comes from the fact that the typedef LPCONSOLE_FONT_INFOEX (and related types) is #ifdef-ed out when NOGDI is defined, but SetCurrentConsoleFontEx (which depends from this type) is always included. The bug makes compiling anything that uses the NOGDI option impossible. -- 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 8

[Bug 10063] New: wineconsole run fail on korean locale.
by wine-bugs＠winehq.org 16 Jun '16

16 Jun '16

http://bugs.winehq.org/show_bug.cgi?id=10063 Summary: wineconsole run fail on korean locale. Product: Wine Version: 0.9.47. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: dlunch(a)gmail.com wineconsole failed to run in korean locale. it reports 'err:wineconsole:WCUSER_SetFont wrong font' few times and 'err:wineconsole:WINECON_Fatal Couldn't find a decent font, aborting'. but when i tried LANG="C" wineconsole cmd, it runs successfully. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 32

[Bug 36031] New: 9700M incorrectly detected as 9400
by wine-bugs＠winehq.org 16 Jun '16

16 Jun '16

http://bugs.winehq.org/show_bug.cgi?id=36031 Bug ID: 36031 Summary: 9700M incorrectly detected as 9400 Product: Wine Version: 1.7.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: funkydude87(a)hotmail.co.uk Running the Battle.net client and attempting to launch WoW. Using the nouveau drivers under 64bit Ubuntu 14.04 and getting a warning message: OS: Windows XP x64 service pack 2 Card: Nvidia Geforce 9400 GT It is a warning that my system is below the minimum recommendations. When launching the game, certain graphical features are disabled that are otherwise enabled under Windows. This is a laptop with a Geforce 9700M GT, it thinks I'm running a 9400 desktop card. It also thinks I'm running XP SP2, not sure if that's correct or should be SP3. lspci result of my card in linux: 01:00.0 VGA compatible controller: NVIDIA Corporation G96M [GeForce 9700M GT] (rev a1) -- 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 28

[Bug 32979] New: Metal Gear Solid Crash
by wine-bugs＠winehq.org 16 Jun '16

16 Jun '16

http://bugs.winehq.org/show_bug.cgi?id=32979 Bug #: 32979 Summary: Metal Gear Solid Crash Product: Wine Version: 1.5.23 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: levanchelidze(a)gmail.com Classification: Unclassified Created attachment 43558 --> http://bugs.winehq.org/attachment.cgi?id=43558 backtrace no fix Tried to run Start Metal Gear Solid installed with no problem but when I started it it gave me a massage that it would start it in software mode but after this it just showed black screen and nothing more then I changed the windows xp to windows 2000 same crash. then I tried GeForce-ATi FiX same error could not run -- 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 21

[Bug 35054] New: Dragon Age 2 system diagnostics tool fails to recognize GeForce GT 425M
by wine-bugs＠winehq.org 16 Jun '16

16 Jun '16

http://bugs.winehq.org/show_bug.cgi?id=35054 Bug #: 35054 Summary: Dragon Age 2 system diagnostics tool fails to recognize GeForce GT 425M Product: Wine Version: 1.7.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello folks, while looking at bug 33552 I remembered that Wine doesn't recognize my own card ;-) It probably won't hurt to have at least one of "NVIDIA GeForce GT 4xx M" series listed. --- snip --- $ lspci -nn | grep VGA | grep NVIDIA 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) --- snip --- PCI device id -> 0x0df0 1 GiB SDRAM Source: http://source.winehq.org/git/wine.git/blob/57d7f74d34f2ce0968af2eb14c7e866d… NVIDIA GeForce GT 400M Series specs: --- snip --- GeForce GT 445M 144 @ 590MHz 192 / 128 Bit @ 1250MHz GeForce GT 435M 96 @ 650MHz 128 Bit @ 800MHz GeForce GT 425M 96 @ 560MHz 128 Bit @ 800MHz GeForce GT 420M 96 @ 500MHz 128 Bit @ 800MHz GeForce GT 415M 48 @ 500MHz 128 Bit @ 800MHz Codename N11P-GS Architecture Fermi Pipelines 96 - unified Core Speed * 560 MHz Shader Speed * 1120 MHz Memory Speed * 800 MHz Memory Bus Width 128 Bit Memory Type DDR3 Max. Amount of Memory 1024 MB Shared Memory no DirectX DirectX 11, Shader 5.0 technology 40 nm Features Optimus Support, PureVideo HD VP4, 3D Vision, Bitstream HD Audio, CUDA, DirectCompute, OpenCL, OpenGL 4.0, DirectX 11 Notebook Size medium sized Date of Announcement 15.08.2010 --- snip --- Regards -- 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 10

[Bug 32594] New: MessageBox hook WH_CBT HCBT_ACTIVATE sees wrong button size given MB_DEFBUTTON* style
by wine-bugs＠winehq.org 15 Jun '16

15 Jun '16

http://bugs.winehq.org/show_bug.cgi?id=32594 Bug #: 32594 Summary: MessageBox hook WH_CBT HCBT_ACTIVATE sees wrong button size given MB_DEFBUTTON* style Product: Wine Version: 1.5.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: staticinline(a)gmail.com Classification: Unclassified MessageBox buttons are not correctly sized during the first call to a WH_CBT HCBT_ACTIVATE hook if a MB_DEFBUTTON* style is used on the message box. Observe in the Wine msgbox.c:MSGBOX_OnInit code, the "position the buttons" loop iterates through each button, and if a button has a MB_DEFMASK set, it also calls SetFocus, which triggers the WH_CBT HCBT_ACTIVATE hook. This is before this loop positions the remaining buttons. The attached wine-msgbox-patch.txt is a patch to Wine 1.5.20 that positions all the buttons before processing the MB_DEFMASK. This problem affects programs using the wxWidgets 2.9.x GUI library, whose message box implementation measures (via GetWindowRec) the initial sizes of the buttons during a WH_CBT HCBT_ACTIVATE hook [2]. This problem is analyzed more fully in a wxWidgets ticket [1]. The problem has also been observed to affect at least as far back as Wine 1.0.1 (debian squeeze, x86). [1] http://trac.wxwidgets.org/ticket/14926 [2] http://trac.wxwidgets.org/browser/wxWidgets/trunk/src/msw/msgdlg.cpp#L369 -- 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 6

[Bug 31697] New: Can't Register Sony Media Manager, couldn't get cookie
by wine-bugs＠winehq.org 14 Jun '16

14 Jun '16

http://bugs.winehq.org/show_bug.cgi?id=31697 Bug #: 31697 Summary: Can't Register Sony Media Manager, couldn't get cookie Product: Wine Version: 1.5.12 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: wininet AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified Trying to reproduce bug 31695, I downloaded Sony Media Manager for Walkman 1.2, 9e0e4ab39084724c4f6001de5f2df8b39390ddcf mm4wm12_lite.exe from http://esupport.sony.com/perl/swu-download.pl?upd_id=3733&SMB=YES&template_… Running wine mm4wm12_lite.exe downloads and tries to install vcrun2005, quicktime 7, and wmp11 runtime. It hangs and fails with "requirements not met". To work around this, follow the tip from http://appdb.winehq.org/objectManager.php?sClass=version&iId=20125&iTesting… e.g. download abc56a568dd1e8ffbfb6f1cbd4d42c031003ed52 wmp11-windowsxp-x86-enu.exe from http://download.cnet.com/windows-media-player/ then do cabextract wmp11-windowsxp-x86-enu.exe -F wmfdist11.exe cabextract wmp11-windowsxp-x86-enu.exe -F wmp11.exe wine wmfdist11 wine wmp11 Both installs will hang after declaring success; ^C them. (You can do that from a clean wineprefix or after the installer fails once, doesn't matter.) Running mm4wm12_lite.exe then downloads and installs vcrun2005 and quicktime 7, then runs the Media Manager installer. This fails right at the end when it's doing "Please wait for initial configuration of Media Manager", with dialog box "Fatal error in gc GetThreadContext failed" Killing this and then starting the app fails because of a missing registry key. To work around this, run winetricks dotnet20 before installing. Then installing succeeds, and on first run the app requires you to register. Doing so fails with a dialog "Requesting cookie... " followed by "An error occurred during registration", and console messages: fixme:wininet:set_cookie persistent cookies not handled (L"expires=Wed, 13-Sep-2017 11:27:19 GMT; path=/; HttpOnly") fixme:wininet:set_cookie httponly not handled (L"HttpOnly") fixme:wininet:set_cookie secure not handled (L"Secure; HttpOnly") ('winetricks wininet' seems to get further, then runs into what look like wintrust problems, but that's another bug) -- 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 4

[Bug 33275] New: Far Cry: Segmentation Fault on start
by wine-bugs＠winehq.org 13 Jun '16

13 Jun '16

http://bugs.winehq.org/show_bug.cgi?id=33275 Bug #: 33275 Summary: Far Cry: Segmentation Fault on start Product: Wine Version: 1.5.23 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ascendant512(a)gmail.com Classification: Unclassified Created attachment 44023 --> http://bugs.winehq.org/attachment.cgi?id=44023 Compressed relay debug log, use unxz or xz --decompress When executing FarCry.exe, wine will segfault. This happens before the game finishes starting. This is not a duplicate of http://bugs.winehq.org/show_bug.cgi?id=9252 The segfault happens before any Direct3D calls are made. I've attached the output of debug.err when running this script: #!/bin/bash export WINEPREFIX=/mnt/media/bin/.wine/far_cry export WINEDEBUG="+relay,+d3d" wine "C:\Program Files (x86)\Far Cry\Bin32\FarCry.exe" 2> debug.err Output of above is: ./farcry.bash: line 4: 24716 Segmentation fault wine "C:\Program Files (x86)\Far Cry\Bin32\FarCry.exe" 2> debug.err This is of course a fresh wine prefix, no winetricks. Host OS: Gentoo amd64 wine compiled with these use flags: X alsa cups elibc_glibc gecko jpeg lcms mono mp3 ncurses nls opengl oss perl png prelink scanner ssl threads truetype udisks v4l win32 win64 xinerama xml -capi -custom-cflags -fontconfig -gphoto2 -gsm -gstreamer -ldap -odbc -openal -opencl -osmesa -pulseaudio -samba -selinux -test -xcomposite GCC version: 4.6.3 Game patched to version 1.4 with no-cd -- 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 44

[Bug 32094] New: Dragon Age: Origins crashes in opengl
by wine-bugs＠winehq.org 10 Jun '16

10 Jun '16

http://bugs.winehq.org/show_bug.cgi?id=32094 Bug #: 32094 Summary: Dragon Age: Origins crashes in opengl Product: Wine Version: 1.5.16 Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl AssignedTo: wine-bugs(a)winehq.org ReportedBy: ovvldc(a)gmail.com Classification: Unclassified Created attachment 42313 --> http://bugs.winehq.org/attachment.cgi?id=42313 backtrace with default settings I have tried running Dragon Age: Origins. I am using Wineskin, which conveniently wraps a vanilla Wine engine (1.5.16 in this case) and XQuartz, the latest X11 version for Mac. I am using OS X 10.6.8 with an nVidia 9400M CPU. Installation: used Winetricks to install MSXML3, PhysX and dotnet2.0sp2. This was done because the installer otherwise complains about malformed XML, because the PhysX installer crashes and because it was anyway installing dotnet2.0sp2. The game installer also installed directx9, xact and xinput by itself (not knowing it was running under Wine). I then installed Awakenings (for which the installer crashed towards the very end) and patch 1.04 (1.05 has really minor changes and is not worth bothering with). When I ran the game, I got a crash in the splash screen: Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x9aa78e4f). The backtrace is attached as DAO_backtrace.txt. Lots of things going through the opengl code with the closest native bit being: d3d9_device_DrawIndexedPrimitive. I then tried using glsl=disabled, which immediately crashes the game on startup, so I turned that back to glsl=enabled I then set ddr=gdi, thinking that the crash might go away if I move away from opengl for this section. This worked, and I got the game to start and show the usual main menu. I then chose 'new game' and the game crashed as soon as I tried to skip the opening cinematic: Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x7671475f). The backtrace is attached as DAO_backtrace ddr=gd.txt. Again, some things going through the opengl code with the closest native bit being: d3d9_swapchain_Present. I hope this description and the backtraces are of some use. -- 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 6