December 2018 - Wine-bugs - list.winehq.org

[Bug 42711] New: Program AntiDupl.net does not start.
by wine-bugs＠winehq.org 13 Nov '20

13 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=42711 Bug ID: 42711 Summary: Program AntiDupl.net does not start. Product: Wine Version: 2.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: trym(a)2.pl Distribution: --- Created attachment 57687 --> https://bugs.winehq.org/attachment.cgi?id=57687 Details of program error. The problem is with software that searches for repetitive pictures named AntiDupl.NET in version-2.3.8.http://antidupl.sourceforge.net/english/index.html?page=downl… The program does not start. -- 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 43409] New: Banished won't run on FreeBSD ( failed to initialize the memory allocator!)
by wine-bugs＠winehq.org 13 Nov '20

13 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=43409 Bug ID: 43409 Summary: Banished won't run on FreeBSD (failed to initialize the memory allocator!) Product: Wine Version: 2.10 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adrien_fernandes2(a)hotmail.com I'm running FreeBSD 11.0-RELEASE-p1 amd64 and I am using Wine staging 2.10 i386. When I try to run Banished, I have a little window saying : A fatal error has occured and the application cannot continue. Memory: The application failed to initialize the memory allocator! The only message I have in the terminal, after the usual "consider using nouveau instead", is : err:ole:CoUninitialize Mismatched CoUninitialize I don't know if it is linked to my 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 1

[Bug 40233] New: Devil Daggers Refuses to Start
by wine-bugs＠winehq.org 13 Nov '20

13 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=40233 Bug ID: 40233 Summary: Devil Daggers Refuses to Start Product: Wine Version: 1.9.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tristanlshockley(a)gmail.com Distribution: --- Created attachment 53778 --> https://bugs.winehq.org/attachment.cgi?id=53778 Devil Dagger Force Close Output I created a thread in the forums (https://forum.winehq.org/viewtopic.php?f=8&t=26228) where I was recommended to create a bug report. To get to this point I needed lib32-openal. After installing samba a winbind error was removed (see the forum link) but this doesn't appear to change anything. The game will not start through terminal because of DRM, you need to run the game through Steam in WINE. When you do so you will see a black box which will autoclose in about five seconds. Attached is the text Steam spits out during this time, and if I can figure out how to post another I will provide an image of the black box. -- 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 12

[Bug 40928] New: Sword of the Stars: The Pit Gold Edition (.NET 4.0/XNA) crashes with a SIGSEGV when using wine-mono
by wine-bugs＠winehq.org 13 Nov '20

13 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=40928 Bug ID: 40928 Summary: Sword of the Stars: The Pit Gold Edition (.NET 4.0/XNA) crashes with a SIGSEGV when using wine-mono Product: Wine Version: 1.9.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fjfrackiewicz(a)gmail.com Distribution: --- Created attachment 55038 --> https://bugs.winehq.org/attachment.cgi?id=55038 Terminal output for Wine-1.9.13-114-gb1930ee Windows XP mode Windows XP mode, clean 32-bit prefix. After installing the GOG version of Sword of the Stars: The Pit Gold Edition and running "wine ThePit.exe" I am greeted with what appears to be a wine-mono crash. Wine-mono 4.6.3 is installed. -- 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 7

[Bug 45536] New: Total Commander 9.x crashes on unimplemented function usp10.dll.ScriptGetFontAlternateGlyphs when Wine is not detected
by wine-bugs＠winehq.org 10 Nov '20

