https://bugs.winehq.org/show_bug.cgi?id=40580
Bug ID: 40580 Summary: TASCAM US-16x08 soundcard controller crashes Product: Wine Version: 1.9.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: brouits@free.fr Distribution: ---
Created attachment 54421 --> https://bugs.winehq.org/attachment.cgi?id=54421 backtrace showing a x00 pointer access
1. on fresh wine 1.9.9, install TASCAM US-16x08 controller from http://www.tascam.eu/sw/us-16x08/US-16x08_driver_v104_win.zip 2. run the installed software with wine 3. expected : GUI started, got crash report from wine
https://bugs.winehq.org/show_bug.cgi?id=40580
Benoît Rouits brouits@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu
https://bugs.winehq.org/show_bug.cgi?id=40580
Benoît Rouits brouits@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #54421|backtrace showing a x00 |backtrace showing a page description|pointer access |fault on 0x00 access
https://bugs.winehq.org/show_bug.cgi?id=40580
--- Comment #1 from Benoît Rouits brouits@free.fr --- notice winecfg must be ran before to configure wine as windows10 flavour.
https://bugs.winehq.org/show_bug.cgi?id=40580
--- Comment #2 from Nikolay Sivov bunglehead@gmail.com --- According to their download page Windows 7 should be enough, but really, start with default winxp first. Also attach complete terminal output, not just a backtrace.
https://bugs.winehq.org/show_bug.cgi?id=40580
--- Comment #3 from Benoît Rouits brouits@free.fr --- on winxp flavour, the software pops up a dialog saying it cannot run. on windows10 flavour its get those cmdline output:
fixme:file:FindFirstFileExW flags not implemented 0x00000002 fixme:system:SetProcessDPIAware stub! fixme:ver:GetCurrentPackageId (0x9e7e9d8 (nil)): stub
then the backtrace (attached).
System information: Wine build: wine-1.9.9 Platform: i386 (WOW64) Version: Windows 10 Host system: Linux Host version: 4.4.0-22-generic
https://bugs.winehq.org/show_bug.cgi?id=40580
Louis Lenders xerox_xerox2000@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox_xerox2000@yahoo.co.uk
--- Comment #4 from Louis Lenders xerox_xerox2000@yahoo.co.uk --- Created attachment 54484 --> https://bugs.winehq.org/attachment.cgi?id=54484 hack/patch to get the GUI running
Hi, this looks as een exact dupe of https://bugs.winehq.org/show_bug.cgi?id=32936
With the hack attached the GUI starts fine for me.
A relay log shows more or less the same sequence of lines before the crash as in bug https://bugs.winehq.org/show_bug.cgi?id=32936
https://bugs.winehq.org/show_bug.cgi?id=40580
Andrew Eikum aeikum@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aeikum@codeweavers.com
https://bugs.winehq.org/show_bug.cgi?id=40580
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com, | |winetest@luukku.com
--- Comment #5 from winetest@luukku.com --- (In reply to Louis Lenders from comment #4)
Created attachment 54484 [details] hack/patch to get the GUI running
Hi, this looks as een exact dupe of https://bugs.winehq.org/show_bug.cgi?id=32936
With the hack attached the GUI starts fine for me.
A relay log shows more or less the same sequence of lines before the crash as in bug https://bugs.winehq.org/show_bug.cgi?id=32936
I have broken sound configuration currently, which prevented me for testing the other bug with wine-git, but it started to work wine-staging after the patch was landed into staging, so It's quite safe to assume that the bug was fixed with the changes
commit ba858c28fd489a812ea0f55a11680a8edaf99ce5 Author: Andrew Eikum aeikum@codeweavers.com Date: Tue Aug 9 10:17:04 2016 -0500
And you assumed that this bug is a dupe. It's a bit hard for me to this now, but I already tested the application against wine-staging 1.9.17 which includes the commit mentioned. And the application starts with no issues. So if your analyze is correct this is indeed a dupe and should be working with both wine 1.9.17 and staging 1.9.17.
https://bugs.winehq.org/show_bug.cgi?id=40580
Andrew Eikum aeikum@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Fixed by SHA1| |ba858c28fd489a812ea0f55a116 | |80a8edaf99ce5
--- Comment #6 from Andrew Eikum aeikum@codeweavers.com --- Yes, I tested this and it seems to work. Please re-open if you still have this problem in Wine 1.9.17 or later, or open a new bug if you run into a different problem.
https://bugs.winehq.org/show_bug.cgi?id=40580
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.9.18.
https://bugs.winehq.org/show_bug.cgi?id=40580
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mstefani@redhat.com Target Milestone|--- |1.8.x
https://bugs.winehq.org/show_bug.cgi?id=40580
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|1.8.x |---
--- Comment #8 from Michael Stefaniuc mstefani@redhat.com --- Removing 1.8.x milestone from bugs included in 1.8.5.
-
wine-bugs＠winehq.org