https://bugs.winehq.org/show_bug.cgi?id=47174
Bug ID: 47174 Summary: Sibelius complains about missing AvidRemoteObjects364.dll Product: Wine Version: 4.3 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dark.shadow4@web.de Distribution: ---
Created attachment 64426 --> https://bugs.winehq.org/attachment.cgi?id=64426 Log
I used "winetricks -q msxml3 dotnet472" before installation. When running the program it failes to start.
https://bugs.winehq.org/show_bug.cgi?id=47174
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://www.avid.com/sibeli | |us Keywords| |download Summary|Sibelius complains about |Sibelius doesn't start |missing |after installation |AvidRemoteObjects364.dll |
--- Comment #1 from Fabian Maurer dark.shadow4@web.de --- This issue was reported in the forums: https://forum.winehq.org/viewtopic.php?f=8&t=31334
There is a free trial, but it needs registration, see linked URL.
Note that on windows, AvidRemoteObjects364.dll doesn't exist either.
https://bugs.winehq.org/show_bug.cgi?id=47174
Louis Lenders xerox.xerox2000x@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x@gmail.com
--- Comment #2 from Louis Lenders xerox.xerox2000x@gmail.com --- Created attachment 64451 --> https://bugs.winehq.org/attachment.cgi?id=64451 last 3500 lines before the failure of loading the dll
For info I attach last 3500 lines before the (not present) dll fails to load
I don`t know if it has anything to do with the bug but just before the dll fails to load there`s:
002a:Call KERNEL32.RaiseException(406d1388,00000000,00000006,0024f980) ret=1401860d7 002a:trace:seh:NtRaiseException code=406d1388 flags=0 addr=0x7b456156 ip=7b456156 tid=002a
That seems to have to do with naming a thread, was also referenced in bug https://bugs.winehq.org/show_bug.cgi?id=25243 . Is this something that works in wine? Also mentioned for example in https://blogs.msdn.microsoft.com/stevejs/2005/12/20/naming-threads-in-win32-...
(As I said, don`t know if this is the cause, might be red herring)
https://bugs.winehq.org/show_bug.cgi?id=47174
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- (In reply to Louis Lenders from comment #2)
Created attachment 64451 [details] last 3500 lines before the failure of loading the dll
For info I attach last 3500 lines before the (not present) dll fails to load
I don`t know if it has anything to do with the bug but just before the dll fails to load there`s:
002a:Call KERNEL32.RaiseException(406d1388,00000000,00000006,0024f980) ret=1401860d7 002a:trace:seh:NtRaiseException code=406d1388 flags=0 addr=0x7b456156 ip=7b456156 tid=002a
That seems to have to do with naming a thread, was also referenced in bug https://bugs.winehq.org/show_bug.cgi?id=25243 . Is this something that works in wine? Also mentioned for example in https://blogs.msdn.microsoft.com/stevejs/2005/12/20/naming-threads-in-win32- and-net/
(As I said, don`t know if this is the cause, might be red herring)
That's a red herring; it's completely opaque to the application whether naming the thread actually does anything or not (and notably I'm pretty sure it only does something when running under a debugger).
If the library is failing to load, the interesting part is probably what happens inside of LoadLibrary(). What failure code is it returning? What does a +module trace say?
https://bugs.winehq.org/show_bug.cgi?id=47174
--- Comment #4 from Louis Lenders xerox.xerox2000x@gmail.com --- (In reply to Zebediah Figura from comment #3)
If the library is failing to load, the interesting part is probably what happens inside of LoadLibrary(). What failure code is it returning? What does a +module trace say?
Well, as reported above, there is no such dll (also not when installed in windows as reporter claimed)
002a:Call KERNEL32.LoadLibraryW(142734aa0 L"../System32/AvidRemoteObjects364.dll") ret=140174f65
So no idea why it tries loading a nonexistant dll for now
https://bugs.winehq.org/show_bug.cgi?id=47174
dave.riedstra@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dave.riedstra@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47174
--- Comment #5 from dave.riedstra@gmail.com --- Created attachment 64642 --> https://bugs.winehq.org/attachment.cgi?id=64642 output of running with WINEDEBUG=+module
https://bugs.winehq.org/show_bug.cgi?id=47174
--- Comment #6 from dave.riedstra@gmail.com --- Discovered that both installing and running the program with a present working directory (ie, 'wine start') seems to fix the missing DLL (though the program still doesn't run). Closing.
https://bugs.winehq.org/show_bug.cgi?id=47174
--- Comment #7 from dave.riedstra@gmail.com --- (In reply to dave.riedstra from comment #6)
Discovered that both installing and running the program with a present working directory (ie, 'wine start') seems to fix the missing DLL (though the program still doesn't run). Closing.
...I can't close it, maybe someone else can :)
https://bugs.winehq.org/show_bug.cgi?id=47174
--- Comment #8 from Fabian Maurer dark.shadow4@web.de --- There's nothing to close, since nothing is fixed. Don't hang yourself up on the "missing dll" message.
https://bugs.winehq.org/show_bug.cgi?id=47174
--- Comment #9 from Louis Lenders xerox.xerox2000x@gmail.com --- Created attachment 65320 --> https://bugs.winehq.org/attachment.cgi?id=65320 dumb hack
This dumb hack allows me to start the program, though it starts painfully slow
@reporter of bug: could you try if dumb hack works for you? Than we can mark this as wintrust bug probabaly
(from debug log: 0027:Ret KERNEL32.HeapFree() retval=00000001 ret=62553e2a 0027:Call KERNEL32.HeapFree(00010000,00000000,1976d5b0) ret=62553e3c 0027:Ret KERNEL32.HeapFree() retval=00000001 ret=62553e3c 0027:Ret wintrust.WinVerifyTrust() retval=800b0100 ret=14000bb92 seems TRUST_E_NOSIGNATURE)
https://bugs.winehq.org/show_bug.cgi?id=47174
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
https://bugs.winehq.org/show_bug.cgi?id=47174
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |wintrust
--- Comment #10 from Fabian Maurer dark.shadow4@web.de --- @Louis Lenders Thanks, I can confirm the hack makes it start.
https://bugs.winehq.org/show_bug.cgi?id=47174
--- Comment #11 from Louis Lenders xerox.xerox2000x@gmail.com --- Here`s my shot in the dark as why the hack works, did a bit of reading on internet on signature verifying but still noob so don`t shoot me if analysis is wrong
It looks like it seems to check some system dlls like kernel32, user32, netapi32 etc
I ran Sigcheck (https://docs.microsoft.com/en-us/sysinternals/downloads/sigcheck) on system32 and not suprisingly all wine`s system dlls are unsigned
0026:trace:wintrust:dump_file_info pcwszFilePath: L"c:\windows\system32\netapi32.dll" . . . 0026:trace:wintrust:WINTRUST_DefaultVerify returning 800b0100
On windows in Virtualbox:
c:\windows\system32\netapi32.dll: Verified: Signed Signing date: 10:37 PM 11/20/2010 Publisher: Microsoft Windows Company: Microsoft Corporation Description: Net Win32 API DLL Product: Microsoft<AE> Windows<AE> Operating System Prod version: 6.1.7601.17514 File version: 6.1.7601.17514 (win7sp1_rtm.101119-1850) MachineType: 64-bit
If WinVerifyTrust just returns success for all system dlls I guess this bug is fixed. I`ll attach +wintrust log for Sibelius hereafter
https://bugs.winehq.org/show_bug.cgi?id=47174
--- Comment #12 from Louis Lenders xerox.xerox2000x@gmail.com --- Created attachment 65338 --> https://bugs.winehq.org/attachment.cgi?id=65338 +wintrust log
+wintrust debug log