10 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=45536 Bug ID: 45536 Summary: Total Commander 9.x crashes on unimplemented function usp10.dll.ScriptGetFontAlternateGlyphs when Wine is not detected Product: Wine Version: 3.13 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: usp10 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, while investigating bug 45514 (dupe of bug 42497) my Total Commander 9.x installation stopped working because I made 'wine_get_version' a '-noname' ordinal export (cheaper way, to avoid using Wine-Staging/patchset). The app no longer detects Wine and runs into a problem. Download: https://totalcommander.ch/win/tcmd920x64.exe --- snip --- $ pwd /home/focht/wineprefix64-tcmd/drive_c/totalcmd $ file *.{DLL,EXE} TC7Z64.DLL: PE32+ executable (DLL) (GUI) x86-64, for MS Windows TCLZMA64.DLL: PE32+ executable (DLL) (GUI) x86-64, for MS Windows TCUNZL64.DLL: PE32+ executable (DLL) (GUI) x86-64, for MS Windows UNRAR64.DLL: PE32+ executable (DLL) (console) x86-64, for MS Windows WCMICON2.DLL: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows WCMICONS.DLL: PE32 executable (GUI) Intel 80386, for MS Windows WCMZIP64.DLL: PE32+ executable (DLL) (GUI) x86-64, for MS Windows NOCLOSE64.EXE: PE32+ executable (GUI) x86-64, for MS Windows TCMADM64.EXE: PE32+ executable (GUI) x86-64, for MS Windows TCMDX32.EXE: PE32 executable (GUI) Intel 80386, for MS Windows TCUNIN64.EXE: PE32+ executable (GUI) x86-64, for MS Windows TOTALCMD64.EXE: PE32+ executable (GUI) x86-64, for MS Windows $ WINEDEBUG=+seh,+relay wine TOTALCMD64.EXE >>log.txt 2>&1 ... 0030:Call KERNEL32.GetProcAddress(7bc80000,00a8a890 "wine_get_version") ret=00474dbb 0030:Ret KERNEL32.GetProcAddress() retval=00000000 ret=00474dbb ... 0030:Ret usp10.ScriptItemize() retval=00000000 ret=009f4047 0030:Call usp10.ScriptShape(00250258,00bd1bc0,01cb9768,00000001,00000010,00099634,02f35050,02f35090,02f350d0,0037693c) ret=009f40d1 ... 0030:Ret usp10.ScriptShape() retval=00000000 ret=009f40d1 0030:Call KERNEL32.RaiseException(80000100,00000001,00000002,01cb96a0) ret=7fe6fee5eb50 0030:trace:seh:NtRaiseException code=80000100 flags=1 addr=0x7b4944b9 ip=7b4944b9 tid=0030 0030:trace:seh:NtRaiseException info[0]=00007fe6fee5eb80 0030:trace:seh:NtRaiseException info[1]=00007fe6fee5eb95 wine: Call from 0x7b4944b9 to unimplemented function usp10.dll.ScriptGetFontAlternateGlyphs, aborting 0030:trace:seh:call_vectored_handlers calling handler at 0x419950 code=80000100 flags=1 ... --- snip --- Source: https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/usp10/usp10.spec#l9 --- snip --- 9 @ stub ScriptGetFontAlternateGlyphs --- snip --- Microsoft docs: https://docs.microsoft.com/en-us/windows/desktop/api/usp10/nf-usp10-scriptg… $ sha1sum tcmd920x64.exe d27abd02fe60002cfb60b1c68888a666c48c9142 tcmd920x64.exe $ du -sh tcmd920x64.exe 5.0M tcmd920x64.exe $ wine --version wine-3.13 Regards -- 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 8

[Bug 35903] New: CED1401 Device connected through USB not found
by wine-bugs＠winehq.org 10 Nov '20

10 Nov '20

http://bugs.winehq.org/show_bug.cgi?id=35903 Bug ID: 35903 Summary: CED1401 Device connected through USB not found Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com The CED1401 is a devices which connected with USB to the PC. The software for controlling the device installs and runs well, but it does not identify the USB device. For this reason, the application "CED1401" in Winehq's AppDB has currently status "Garbage". -- 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 37

[Bug 44127] New: Metal Gear Solid V: Ground Zeroes doesn't launch
by wine-bugs＠winehq.org 10 Nov '20

10 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=44127 Bug ID: 44127 Summary: Metal Gear Solid V: Ground Zeroes doesn't launch Product: Wine Version: 2.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 59865 --> https://bugs.winehq.org/attachment.cgi?id=59865 +seh Game crashes at launch. 00e2:err:seh:NtRaiseException Unhandled exception code 80000003 flags 0 addr 0x7bc8e34d wine-2.22-158-g47e9e911ac -- 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 8

[Bug 44925] New: StarForce v3 kernel driver service 'sfhlp02' fails in driver entry point due to 'ntoskrnl.exe.ExCreateCallback' stub ( needs STATUS_SUCCESS)
by wine-bugs＠winehq.org 10 Nov '20

