https://bugs.winehq.org/show_bug.cgi?id=48050
Bug ID: 48050 Summary: Sony Vegas 13 stops at "Creating file I/O manager..." Product: Wine Version: 4.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: vinibali1@gmail.com Distribution: ---
Created attachment 65590 --> https://bugs.winehq.org/attachment.cgi?id=65590 output
Hello!
CPU: Ryzen 5 3400G OS: Arch Linux x64 (5.2.10-1-ck) Package (1st run): quartz. Package (2nd run): corefonts d3dx10 d3dx11_42 d3dx11_43 d3dx9 directmusic directplay dotnet40 dsound msxml3 msxml6 quicktime76 Package (3rd run): vcrun2005 vcrun2008 vcrun2010 vcrun2012 vcrun2013 vcrun2015 Prefix: fresh Windows 7 x64 Wine: 4.9, 4.18 (stable and staging)
The application splash screen starts and suddenly stops there in the first part of the progress bar. The message says it's "Creating file I/O manager...". I walked through the steps using Sergey's guideline: https://appdb.winehq.org/objectManager.php?sClass=version&iId=33495&... I even tried black magic, but doesn't helped. Terminal output attached:
Regards
https://bugs.winehq.org/show_bug.cgi?id=48050
vinibali vinibali1@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux
https://bugs.winehq.org/show_bug.cgi?id=48050
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x@gmail.com
--- Comment #1 from Louis Lenders xerox.xerox2000x@gmail.com --- (In reply to vinibali from comment #0)
Created attachment 65590 [details] output
Hello!
Package (2nd run): corefonts d3dx10 d3dx11_42 d3dx11_43 d3dx9 directmusic directplay dotnet40 dsound msxml3 msxml6 quicktime76 Package (3rd run): vcrun2005 vcrun2008 vcrun2010 vcrun2012 vcrun2013 vcrun2015
Hi, So you have tons of native dlls installed and using now. What happens if you just use builtin ones? Using so many native dlls does not usually make bugreport worthfull. Could you start by posting console output with all dlls set to builtin? Thanks
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #2 from vinibali vinibali1@gmail.com --- Hi! I think, couple of libraries are not replaceable like dotnet or msxml. What if I set all of them to Buildin, then native? Regards
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #3 from vinibali vinibali1@gmail.com --- This time I installed only the dotnet40 package alongside with the msxml3. Right after I installed the application, I tried couple of combination to figure out whats wrong: - dotnet40 with native msxml3, - dotnet40 with builtin msxml3, - mono with native msxml3, - mono dotnet40 with builtin msxml3. None of the following combination have been working and producing so much different output :) .net40 doesn't seems to effect anything after the install until the very first steps on the startup progress. Do you have any ideas?
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #4 from vinibali vinibali1@gmail.com --- Created attachment 65606 --> https://bugs.winehq.org/attachment.cgi?id=65606 1
https://bugs.winehq.org/show_bug.cgi?id=48050
vinibali vinibali1@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #65606|1 |20191107_dotnet_msxml_built description| |in
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #5 from vinibali vinibali1@gmail.com --- Created attachment 65607 --> https://bugs.winehq.org/attachment.cgi?id=65607 20191107_dotnet_msxml_native
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #6 from vinibali vinibali1@gmail.com --- Created attachment 65608 --> https://bugs.winehq.org/attachment.cgi?id=65608 20191107_mono_msxml_builtin
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #7 from vinibali vinibali1@gmail.com --- Created attachment 65609 --> https://bugs.winehq.org/attachment.cgi?id=65609 20191107_mono_msxml_nat
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #8 from Louis Lenders xerox.xerox2000x@gmail.com --- Hi, i found trial here: http://dl03.vegascreativesoftware.com/vegaspro13.exe?dwl=1
If you fill in name/emailadress in the first splash screen to register, the trial can be started
I cannot reproduce this. The trial starts fine for me, i can see "creating I/O manager" in the 2nd splash screen, but it gets past it and the app seems to start fine.
I installed it in a prefix where i had dotnet46 installed;
From your log with builtin msxml i see
002c:err:ole:COMPOBJ_DllList_Add couldn't load in-process dll L"C:\windows\system32\msxml3.dll"
That doesn`t look right, i`m guessing there is something wrong with your setup.
Could you try if you can start the trial in a fresh WINEPREFIX, only install dotnet beforeheand, for example dotnet46 or dotnet472, and then report back please?
Thanks
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #9 from vinibali vinibali1@gmail.com --- As I said, all my prefixes were brand new, because these were located on ramdisk. I had another try on btrfs after the tmpfs and with the link you provided they all were the same. But on local filesystem I had much more logs, like I had before. I'll attach it, maybe you'll find something. But don't spend so much time on it. I just found my old SSD with a nearly one year old kernel and Wine 2.18 and that was working perfect. I'll update you tomorrow, thank you!
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #10 from vinibali vinibali1@gmail.com --- Created attachment 65616 --> https://bugs.winehq.org/attachment.cgi?id=65616 20191108_dotnet46
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #11 from vinibali vinibali1@gmail.com --- One more thing. The very first run provided the largest amount of output (17KB vs. 199 KB), but only for the very first time, however I killed the remaining processes called .exe, [sS]ony and [wW]ine before each run.
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #12 from vinibali vinibali1@gmail.com --- During the day, I was working on to figure out what is wrong with this configuration. So I created a fresh Arch Linux installation on my old Athlon II X4 powered machine. Wine 4.18 was installed along with Linux 5.3.8.1 and Linux LTS 4.19.81 kernels. I've got the same error on both kernel versions, so I thought maybe these are too new, so I downgraded them to Linux 5.0.13 and Linux LTS 4.19.14 but this didn't helped any. Later I downgraded Wine to version 2.18 and Vegas was started to work as expected, while the app was starting and the Wine environment was reinitialized, I've got couple of run time related errors. After the downgrade, I upgraded to the latest version, got the same error messages but Vegas was working again as expected with Wine 4.18. Please note, the same prefixless installation was on use on the ~/.wine directory and I started the application simply from the directory (~/.wine/drive_c/Program Files/VEGAS/VEGAS Pro 13.0) with wine vegas130.exe. It's so mysterious...
https://bugs.winehq.org/show_bug.cgi?id=48050
--- Comment #13 from vinibali vinibali1@gmail.com --- Still exists one Wine 5.8
-
WineHQ Bugzilla