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

[Bug 46442] New: FormatCurrency(9) returns .9.00 (period in front)
by wine-bugs＠winehq.org May 15, 2019

May 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=46442 Bug ID: 46442 Summary: FormatCurrency(9) returns .9.00 (period in front) Product: Wine Version: 4.0-rc5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine(a)londonlight.org Distribution: --- Created attachment 63224 --> https://bugs.winehq.org/attachment.cgi?id=63224 compiled executable Reproduced in wine-3.0.4 in Linux Mint, wine-3.18-staging in Sabayon (from its package manager) as well as self-compiled (vanilla) wine-3.21-298-ge9231beb86 and wine-4.0-rc5-14-g0ff7fd1259 FormatCurrency(9) returns ".9.00", notice the period in the front. Therefore, FormatCurrency(FormatCurrency(9)) will segfault. Why does it add the period there? Compiled exe attached, source code zipped and attached in next comment. Steps: 1. Get winetricks: wget https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetric… 2. Install vb6run: WINEARCH=win32 WINEPREFIX="$HOME/wine-ct" ~/winetricks vb6run 3. Run currencytest.exe LC_ALL="en_US.utf8" WINEPREFIX="$HOME/wine-ct" currencytest.exe -- 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 45473] New: Rogue Squadron 3D crashes on startup
by wine-bugs＠winehq.org May 15, 2019

May 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=45473 Bug ID: 45473 Summary: Rogue Squadron 3D crashes on startup Product: Wine Version: 3.12 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-dsound Assignee: wine-bugs(a)winehq.org Reporter: leslie_alistair(a)hotmail.com Distribution: --- Created attachment 61818 --> https://bugs.winehq.org/attachment.cgi?id=61818 Dont destroy secondarybuffer in IDirectSoundNotify Rogue Squadron 3D crashes on startup unless native dsound is used -- 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 11

[Bug 46691] New: comctl32/tests/propsheet.c shows uninitalized memory use
by wine-bugs＠winehq.org May 15, 2019

May 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=46691 Bug ID: 46691 Summary: comctl32/tests/propsheet.c shows uninitalized memory use Product: Wine Version: 4.2 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com CC: bunglehead(a)gmail.com Distribution: Gentoo ../../../tools/runtest -q -P wine -T ../../.. -M comctl32.dll -p comctl32_test.exe.so propsheet && touch propsheet.ok ==30493== Syscall param write(buf) points to uninitialised byte(s) ==30493== at 0x4253C7F: write (write.c:27) ==30493== by 0x7BC75AAB: send_request (server.c:213) ==30493== by 0x7BC767F0: server_call_unlocked (server.c:288) ==30493== by 0x7BC76845: wine_server_call (server.c:321) ==30493== by 0x4FA5FFD: PostQuitMessage (message.c:3762) ==30493== by 0x5975F8E: do_loop (propsheet.c:2781) ==30493== by 0x5976031: PROPSHEET_PropertySheet (propsheet.c:2815) ==30493== by 0x5976612: PropertySheetA (propsheet.c:2865) ==30493== by 0x4AE4E8F: test_bad_control_class (propsheet.c:1167) ==30493== by 0x4AE82D7: func_propsheet (propsheet.c:1208) ==30493== by 0x4B2C64C: run_test (test.h:617) ==30493== by 0x4B2D08A: main (test.h:701) ==30493== Address 0x4c6fb58 is on thread 1's stack ==30493== in frame #4, created by PostQuitMessage (message.c:3758) ==30493== Uninitialised value was created by a stack allocation ==30493== at 0x5975EC4: do_loop (propsheet.c:2762) ==30493== -- 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 46493] New: Functions ilogb* are not implemented
by wine-bugs＠winehq.org May 15, 2019

May 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=46493 Bug ID: 46493 Summary: Functions ilogb* are not implemented Product: Wine Version: 4.0-rc7 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: bunglehead(a)gmail.com Distribution: --- Created attachment 63331 --> https://bugs.winehq.org/attachment.cgi?id=63331 patch This was reported via #winehq, application name wasn't mentioned. -- 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 46485] New: clrmamepro: crash when loading datfiles which contains release elements
by wine-bugs＠winehq.org May 15, 2019