10 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=44925 Bug ID: 44925 Summary: StarForce v3 kernel driver service 'sfhlp02' fails in driver entry point due to 'ntoskrnl.exe.ExCreateCallback' stub (needs STATUS_SUCCESS) Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 44924 --- snip --- ... 0035:Call driver init 0x785300 (obj=0x11caf0,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\sfhlp02") ... 035:Call ntoskrnl.exe.IoCreateSynchronizationEvent(0065fc80,0065fc8c) ret=00785414 0035:fixme:ntoskrnl:IoCreateSynchronizationEvent (0x65fc80 0x65fc8c) stub 0035:Ret ntoskrnl.exe.IoCreateSynchronizationEvent() retval=cafebabe ret=00785414 0035:Call ntoskrnl.exe.KeEnterCriticalRegion() ret=0078542c 0035:fixme:ntoskrnl:KeEnterCriticalRegion : stub 0035:Ret ntoskrnl.exe.KeEnterCriticalRegion() retval=00000031 ret=0078542c 0035:Call ntoskrnl.exe.KeWaitForSingleObject(cafebabe,00000000,00000000,00000000,00000000) ret=00785437 0035:fixme:ntoskrnl:KeWaitForSingleObject stub: 0xcafebabe, 0, 0, 0, (nil) 0035:Ret ntoskrnl.exe.KeWaitForSingleObject() retval=c0000002 ret=00785437 0035:Call ntoskrnl.exe.RtlInitUnicodeString(0065fc78,007853ac L"\\Callback\\StarForceCreateThread") ret=00785442 0035:Call ntdll.RtlInitUnicodeString(0065fc78,007853ac L"\\Callback\\StarForceCreateThread") ret=7bc7f41b 0035:Ret ntdll.RtlInitUnicodeString() retval=0065fc78 ret=7bc7f41b 0035:Ret ntoskrnl.exe.RtlInitUnicodeString() retval=0065fc78 ret=00785442 0035:Call ntoskrnl.exe.ExCreateCallback(0065fc88,0065fc60,00000000,00000001) ret=00785472 0035:fixme:ntoskrnl:ExCreateCallback (0x65fc88, 0x65fc60, 0, 1): stub 0035:Ret ntoskrnl.exe.ExCreateCallback() retval=c0000002 ret=00785472 0035:Call ntoskrnl.exe.ZwClose(00783014) ret=007854ee 0035:Call ntdll.NtClose(00783014) ret=7bc7f41b 0035:Ret ntdll.NtClose() retval=c0000008 ret=7bc7f41b 0035:Ret ntoskrnl.exe.ZwClose() retval=c0000008 ret=007854ee 0035:Call ntoskrnl.exe.KeLeaveCriticalRegion() ret=007854f4 0035:fixme:ntoskrnl:KeLeaveCriticalRegion : stub 0035:Ret ntoskrnl.exe.KeLeaveCriticalRegion() retval=00000031 ret=007854f4 0035:Call ntoskrnl.exe.IoAllocateErrorLogEntry(0011caf0,00000030) ret=0078103a 0035:fixme:ntoskrnl:IoAllocateErrorLogEntry stub: 0x11caf0, 48 0035:Ret ntoskrnl.exe.IoAllocateErrorLogEntry() retval=00000000 ret=0078103a ... 0035:Ret driver init 0x785300 (obj=0x11caf0,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\sfhlp02") retval=c0000002 ... 0035:Ret ntoskrnl.exe.IoCreateDriver() retval=c0000002 ret=7effb786 0035:err:winedevice:async_create_driver failed to create driver L"sfhlp02": c0000002 --- snip --- With a patch applied, the driver entry point is successfully executed: --- snip --- ... 0036:Call driver init 0x785300 (obj=0x11cbb0,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\sfhlp02") ... 0036:Call ntoskrnl.exe.RtlInitUnicodeString(0065fc78,007853ac L"\\Callback\\StarForceCreateThread") ret=00785442 0036:Call ntdll.RtlInitUnicodeString(0065fc78,007853ac L"\\Callback\\StarForceCreateThread") ret=7bc7f41b 0036:Ret ntdll.RtlInitUnicodeString() retval=0065fc78 ret=7bc7f41b 0036:Ret ntoskrnl.exe.RtlInitUnicodeString() retval=0065fc78 ret=00785442 0036:Call ntoskrnl.exe.ExCreateCallback(0065fc88,0065fc60,00000000,00000001) ret=00785472 0036:fixme:ntoskrnl:ExCreateCallback (0x65fc88, 0x65fc60, 0, 1): stub 0036:Ret ntoskrnl.exe.ExCreateCallback() retval=00000000 ret=00785472 ... 0036:Call ntoskrnl.exe.KeLeaveCriticalRegion() ret=0078551a 0036:fixme:ntoskrnl:KeLeaveCriticalRegion : stub 0036:Ret ntoskrnl.exe.KeLeaveCriticalRegion() retval=00000031 ret=0078551a 0036:Ret driver init 0x785300 (obj=0x11cbb0,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\sfhlp02") retval=00000000 0036:Ret ntoskrnl.exe.IoCreateDriver() retval=00000000 ret=7effb786 0036:Call ntoskrnl.exe.ObReferenceObjectByName(0065fdc0,00000040,00000000,00000000,00000000,00000000,00000000,0065fdc8) ret=7effb810 0036:trace:ntoskrnl:ObReferenceObjectByName mostly-stub:L"\\Driver\\sfhlp02" 64 (nil) 0 (nil) 0 (nil) 0x65fdc8 0036:Call ntdll.RtlCompareUnicodeString(0065fdc0,0011cbcc,00000000) ret=7ec13108 0036:Ret ntdll.RtlCompareUnicodeString() retval=00000000 ret=7ec13108 0036:Ret ntoskrnl.exe.ObReferenceObjectByName() retval=00000000 ret=7effb810 ... 0036:Call KERNEL32.SetEvent(0000003c) ret=7effb88e 0036:Ret KERNEL32.SetEvent() retval=00000001 ret=7effb88e 0036:Call advapi32.SetServiceStatus(0011b7e0,0065fd84) ret=7effb3d9 --- snip --- $ sha1sum tmsunrisedemo_setup.exe 2d44577a71718464c595d9da91a017fb0914afc4 tmsunrisedemo_setup.exe $ du -sh tmsunrisedemo_setup.exe 210M tmsunrisedemo_setup.exe $ wine --version wine-3.5-91-g3263d51a1f Regards -- 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 44306] New: Visual Novel "A Clockwork Ley-Line: The Borderline of Dusk" doesn't work with d3d9
by wine-bugs＠winehq.org 10 Nov '20

