wine-bugs March 2019

wine-bugs@winehq.org

1 participants
7773 discussions

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

15 May '19

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 15 May '19

15 May '19

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 15 May '19

15 May '19

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 15 May '19

15 May '19

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 15 May '19

15 May '19

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 15 May '19

15 May '19

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 15 May '19

15 May '19

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 15 May '19

15 May '19

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

[Bug 28140] New: theatre of war 3 korea Demo does not start
by wine-bugs＠winehq.org 15 May '19

15 May '19

http://bugs.winehq.org/show_bug.cgi?id=28140 Summary: theatre of war 3 korea Demo does not start Product: Wine Version: 1.3.26 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lill.guill(a)gmail.com Hello, Theatre of war 3 korea Demo does not start. fixme:exec:SHELL_execute flags ignored: 0x00000100 fixme:exec:SHELL_execute flags ignored: 0x00004100 fixme:wintrust:WinVerifyTrust unimplemented for 11088336 wine: Unhandled page fault on read access to 0x7ff8b2d0 at address 0x7ff8b2d0 (thread 0026), starting debugger... Unhandled exception: page fault on read access to 0x7ff8b2d0 in 32-bit code (0x7ff8b2d0). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:7ff8b2d0 ESP:0033fc08 EBP:0033fc10 EFLAGS:00010246( R- -- I Z- -P- ) EAX:00d4b600 EBX:00000000 ECX:00000000 EDX:00d4a660 ESI:00d4b640 EDI:00a8040c Stack dump: 0x0033fc08: 7ffc0592 00000000 0033fc64 00a7ffe6 0x0033fc18: 00a8040c 0033fc28 00a455f0 0033fc64 0x0033fc28: 0033fc98 00a455f0 0033fc64 00a8040c 0x0033fc38: 00d4b640 00d4b640 00000000 00000000 0x0033fc48: 00000000 00000000 00d3e240 00000000 0x0033fc58: 00000000 00000000 00000000 0033fc8c Backtrace: =>0 0x7ff8b2d0 (0x0033fc10) 1 0x00a7ffe6 in korea (+0x67ffe5) (0x0033fc64) 2 0x00a7840d in korea (+0x67840c) (0x0033fc8c) 3 0x00a803c5 in korea (+0x6803c4) (0x0033fcf0) 4 0x00a968d4 in korea (+0x6968d3) (0x0033fdbc) 5 0x00a9ca48 in korea (+0x69ca47) (0x0033fdec) 6 0x00a9d10d in korea (+0x69d10c) (0x0033fe1c) 7 0x00a9d363 in korea (+0x69d362) (0x0033fe7c) 8 0x0040127d in korea (+0x127c) (0x0033fe90) 9 0x7b85aa7c call_process_entry+0xb() in kernel32 (0x0033fea8) 10 0x7b85df4b in kernel32 (+0x4df4a) (0x0033fee8) 11 0x7bc71358 call_thread_func+0xb() in ntdll (0x0033fef8) 12 0x7bc7152e in ntdll (+0x6152d) (0x0033ffc8) 13 0x7bc4bd8e in ntdll (+0x3bd8d) (0x0033ffe8) 0x7ff8b2d0: addb %al,0x0(%eax) Modules: Module Address Debug info Name (71 modules) PE 400000- ad8000 Export korea ELF 7b800000-7b9aa000 Dwarf kernel32<elf> \-PE 7b810000-7b9aa000 \ kernel32 ELF 7bc00000-7bcc1000 Dwarf ntdll<elf> \-PE 7bc10000-7bcc1000 \ ntdll ELF 7bf00000-7bf04000 Deferred <wine-loader> ELF 7e089000-7e09d000 Deferred psapi<elf> \-PE 7e090000-7e09d000 \ psapi ELF 7e09d000-7e0b1000 Deferred shfolder<elf> \-PE 7e0a0000-7e0b1000 \ shfolder ELF 7e113000-7e147000 Deferred uxtheme<elf> \-PE 7e120000-7e147000 \ uxtheme ELF 7e147000-7e23a000 Deferred comctl32<elf> \-PE 7e150000-7e23a000 \ comctl32 ELF 7e23a000-7e2a4000 Deferred shlwapi<elf> \-PE 7e250000-7e2a4000 \ shlwapi ELF 7e2a4000-7e4af000 Deferred shell32<elf> \-PE 7e2b0000-7e4af000 \ shell32 ELF 7e4af000-7e55d000 Deferred crypt32<elf> \-PE 7e4c0000-7e55d000 \ crypt32 ELF 7e55d000-7e590000 Deferred wintrust<elf> \-PE 7e560000-7e590000 \ wintrust ELF 7e590000-7e606000 Deferred rpcrt4<elf> \-PE 7e5a0000-7e606000 \ rpcrt4 ELF 7e606000-7e70d000 Deferred ole32<elf> \-PE 7e620000-7e70d000 \ ole32 ELF 7e70d000-7e800000 Deferred oleaut32<elf> \-PE 7e720000-7e800000 \ oleaut32 ELF 7e800000-7e80a000 Deferred libxcursor.so.1 ELF 7e80a000-7e818000 Deferred libxi.so.6 ELF 7e818000-7e81e000 Deferred libxfixes.so.3 ELF 7e81e000-7e822000 Deferred libxcomposite.so.1 ELF 7e822000-7e82a000 Deferred libxrandr.so.2 ELF 7e82a000-7e834000 Deferred libxrender.so.1 ELF 7e834000-7e83a000 Deferred libxxf86vm.so.1 ELF 7e83a000-7e83e000 Deferred libxinerama.so.1 ELF 7e83e000-7e860000 Deferred imm32<elf> \-PE 7e840000-7e860000 \ imm32 ELF 7e860000-7e866000 Deferred libxdmcp.so.6 ELF 7e866000-7e86a000 Deferred libxau.so.6 ELF 7e86a000-7e884000 Deferred libxcb.so.1 ELF 7e884000-7e889000 Deferred libuuid.so.1 ELF 7e889000-7e9a6000 Deferred libx11.so.6 ELF 7e9a6000-7e9b6000 Deferred libxext.so.6 ELF 7e9b6000-7e9cf000 Deferred libice.so.6 ELF 7e9cf000-7e9d8000 Deferred libsm.so.6 ELF 7e9fc000-7eaa4000 Deferred winex11<elf> \-PE 7ea10000-7eaa4000 \ winex11 ELF 7ead9000-7eb00000 Deferred libexpat.so.1 ELF 7eb00000-7eb30000 Deferred libfontconfig.so.1 ELF 7eb30000-7eb45000 Deferred libz.so.1 ELF 7eb45000-7ebbb000 Deferred libfreetype.so.6 ELF 7ebdf000-7ec40000 Deferred advapi32<elf> \-PE 7ebf0000-7ec40000 \ advapi32 ELF 7ec40000-7ece4000 Deferred gdi32<elf> \-PE 7ec50000-7ece4000 \ gdi32 ELF 7ece4000-7ee21000 Deferred user32<elf> \-PE 7ed00000-7ee21000 \ user32 ELF 7ee21000-7ee2d000 Deferred libnss_files.so.2 ELF 7ee2d000-7ee35000 Deferred libnss_compat.so.2 ELF 7ee40000-7ee59000 Deferred version<elf> \-PE 7ee50000-7ee59000 \ version ELF 7efb6000-7efdc000 Deferred libm.so.6 ELF 7efdf000-7efe9000 Deferred libnss_nis.so.2 ELF 7efe9000-7f000000 Deferred libnsl.so.1 ELF f7429000-f742d000 Deferred libdl.so.2 ELF f742d000-f7587000 Deferred libc.so.6 ELF f7588000-f75a1000 Deferred libpthread.so.0 ELF f75c5000-f7706000 Dwarf libwine.so.1 ELF f7708000-f7726000 Deferred ld-linux.so.2 ELF f7726000-f7727000 Deferred [vdso].so Threads: process tid prio (all id:s are in hex) 0000000e services.exe 00000021 0 0000001c 0 00000016 0 00000015 0 00000014 0 00000010 0 0000000f 0 00000011 winedevice.exe 00000018 0 00000017 0 00000013 0 00000012 0 00000019 plugplay.exe 0000001d 0 0000001b 0 0000001a 0 0000001e winedevice.exe 00000022 0 00000020 0 0000001f 0 00000023 explorer.exe 00000024 0 00000025 (D) C:\Program Files\Battlefront\1C Company\Theatre of War 3 Korea - Trial Version\Korea.exe 00000026 0 <== Backtrace: =>0 0x7ff8b2d0 (0x0033fc10) 1 0x00a7ffe6 in korea (+0x67ffe5) (0x0033fc64) 2 0x00a7840d in korea (+0x67840c) (0x0033fc8c) 3 0x00a803c5 in korea (+0x6803c4) (0x0033fcf0) 4 0x00a968d4 in korea (+0x6968d3) (0x0033fdbc) 5 0x00a9ca48 in korea (+0x69ca47) (0x0033fdec) 6 0x00a9d10d in korea (+0x69d10c) (0x0033fe1c) 7 0x00a9d363 in korea (+0x69d362) (0x0033fe7c) 8 0x0040127d in korea (+0x127c) (0x0033fe90) 9 0x7b85aa7c call_process_entry+0xb() in kernel32 (0x0033fea8) 10 0x7b85df4b in kernel32 (+0x4df4a) (0x0033fee8) 11 0x7bc71358 call_thread_func+0xb() in ntdll (0x0033fef8) 12 0x7bc7152e in ntdll (+0x6152d) (0x0033ffc8) 13 0x7bc4bd8e in ntdll (+0x3bd8d) (0x0033ffe8) -- 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 29

[Bug 46708] New: Photoline crashed right after start, no problem with wine 3.0.4
by wine-bugs＠winehq.org 15 May '19

15 May '19

https://bugs.winehq.org/show_bug.cgi?id=46708 Bug ID: 46708 Summary: Photoline crashed right after start, no problem with wine 3.0.4 Product: Wine Version: 4.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: k8auf1947(a)cometchaser.de Distribution: --- Created attachment 63676 --> https://bugs.winehq.org/attachment.cgi?id=63676 Backtrace from Wine after Photoline crashed The application Photoline 16.50 crashes after start. This happens only with the new Wine 4.0. Happens on two different PC's with Linux Debian Stable. Both working with the same Wine 4.0. The application worked great with Wine 3.0.4 -- 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

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 March 2019