May 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=46485 Bug ID: 46485 Summary: clrmamepro: crash when loading datfiles which contains release elements Product: Wine Version: 4.0-rc7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: tomgpdev(a)gmail.com Distribution: --- Created attachment 63322 --> https://bugs.winehq.org/attachment.cgi?id=63322 Crafted .dat file and the crash backtrace The app crashes when trying to load LogiqX .DAT files which has "release" elements inside the "game" elements. From the stack trace, it see something about comctl32, but I don't know the reason about the crash itself. For you to trigger the crash, I crafted an example .dat file. Here's the procedure: 1. Download clrmame pro. 2. Copy the crash.dat file inside its datfiles dir. 3. Run clrmame pro. 4. Click OK in the welcome screen. 5. In [NEW DATAFILES], double click on "Crash test". 6. Click on "Default". 7. The crash should happen. I checked on Windows 10 that it loads the crafted crash.dat file attached to this bug report without crashing. AppDB link: https://appdb.winehq.org/objectManager.php?sClass=application&iId=5692 Program version: 4.035 64 bits -- 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 12

[Bug 23863] New: The Bard's Tale (2005): unplayable due to almost completely black screen
by wine-bugs＠winehq.org May 15, 2019

May 15, 2019

http://bugs.winehq.org/show_bug.cgi?id=23863 Summary: The Bard's Tale (2005): unplayable due to almost completely black screen Product: Wine Version: 1.3.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Created an attachment (id=29959) --> (http://bugs.winehq.org/attachment.cgi?id=29959) terminal output (without any dll overrides) After starting The Bard's Tale (published in 2005 by inXile Entertainment) the screen in the menus is way too dark, so you can see almost nothing, unless you turn up the gamma of the screen. The animated hero is also missing on the left side of the screen, when you choose to generate a new character. The biggest problem that makes the game unplayable is when you start a new game, almost the whole screen is black, only the mini-map is shown in the upper-right corner, and the health bar in the upper-left corner. Besides only subtitles are shown. Majority of the screen is pure black. This bug affects at least the Steam version of the game, but according to AppDB the retail (DVD version) is also affected: http://appdb.winehq.org/objectManager.php?sClass=version&iId=4041 I tried out several Wine versions but all of them showed the same issue, including 1.1.0 which received Gold rating on AppDB. However, the demo version of the game has no such issues: it displays everything correctly, from the menus to the actual gameplay. The only difference between the terminal output of the demo (working one) and the retail version is the following line (repeated several times) when playing the retail version: 'fixme:d3d:buffer_PreLoad Too many full buffer conversions, stopping converting' Wine-1.3.0 Fedora 13 Nvidia 7600 GT card / driver 195.36.31 -- 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 40

[Bug 46729] New: Wine directx not detecting Intel HD Graphics 620 (Rev 02) chipset
by wine-bugs＠winehq.org May 15, 2019

May 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=46729 Bug ID: 46729 Summary: Wine directx not detecting Intel HD Graphics 620 (Rev 02) chipset Product: Wine Version: 4.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)darkhelm.org Distribution: --- Created attachment 63708 --> https://bugs.winehq.org/attachment.cgi?id=63708 GPU Caps Viewer screenshot (from within Wine) Wine is not identifying my card. >From lspci -nn | grep VGA: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) Yet when I run GPU Caps Viewer, it cannot determine my card. When I run WoW, it lists my card info as: 2/20 08:35:39.152 Vendor ID: 8086 2/20 08:35:39.916 Device ID: 162 Which is an Intel HD Graphics 4000, an older card -- apparently a "fallback" card used by Blizzard when it cannot determine the card information. This is preventing games from being able to use vkd3d. -- 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 15

[Bug 31954] New: Second Sight hangs with a black screen after the intro videos
by wine-bugs＠winehq.org May 15, 2019

May 15, 2019