10 Nov '20

https://bugs.winehq.org/show_bug.cgi?id=44306 Bug ID: 44306 Summary: Visual Novel "A Clockwork Ley-Line: The Borderline of Dusk" doesn't work with d3d9 Product: Wine Version: 3.0-rc4 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- The game simply doesn't start when directx is used. The console log stops, and nothing happens anymore. Issue happens with wine-3.0-rc4 and wine-staging-2.21. Complete log: -------- 006f:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub 006f:fixme:win:WINNLSEnableIME hwnd 0x70050 enable 0: stub! 006f:fixme:win:EnumDisplayDevicesW ((null),0,0x33f874,0x00000000), stub! 006f:fixme:d3d:wined3d_check_device_format_conversion wined3d 0x16ae38, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, src_format WINED3DFMT_B8G8R8A8_UNORM, dst_format WINED3DFMT_B8G8R8X8_UNORM stub! -------- When setting d3d9 to disabled in winecfg, the game starts up fine. Note: I'm using the non-steam version of the game. -- 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 9

[Bug 26171] New: wine fails to install BVRP classic phone tools
by wine-bugs＠winehq.org 10 Nov '20

10 Nov '20

http://bugs.winehq.org/show_bug.cgi?id=26171 Summary: wine fails to install BVRP classic phone tools Product: Wine Version: 1.3.14 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: axel.braun(a)gmx.de Created an attachment (id=33350) --> (http://bugs.winehq.org/attachment.cgi?id=33350) backtrace I try to install the BVRP classic phone tools ( http://www.avanquest.com/USA/software/classic-phonetools-9-27401 ) - use trial version to cross-check - to manage a USR 56K Message modem axel(a)southpole:/daten/linux/USRobotics/DEU> wine setup.exe wine: created the configuration directory '/home/axel/.wine' fixme:system:SetProcessDPIAware stub! fixme:iphlpapi:NotifyAddrChange (Handle 0x90fe914, overlapped 0x90fe918): stub wine: configuration in '/home/axel/.wine' has been updated. fixme:storage:create_storagefile Storage share mode not implemented. err:richedit:ReadStyleSheet skipping optional destination err:richedit:ReadStyleSheet skipping optional destination fixme:shell:IShellLinkA_fnGetPath (0x13198e8): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkA_fnGetPath (0x13198e8): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkA_fnGetPath (0x13184a8): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkA_fnGetPath (0x13184a8): WIN32_FIND_DATA is not yet filled. fixme:mixer:ALSA_MixerInit No master control found on HDA ATI HDMI, disabling mixer fixme:spoolsv:service_handler got service ctrl 4 -- at this point in the the installation asks for the C:\windows\Driver Cache\I386\ files. I redirect to the installation disk, and wine scans winsys32.cab. Afterwards the error message 'AddPrintProcessor: No enough buffer' is issued in a pop-up box When then starting the application, the assistant for device configuration is startet, and shows com1-com8 I see tons of messages: fixme:ntdll:server_ioctl_file Unsupported ioctl 24000 (device=2 access=1 func=0 method=0) fixme:winspool:OpenPrinterW PRINTER_DEFAULTS ignored => L"RAW",(nil),0x000f000c fixme:winspool:AddPrintProcessorA ((null),(null),"WfxPrint2000.dll","WfxPrint2000"): stub fixme:spoolsv:service_handler got service ctrl 4 fixme:rpc:handle_bind_error unexpected status value 1765 fixme:spoolsv:service_handler got service ctrl 4 fixme:shell:IShellLinkA_fnGetPath (0x13f9df0): WIN32_FIND_DATA is not yet filled. fixme:shell:IShellLinkA_fnGetPath (0x13f9df0): WIN32_FIND_DATA is not yet filled. axel(a)southpole:/daten/linux/USRobotics/DEU> fixme:win:AnimateWindow partial stub fixme:tapi:lineInitialize (0x33f83c, 0x820000, 0x83c200, (null), 0x33f880): stub. fixme:tapi:lineInitialize (0x33e83c, 0x820000, 0x83c200, (null), 0x33e880): stub. fixme:tapi:lineInitialize (0x33dff8, 0x820000, 0x83c200, (null), 0x33e03c): stub. fixme:tapi:lineInitialize (0x845948, 0x820000, 0x83c200, (null), 0x84598c): stub. fixme:setupapi:SetupDiLoadClassIcon : stub {4d36e978-e325-11ce-bfc1-08002be10318}, (nil), 0x33d468 fixme:setupapi:SetupDiLoadClassIcon : stub {4d36e978-e325-11ce-bfc1-08002be10318}, (nil), 0x33d468 fixme:setupapi:SetupDiLoadClassIcon : stub {4d36e978-e325-11ce-bfc1-08002be10318}, (nil), 0x33d468 fixme:setupapi:SetupDiLoadClassIcon : stub {4d36e978-e325-11ce-bfc1-08002be10318}, (nil), 0x33d468 fixme:comm:set_queue_size insize 16384 outsize 16384 unimplemented stub fixme:setupapi:SetupDiLoadClassIcon : stub {4d36e978-e325-11ce-bfc1-08002be10318}, (nil), 0x33b044 (etc) When starting the application manually, it tries to access the modem installed under /dev/ttyS0 as com1, which fails. axel(a)southpole:~/.wine> dir /dev/ttyS0 crw-rw---- 1 root dialout 4, 64 19. Feb 17:35 /dev/ttyS0 If I install without hardware check, and select the hardware manually from the list, an error message c:\windows\inf\mdmgen.inf not found If I contineu with the installation, phonetools.exe crashes - see backtrace. Any Idea what I could do to make the programm see the modem -- 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 15