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

[Bug 43784] New: Updating a 2.16 prefix to 2.17 causes Wine to hang forever updating the configuration.
by wine-bugs＠winehq.org Feb. 7, 2018

Feb. 7, 2018

https://bugs.winehq.org/show_bug.cgi?id=43784 Bug ID: 43784 Summary: Updating a 2.16 prefix to 2.17 causes Wine to hang forever updating the configuration. Product: Wine Version: 2.17 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexchandel(a)gmail.com Running winecfg (with wine 2.17) on a 2.16 prefix causes the "The Wine configuration in X is being updated, please wait..." dialog to appear. However, it never finishes, and the Activity Monitor reveals an unresponsive process using 58% CPU. Eventually, this message is printed: err:process:__wine_kernel_init boot event wait timed out and the winecfg window appears. However, the unresponsive process continues using 58% CPU and never exits, even when winecfg is closed. -- 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 5

[Bug 31422] New: Generate Website fails to display with iexplore
by wine-bugs＠winehq.org Feb. 6, 2018

Feb. 6, 2018

http://bugs.winehq.org/show_bug.cgi?id=31422 Bug #: 31422 Summary: Generate Website fails to display with iexplore Product: Wine Version: 1.5.10 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: mshtml AssignedTo: wine-bugs(a)winehq.org ReportedBy: leslie_alistair(a)hotmail.com Classification: Unclassified Created attachment 41303 --> http://bugs.winehq.org/attachment.cgi?id=41303 Sample generated website Attempt to load the attached web site results in an error message being display "It appears that you may have Javascript disabled. ". If you use native JScript the same error message is displayed. -- 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 9

[Bug 26263] New: __wine_call_from_regs violates x86 ABI
by wine-bugs＠winehq.org Feb. 6, 2018

Feb. 6, 2018

http://bugs.winehq.org/show_bug.cgi?id=26263 Summary: __wine_call_from_regs violates x86 ABI Product: Wine Version: 1.3.14 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: bart.vanassche(a)gmail.com Created an attachment (id=33470) --> (http://bugs.winehq.org/attachment.cgi?id=33470) Valgrind output As far as I know x86 applications should not modify data below the stack pointer. Running the latest (2011-02-27) git version of Wine under Valgrind results in many "address is just below the stack pointer" complaints. See also the attachment for the output of the following command: valgrind --suppressions=wine-memcheck.supp --trace-children=yes --trace-children-skip=/usr/bin/wineserver --trace-children-skip-by-arg=wineboot.exe,winemenubuilder.exe,services.exe,winedevice.exe,plugplay.exe,explorer.exe --vex-iropt-precise-memory-exns=yes --num-callers=32 --fullpath-after=$HOME/software --error-limit=no --gen-suppressions=all wine notepad -- 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 8

[Bug 9493] New: Cosmetic Errors when using Default Luna theme from Windows XP
by wine-bugs＠winehq.org Feb. 3, 2018

Feb. 3, 2018

http://bugs.winehq.org/show_bug.cgi?id=9493 Summary: Cosmetic Errors when using Default Luna theme from Windows XP Product: Wine Version: 0.9.44. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P3 Component: wine-gui AssignedTo: wine-bugs(a)winehq.org ReportedBy: smackdat1(a)gmail.com Created an attachment (id=7842) --> (http://bugs.winehq.org/attachment.cgi?id=7842) errors using luna theme Background for dragbar is black and Frame and Checkbox labelsdo not blend with the background. Component is just a guess -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 31

[Bug 40418] New: Doom 4 requires bcrypt AES provider
by wine-bugs＠winehq.org Feb. 2, 2018

Feb. 2, 2018

https://bugs.winehq.org/show_bug.cgi?id=40418 Bug ID: 40418 Summary: Doom 4 requires bcrypt AES provider Product: Wine Version: 1.9.7 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs(a)winehq.org Reporter: 00cpxxx(a)gmail.com CC: charles.gorand.dev(a)gmail.com Distribution: --- Continuation of bug 40406. fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"AES" not supported -- 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 32

[Bug 42716] New: IsDebuggerPresent returning TRUE
by wine-bugs＠winehq.org Feb. 2, 2018

Feb. 2, 2018

https://bugs.winehq.org/show_bug.cgi?id=42716 Bug ID: 42716 Summary: IsDebuggerPresent returning TRUE Product: Wine Version: 2.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: dmpeletronic(a)gmail.com Distribution: --- The function above is always returning true, depending on the machine. It seems that the struct is not initialized correctly. BOOL WINAPI IsDebuggerPresent(void) { return NtCurrentTeb()->Peb->BeingDebugged; } Please check the Peb and BeingDebugged initialization. As consequence, some applications sometimes cannot be run, such as MetaTrader5, and we get a DialogBox: “A debugger has been found running in your system. Please unload it from your memory and restart your program”. -- 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 26

[Bug 44277] New: WOLF RPG Editor: Certain background music doesn' t stop when using XAudio2
by wine-bugs＠winehq.org Feb. 2, 2018

Feb. 2, 2018