http://bugs.winehq.org/show_bug.cgi?id=31954 Bug #: 31954 Summary: Second Sight hangs with a black screen after the intro videos Product: Wine Version: 1.5.15 Platform: x86 URL: http://www.gamershell.com/download_8848.shtml OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Classification: Unclassified Created attachment 42105 --> http://bugs.winehq.org/attachment.cgi?id=42105 plain terminal output According to the test results on AppDB, this game probably never worked in Wine, yet, no one has reported the problem here. The problem can be reproduced with the demo version as well, so I decided to file a bug report. The game starts with a couple of intro videos, then comes a black screen with a greyish loading bar at the bottom and the game freezes there. Wineserver and secondsight.exe together are consuming 100% CPU power, so something is happening 'under the hood', but the game never finishes loading. Steps to reproduce the problem with the demo version: 1. create a new wineprefix 2. winetricks ie6 3. start the installed demo with secondsight.exe. In the launcher click <Start Free Trial>, wait for the videos to end...the game is hanging with a black screen after the videos. Fedora 17 Nvidia 250 / driver 304.51 -- 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 47

[Bug 46907] New: msi crashes processing a RemoveFile table with an invalid directory
by wine-bugs＠winehq.org May 15, 2019

May 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=46907 Bug ID: 46907 Summary: msi crashes processing a RemoveFile table with an invalid directory Product: Wine Version: 4.4 Hardware: x86 OS: Linux Status: NEW Severity: minor Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: madewokherd(a)gmail.com Distribution: --- This is just something I noticed while splitting up the Wine Mono msi. The action should probably fail without crashing. Backtrace: =>0 0x00007f455c7853c8 remove_folder+0x8(folder=(nil)) [/home/meh/work/wine/wine64/dlls/msi/../../../dlls/msi/files.c:1549] in msi (0x00000000000a1580) 1 0x00007f455c78a350 ACTION_RemoveFiles+0x1ef(package=0xa1580) [/home/meh/work/wine/wine64/dlls/msi/../../../dlls/msi/files.c:1648] in msi (0x00000000000a1580) 2 0x00007f455c74c330 ACTION_HandleStandardAction+0x16f(package=0xa1580, action="RemoveFiles") [/home/meh/work/wine/wine64/dlls/msi/../../../dlls/msi/action.c:7980] in msi (0x00000000000c63c0) 3 0x00007f455c75d298 ACTION_PerformAction+0x27() in msi (0x00000000000b1f10) 4 0x00007f455c75d7b6 execute_script+0x115(package=0xa1580, script=0x2) [/home/meh/work/wine/wine64/dlls/msi/../../../dlls/msi/action.c:1543] in msi (0x00000000000b1f10) 5 0x00007f455c75e5d3 MSI_InstallPackage+0x4f2(package=0xa1580, szPackagePath=<is not available>, szCommandLine=<is not available>) [/home/meh/work/wine/wine64/dlls/msi/../../../dlls/msi/action.c:8178] in msi (0x00000000000b1f10) 6 0x00007f455c79a5c2 MsiInstallProductW+0x1e1(szPackagePath="image/support/winemono-support.msi", szCommandLine=0x0(nil)) [/home/meh/work/wine/wine64/dlls/msi/../../../dlls/msi/msi.c:268] in msi (0x000000000022fa10) -- 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 46318] New: vbscript doesn' t parse if identifier is also keyword token
by wine-bugs＠winehq.org May 15, 2019

May 15, 2019

https://bugs.winehq.org/show_bug.cgi?id=46318 Bug ID: 46318 Summary: vbscript doesn't parse if identifier is also keyword token Product: Wine Version: 4.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: vbscript Assignee: wine-bugs(a)winehq.org Reporter: brendan(a)redmandi.com Distribution: --- Created attachment 63051 --> https://bugs.winehq.org/attachment.cgi?id=63051 Treat all tokens after immediately following a '.' as identifier The following vbscript currently fails with a parsing error: Set oLocator = CreateObject("Wbemscripting.SWbemLocator") Set oReg = oLocator.ConnectServer("", "root\default", "", "").Get("StdRegProv") The issue appears to be using a method named 'Get' which is also one of the tokens used in the parse. I was able to fix this by modifying the parse to treat any value immediately after a '.' as an identifier. Although I'm not familiar enough with vbscript syntax to know if this will cause any other issues. The patch used is attached. -- 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