wine-bugs July 2021

wine-bugs@winehq.org

1 participants
5027 discussions

[Bug 51341] New: incomplete Audio USB class compliant driver emulation / passthrough
by WineHQ Bugzilla 01 Jul '21

01 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51341 Bug ID: 51341 Summary: incomplete Audio USB class compliant driver emulation / passthrough Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: usb Assignee: wine-bugs(a)winehq.org Reporter: audioprof2002(a)hotmail.com Distribution: --- Story goes like this: Focusrite is currently the most popular manufacturer of home studio sound interfaces. has different products, Thunderbolt, USB, FireWire. but does Not care about Linux, Focusrite support is Not interested in Linux. https://support.focusrite.com/hc/en-gb/articles/208530735-Is-my-Focusrite-P… USB products (Scarlett and Clarett USB) are Class Compliant USB Devices, and sound in Linux. Kubuntu 20.10 Groovy Gorilla. also work in older OSX like Mavericks 10.9.5 alsamixer in terminal, works, but has No options. https://www.alsa-project.org/wiki/Matrix:Vendor-Focusrite Focusrite interfaces have lots of settings/configurations/routings for the built-in DSP, that can only be changed with the Focusrite Software. Focusrite v3.6.0 software works in PlayOnLinux and Wine 6.10 - 6.11, works, BUT..... Does Not detect the USB interface, and cannot change anything. Because: Wine requires a USB dummy / USB passthrough / USB emulator / translator driver to communicate with the interface. Wine needs to emulate the Focusrite windows USB driver, HW ID address, name, version, and route signals to Linux USB class compliant driver. for the Focusrite software to see & control the interface. Focusrite Clarett 8pre usb, Scarlett 18i20 mk2 mk3 are almost the same, have different exterior case, analog circuit components, different DAC but same drivers, same software that detects the different Firmware & serial numbers. to add or remove editable / controllable settings. https://fael-downloads-prod.focusrite.com/customer/prod/s3fs-public/downloa… https://customer.focusrite.com/en/support/downloads?brand=Focusrite&product… https://customer.focusrite.com/en/support/downloads?brand=Focusrite&product… https://customer.focusrite.com/en/support/downloads?brand=Focusrite&product… Asking ALSA to make a similar control software would require open source code released from Focusrite, thats why i think emulating the driver side is more easy, than making the whole software in Linux without access to source code. -- 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 51377] New: Driver binaries cross-compiled with MinGW (PE) have 'IMAGE_FILE_DLL' image characteristics set
by WineHQ Bugzilla 01 Jul '21