https://bugs.winehq.org/show_bug.cgi?id=44277 Bug ID: 44277 Summary: WOLF RPG Editor: Certain background music doesn't stop when using XAudio2 Product: Wine Version: 3.0-rc4 Hardware: x86-64 URL: https://www.freem.ne.jp/win/game/10030 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: kakurasan(a)gmail.com Distribution: --- Created attachment 60102 --> https://bugs.winehq.org/attachment.cgi?id=60102 savegame In a game created with WOLF RPG Editor v2.10 (Japanese), certain background music doesn't stop when using XAudio2. If WINEDLLOVERRIDES="xaudio2_7=;xaudio2_8=" is specified, it works as expected (DirectSound is used instead). Steps to reproduce: 1. Download the game "Time Flow" from https://www.freem.ne.jp/dl/win/10030 2. Unpack TimeFlow.zip (e.g. unar -e cp932 TimeFlow.zip) 3. Unpack timeflow-save.tar.xz and put the *.sav files into "TimeFlow/Save/" 4. Run Game.exe without disabling XAudio2 5. Hold "Enter" key for a while (Load savegame, start battle, and defeat all enemies) 6. The background music (in the battle) doesn't stop and the program plays multiple music at the same time $ sha1sum TimeFlow.zip 4242dbbbce3f610647841e8b45d375cad76a189d TimeFlow.zip -- 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 19

[Bug 38064] New: Using alt+enter to fullscreen any rpgmaker XP game causes keyboard input lose and not fullscreen
by wine-bugs＠winehq.org Feb. 2, 2018

Feb. 2, 2018

https://bugs.winehq.org/show_bug.cgi?id=38064 Bug ID: 38064 Summary: Using alt+enter to fullscreen any rpgmaker XP game causes keyboard input lose and not fullscreen Product: Wine Version: 1.7.36 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: t_arceri(a)yahoo.com.au Distribution: --- Full screen used to work fine in wine-1.7.31 and broke in wine-1.7.31. Now when I try to go full screen it doesn't take input from the keyboard meaning I can't exit and have to power off my laptop. Also it doesn't fullscreen properly just part of the window is redrawn in the top left. I've bisected the input issue to this commit: 45d530461bf29c953f5f4532cc0e917b4c4fc296 is the first bad commit commit 45d530461bf29c953f5f4532cc0e917b4c4fc296 Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Thu Nov 13 20:39:25 2014 +0100 wined3d: Minimize device windows on focus loss. And bisected the drawing issue to: commit f6dde7062413a1dfdd71acc92c5178ac66f3ade0 Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Tue Nov 18 21:26:57 2014 +0100 wined3d: Restore the display mode on focus change. Example app: http://www.itsqueeze.com/wp-content/uploads/2015/02/Custom_Mouse_System.tar… You also need the run time package for Rpgmaker XP: http://www.rpgmakerweb.com/download/additional/run-time-packages Just run Game.exe and press alt+enter -- 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 18

[Bug 44365] New: armel build fails: selected processor does not support `strd r4,[sp]' in ARM mode
by wine-bugs＠winehq.org Feb. 2, 2018

Feb. 2, 2018

https://bugs.winehq.org/show_bug.cgi?id=44365 Bug ID: 44365 Summary: armel build fails: selected processor does not support `strd r4,[sp]' in ARM mode Product: Wine Version: 3.0-rc2 Hardware: x86 URL: https://buildd.debian.org/status/fetch.php?pkg=wine-de velopment&arch=armel&ver=3.0%7Erc3-1&stamp=1516136421& raw=0 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: jre.winesim(a)gmail.com Distribution: Debian Beginning with 3.0-rc2 Wine started to fail to build on armel in Debian again: gcc -c -o relay.o relay.c -I. -I../../include -D__WINESRC__ -D_NTSYSTEM_ -D_REENTRANT -fPIC -Wall \ -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers \ -Wno-packed-not-aligned -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits \ -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith -Wlogical-op -gdwarf-2 \ -gstrict-dwarf -Werror -Wdate-time -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -march=armv5t -Wno-error -marm -mfloat-abi=soft [...] {standard input}: Assembler messages: {standard input}:51: Error: selected processor does not support `strd r4,[sp]' in ARM mode Makefile:521: recipe for target 'relay.o' failed make[2]: *** [relay.o] Error 1 make[2]: Leaving directory '/<<PKGBUILDDIR>>/dlls/ntdll' Makefile:13147: recipe for target 'dlls/ntdll' failed make[1]: *** [dlls/ntdll] Error 2 I put the link to the complete buildlog in the URL field. For now I only tested rc2 and rc3, but will do the rest the next days. Looking at the changes in dlls/ntdll/ I don't expect any existing fixes, so I guess it's better to report as soon as possible. I didn't bisect the issue but assume it's in these commits: 5e3534ee411a8c5baea5022705eac0e3c7f3cc70 8a07ee48fa96e12474cb6f7c1d365858aaebcdff f492efdb3c77f015247f6b73d98110a0353035b3 d147c4c3239a367381ac5dbccbc1cab40699fedb btw, Wine 3.0-rc1 built fine again on armel in Debian. Thanks for taking care of #44010! Greets jre -- 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 5

[Bug 44158] New: QueryProcessCycleTime() causing exception/crash
by wine-bugs＠winehq.org Feb. 2, 2018

Feb. 2, 2018

https://bugs.winehq.org/show_bug.cgi?id=44158 Bug ID: 44158 Summary: QueryProcessCycleTime() causing exception/crash Product: Wine Version: 2.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: aj664(a)hotmail.com Distribution: --- it's got a ok/fail return value, so if it's not implemented, it should be a no-op FIXME thingy, returning a fail value. or is it actually implemented, and just crashes?!? OS.. up-to-date Lubuntu x86-64 running in a Virtual Box v5.1.20 VM. -- 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