01 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=51377 Bug ID: 51377 Summary: Driver binaries cross-compiled with MinGW (PE) have 'IMAGE_FILE_DLL' image characteristics set Product: Wine Version: 6.11 Hardware: x86-64 OS: Linux Status: NEW Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, while investigating bug 51375 ("SCM erroneously tries to start 64-bit kernel drivers as 32-bit service due to incorrect handling of 'IMAGE_FILE_DLL' image characteristics in 'kernel32.dll.GetBinaryTypeW' (Protect DiSC 'acedrv11.sys'))", I've found another discrepancy: --- snip --- $ pwd /home/focht/.wine/drive_c/windows/system32/drivers $ file * acedrv11.sys: PE32+ executable (native) x86-64, for MS Windows etc: directory fltmgr.sys: PE32+ executable (DLL) (native) x86-64, for MS Windows hidclass.sys: PE32+ executable (DLL) (GUI) x86-64, for MS Windows http.sys: PE32+ executable (DLL) (native) x86-64, for MS Windows ksecdd.sys: PE32+ executable (DLL) (native) x86-64, for MS Windows mountmgr.sys: PE32+ executable (native) x86-64, for MS Windows ndis.sys: PE32+ executable (DLL) (native) x86-64, for MS Windows netio.sys: PE32+ executable (DLL) (native) x86-64, for MS Windows nsiproxy.sys: PE32+ executable (native) x86-64, for MS Windows scsiport.sys: PE32+ executable (DLL) (native) x86-64, for MS Windows tdi.sys: PE32+ executable (DLL) (native) x86-64, for MS Windows usbd.sys: PE32+ executable (DLL) (native) x86-64, for MS Windows winebus.sys: PE32+ executable (native) x86-64, for MS Windows winehid.sys: PE32+ executable (DLL) (native) x86-64, for MS Windows wineusb.sys: PE32+ executable (native) x86-64, for MS Windows --- snip --- All driver binaries which have been cross-compiled with MinGW (PE) have 'IMAGE_FILE_DLL' image characteristics set which is rather unusual. --- snip --- $ winedump http.sys Contents of http.sys: 49152 bytes *** This is a Wine builtin DLL *** File Header Machine: 8664 (AMD64) Number of Sections: 6 TimeDateStamp: 60DC03A9 (Wed Jun 30 07:39:53 2021) offset 128 PointerToSymbolTable: 00000000 NumberOfSymbols: 00000000 SizeOfOptionalHeader: 00F0 Characteristics: 2022 EXECUTABLE_IMAGE LARGE_ADDRESS_AWARE DLL ... --- snip --- Real native and Wine builtin 'fake' drivers are fine. https://source.winehq.org/git/wine.git/blob/0ec555e58ea9d5b33f4c825e96965ad… --- snip --- 1 MODULE = nsiproxy.sys 2 IMPORTS = ntoskrnl uuid 3 EXTRADLLFLAGS = -Wl,--subsystem,native --- snip --- vs. https://source.winehq.org/git/wine.git/blob/0ec555e58ea9d5b33f4c825e96965ad… --- snip --- 1 MODULE = http.sys 2 IMPORTS = ntoskrnl ws2_32 3 EXTRADLLFLAGS = -Wl,--subsystem,native -mno-cygwin --- snip --- This doesn't cause a problem in shared WoW64 prefixes under Linux but still could be addressed. $ wine --version wine-6.11-235-g7f1623bc626 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.

1 0

[Bug 49165] New: Crash when trying to open Veracrypt
by WineHQ Bugzilla 01 Jul '21

01 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=49165 Bug ID: 49165 Summary: Crash when trying to open Veracrypt Product: Wine Version: 5.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikrutrafal54(a)gmail.com Distribution: --- Created attachment 67184 --> https://bugs.winehq.org/attachment.cgi?id=67184 Veracrypt log I'm not sure if this is fixable bug, because Veracrypt probably use a lot of low level functions. https://launchpad.net/veracrypt/trunk/1.24-update6/+download/VeraCrypt%20Po… Steps to reproduce: - Download - Extract/Install project - Run -- 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 8606] No network-support in the game Joint Operations Typhoon Rising
by WineHQ Bugzilla 01 Jul '21

01 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=8606 Matteo Bruni <matteo.mystral(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |35288d6537652989473dd87258d | |e5b006d60b589 -- 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 0

[Bug 39739] New: Cobra 11 - Burning Wheels demo: crashes when starting the tutorial
by wine-bugs＠winehq.org 01 Jul '21

01 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=39739 Bug ID: 39739 Summary: Cobra 11 - Burning Wheels demo: crashes when starting the tutorial Product: Wine Version: 1.8-rc2 Hardware: x86-64 URL: http://www.4players.de/4players.php/download_info/Down loads/Download/50183/Alarm_fuer_Cobra_11_Burning_Wheel s/Deutsche_Demo.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)vr-web.de CC: hverbeet(a)gmail.com Regression SHA1: ffc9f535eb7817ea4cd0d0657471e61a9813debd Distribution: --- Created attachment 52998 --> https://bugs.winehq.org/attachment.cgi?id=52998 Avoid freeing memory that gets used later by the demo version of "Cobra 11 - Burning Wheels". When starting the tutorial the demo crashes. This seems to be because the accessed memory was freed before: (See attached patch for the additional trace calls.) 002d:0065:trace:d3d:wined3d_resource_allocate_sysmem Allocated mem=0x1ac47020-0x1aec1093 size=0x27a073 heap_memory=0x1ac47030 resource=0xd70aa98 002d:002e:trace:d3d:wined3d_resource_free_sysmem Freeing heap_memory=0x1ac47030 resource=0xd70aa98 wine: Unhandled page fault on read access to 0x1ada2920 at address 0x52f7b2 (thread 002e), starting debugger... The demo was working some years ago. A git bisect leads to this commit: ffc9f535eb7817ea4cd0d0657471e61a9813debd is the first bad commit commit ffc9f535eb7817ea4cd0d0657471e61a9813debd Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Fri Jun 14 09:07:12 2013 +0200 wined3d: Handle pre-transformed vertices in the GLSL vertex pipe. This also avoids a fallback to drawStridedSlow(). Attached patch makes the game (or at least the tutorial) playable by never freeing the memory above a certain size in buffer_create_buffer_object. -- 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 13

[Bug 39738] New: Collecting backtrace of crashing process not possible.
by wine-bugs＠winehq.org 01 Jul '21

01 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=39738 Bug ID: 39738 Summary: Collecting backtrace of crashing process not possible. Product: Wine Version: 1.8-rc2 Hardware: x86-64 URL: http://www.4players.de/4players.php/download_info/Down loads/Download/50183/Alarm_fuer_Cobra_11_Burning_Wheel s/Deutsche_Demo.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)vr-web.de Distribution: Debian Created attachment 52997 --> https://bugs.winehq.org/attachment.cgi?id=52997 On crash stop all other threads before executing winedbg. This is about a crash in "Cobra 11 - Burning Wheels" demo. It seems this demo includes parts of the copy protection of the full game. (see https://bugs.winehq.org/show_bug.cgi?id=39734 ) Therefore it is not possible to start it with winedbg from begin. Also one gets the crash dialog, but clicking on details shows just "Loading detailed information, please wait...". With the crash dialog disabled it shows: wine: Unhandled page fault on read access to 0x1adb2920 at address 0x52f7b2 (thread 0009), starting debugger... Process of pid=0008 has terminated No process loaded, cannot execute 'echo Modules:' Cannot get info on module while no process is loaded No process loaded, cannot execute 'echo Threads:' (remaining threads) winedbg: Internal crash at 0x7ed8af1d Attaching plain gdb makes the process not end itself and the process gets stopped on the crash. But setting breakpoints is not possible without "disturbing" the process. The attached patch assumes that just one thread crashes which starts then winedbg. Meanwhile another thread gets notified about the crash and terminates the process before winedbg gets a chance to attach. Therefore this patch tries to suspend all other threads before starting winedbg. That way the crash dialog could show a backtrace reliably. -- 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 4

[Bug 39734] New: ProtectDisc Driver 11: acedrv11.sys crashes
by wine-bugs＠winehq.org 01 Jul '21

01 Jul '21

https://bugs.winehq.org/show_bug.cgi?id=39734 Bug ID: 39734 Summary: ProtectDisc Driver 11: acedrv11.sys crashes Product: Wine Version: 1.8-rc2 Hardware: x86-64 URL: http://www.4players.de/4players.php/download_info/Down loads/Download/50183/Alarm_fuer_Cobra_11_Burning_Wheel s/Deutsche_Demo.html OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)vr-web.de Distribution: Debian Created attachment 52986 --> https://bugs.winehq.org/attachment.cgi?id=52986 backtrace.txt The demo version of "Cobra 11: Burning Wheels" comes with this copy protection driver. It gets silently installed by default. One can extract the protection driver from the setup with: 7z x BurningWheelsDemo.exe "\$PLUGINSDIR/Driver_Setup.exe" After this driver is installed wine tries to start the copy protection driver acedrv11.sys on every startup of this wineprefix. This results in a crash of this driver: bernhard@rechner:~/wine/drive_c$ wineserver -k; wine wineboot fixme:ntoskrnl:IoGetDeviceObjectPointer stub: L"\\DosDevices\\CdRom0" 80 0x53e690 0x53e694 fixme:ntoskrnl:KeInitializeEvent stub: 0x11264c 0 0 wine: Unhandled page fault on read access to 0x00000060 at address 0x57923a (thread 0019), starting debugger... ProtectionID v0.6.7.0 identifies it as: #[VersionInfo] Product Name : ProtectDisc x64/x86 Hybrid Driver #[VersionInfo] Product Version : 9.0.0.0 #[VersionInfo] File Version : 11.0.0.11 built by: WinDDK #[VersionInfo] Original FileName : acedrv.sys #[!] ProtectDisc v 9.0.0.0 Driver -- 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 21

Jump to page:

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 July 2021