http://bugs.winehq.org/show_bug.cgi?id=20354
Summary: Sony Vegas has encountered an Error: 'WIA-Manager could not be initialized' Product: Wine Version: 1.1.31 Platform: PC-x86-64 URL: http://www.sonycreativesoftware.com/vegaspro OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: winecreations@trashmail.net
Created an attachment (id=24107) --> (http://bugs.winehq.org/attachment.cgi?id=24107) Console Output when starting the installed and registered program
I am a professional video editor for one of the large studios around. Lately switching to Linux have 'forced' me to use the awesome WINE in order to install Sony Vegas Pro 9. Unfortunately WINE does absolutely not care about the Windows Image Acquisition (WIA).
Ths, I only can say that Sony Vegas Pro 9 install absolutely without any errors, and even registration works fine. Right after the start of the program the loading window shows up and is replaced immediately with an error notification: "Sony Vegas has encountered an Error: 'WIA-Manager could not be initialized'".
I figured to talk to the people on IRC and post an error log, but even they say that WINE does not care the slightest about the Windows Image Acquisition. I am actually looking forward to see WIA supported as fast as possible.
I´ve been talking directly to Sony developers in their forum (complete Thread in German). If you are interested seing the output feel free to visit: http://www.vegasforum.de/sony-vegas-pro-t1878.html
THANK YOU for the work you do every day to improve WINE. It is much appreciated.
http://bugs.winehq.org/show_bug.cgi?id=20354
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #24107|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=20354
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Alias|WIA-Manager-Bug |
http://bugs.winehq.org/show_bug.cgi?id=20354
Damjan Jovanovic damjan.jov@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |damjan.jov@gmail.com Ever Confirmed|0 |1 Difficulty|--- |Years
--- Comment #1 from Damjan Jovanovic damjan.jov@gmail.com 2009-10-14 03:51:29 --- We only barely support WIA's predecessor and foundation, STI (Still Image). Some of my rudimentary STI patches went in only about a week ago, and I've been struggling hard since to write even a basic IStillImage_GetDeviceList() test. And I haven't even gotten to USBSCAN.SYS and USB access in Wine...
WIA is massive. It even has at least 2 interfaces to scripting languages and .NET, and the docs are about 5 times longer than the STI docs. It is years away, if we ever even get to it.
You might be able to use the Windows native DLLs and EXEs for WIA in Wine, but then you'd still need kernel mode components, probably missing SETUPAPI bits, various .INF files, registry entries, and maybe even some .NET stuff, so I just don't see it happening.
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #2 from sl@shback winecreations@trashmail.net 2009-10-14 05:26:15 --- Thanks for your explanation on this topic. I thought it wouldn´t be that complicated to implement WIA-Management in WINE in order to use this awesome video editing suite. How about MONO - does it support WIA at the moment?
http://bugs.winehq.org/show_bug.cgi?id=20354
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Difficulty|Years |---
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #3 from sl@shback winecreations@trashmail.net 2009-10-14 08:03:03 --- Found out that MONO does not support WIA either. But how can something so crutial be missing in WINE? Do any "replacements" for WIA exist then?
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #4 from Damjan Jovanovic damjan.jov@gmail.com 2009-10-14 08:34:27 --- It's a fairly obscure Microsoft-proprietary API for still image devices, intended to kill open and portable standards like TWAIN, so how does one uncommon app make it "crucial" :-) ?
If Sony Vegas does not use WIA a lot, it may be possible to write a very simple stubbed WIA implementation that just fools Sony Vegas into starting but does little else. It won't actually work with a camera or scanner.
I'll have a closer look when I get home.
Does the trial version have the same problem? Are you willing to try some patches?
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #5 from sl@shback winecreations@trashmail.net 2009-10-15 02:06:16 --- Of course, bring it on! ;) Thank you for taking a look at it.
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #6 from sl@shback winecreations@trashmail.net 2009-10-18 15:03:25 --- (In reply to comment #4)
It's a fairly obscure Microsoft-proprietary API for still image devices, intended to kill open and portable standards like TWAIN, so how does one uncommon app make it "crucial" :-) ?
If Sony Vegas does not use WIA a lot, it may be possible to write a very simple stubbed WIA implementation that just fools Sony Vegas into starting but does little else. It won't actually work with a camera or scanner.
I'll have a closer look when I get home.
Does the trial version have the same problem? Are you willing to try some patches?
Same problem with the trial version. Of course I am willing to try some patches - hand them over please...
Greetings, sl@shback
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #7 from Damjan Jovanovic damjan.jov@gmail.com 2009-10-21 11:03:54 --- Hello again
Well on Saturday I finally found some free time and got hold of a Platform SDK and started writing up a wia.h for Wine, only to discover that IWiaDevMgr (1) needs numerous other interfaces, and (2) is hosted in an out of process COM server.
Now (1) would just be more work, but (2) makes the entire wia.h useless, since both wia.h and the inter-process marshaling code needs to be generated by widl (Wine's "midl") from a wia.idl, something I've never done before :-).
After starting on wia.idl, I noticed the interfaces just needed more and more other interfaces, and a few nights later I gave up on that approach too, because I realized that if IWiaDevMgr is just a stub, the other interfaces can be empty, since they'll never be used.
So now I'm busy compiling Wine with the second wia.idl and next I'll have to try make sti.dll play along as a proxy like it does on Windows and marshal to some WIA DLL that is hosted by svchost.exe on Windows (AFAIK only 1 other Wine DLL does that, eek!). Then, which is hopefully tomorrow or soon after, I can send you a patch for testing.
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #8 from sl@shback winecreations@trashmail.net 2009-10-24 14:56:17 ---
Whoa, thanks for doing this great contribution Mr. Jovanovic!
Please let me know when I can support you with specific tasks. I´m gladly looking forward to test some patches. ;)
Have a good start into the weekend!
/-back
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #9 from Damjan Jovanovic damjan.jov@gmail.com 2009-10-25 12:41:19 --- Created an attachment (id=24347) --> (http://bugs.winehq.org/attachment.cgi?id=24347) Stubbed IWiaDevMgr implementation
Hi
Please try this patch.
After applying the patch to the Wine source, it's not enough to compile Wine with the normal "./configure && make depend && make && make install", you have to first run "autoconf", and then you might need to run "regsvr32 sti.dll" and "regsvr32 wiaservc.dll" after it's compiled and installed.
It works for me in a test where I just create IWiaDevMgr (which is what Sony Vegas does), but I don't know what else Sony Vegas might want to do. If it doesn't work, please post console output.
Thank you for testing Damjan
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #10 from sl@shback winecreations@trashmail.net 2009-10-27 12:16:04 --- Hey Damjan, I've successfully applied your patch to WINE 1.1.32, but when running autoconf it tells me that '/usr/bin/m4:configure.ac:5: cannot open `VERSION': No such file or directory' as well as 'autom4te: /usr/bin/m4 failed with exit status: 1'. Talking to soe people on IRC (taking a mental note of arethusas friendly replies here) they told me that doing autoconf was no problem for them and recommended me to apply the patch on GIT. However, I won't load it right now as it is too large in my eyes in this moment.
Would you please re-check the command you posted before? I am running on x86_64, so this might be the cause...
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #11 from Damjan Jovanovic damjan.jov@gmail.com 2009-10-27 12:53:41 --- Git is very close to 1.1.32, it probably won't work any differently.
I just tried 1.1.32, and "autoconf" works for me. Are you running it from the wine-1.1.32 directory, ie. the one the VERSION file is in?
Then again maybe it is some 64 bit thing (I've never used a 64 bit desktop, and don't look forward to it :-). If you are really struggling, I could send you a patch that covers configure as well, then you wouldn't have to run autoconf.
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #12 from sl@shback winecreations@trashmail.net 2009-10-28 03:45:13 --- (In reply to comment #11)
Git is very close to 1.1.32, it probably won't work any differently.
I just tried 1.1.32, and "autoconf" works for me. Are you running it from the wine-1.1.32 directory, ie. the one the VERSION file is in?
Then again maybe it is some 64 bit thing (I've never used a 64 bit desktop, and don't look forward to it :-). If you are really struggling, I could send you a patch that covers configure as well, then you wouldn't have to run autoconf.
Thanks for replying, yes I did. I´m not sure what causes the issue, but I´ll certainly try again this evening. I´d appreciate it if you would provide a small patch handling configure as well. Have a good one!
http://bugs.winehq.org/show_bug.cgi?id=20354
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #13 from Dan Kegel dank@kegel.com 2009-10-28 08:50:01 --- '/usr/bin/m4:configure.ac:5: cannot open `VERSION': No such file or directory' is a very odd error. Googling for it only finds two hits, and no solutions.
What are the permissions on VERSION? Are you running as yourself, or as root?
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #14 from sl@shback winecreations@trashmail.net 2009-10-28 11:04:36 --- Hi there Mr. Kegel! Better would have been if you told me what would be correct to do since I could hit the road right away then. I´ve been running this as normal user, Version permissions are set to user. Anyhow, I´ll try again soon - I´m just awaiting some reply from Mr. Jovanovic.
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #15 from Dan Kegel dank@kegel.com 2009-10-28 11:06:51 --- If I knew what to do, I'd tell you :-)
Thanks for the answer, but I'm still unclear... what does ls -l Version say?
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #16 from Damjan Jovanovic damjan.jov@gmail.com 2009-10-28 12:04:21 --- Created an attachment (id=24414) --> (http://bugs.winehq.org/attachment.cgi?id=24414) configure for Wine 1.1.32 with the patch
Here is the configure for Wine 1.1.32 with the patch applied and autoconf run, but I'm afraid that if even autoconf isn't running something else may be majorly wrong...
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #17 from sl@shback winecreations@trashmail.net 2009-11-03 12:39:43 --- Thanks for providing this, Mr. Jovanovic! First off, I tested your first patch again, discovering that probably not all 32-bit development packages are installed on the 64bit system I'm testing with (see http://pastebin.org/50529). I've been testing your latest patch as well and found that GCC >= 4.4. was required - thus, I installed it, but still received the above mentioned error when running autoconf. In 9 days I'm migrating to a new verion of my OS - but until then I'd like someone else to test Mr. Jovanovics Patch. If it works with the trial version, there shouldn't be a problem with the fully registered one.
Please support this project - I'd love to see someone testing this patch! :) Don't forget, if anything else is needed in order to make this work - I'm always watching this page. -slashback
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #18 from Damjan Jovanovic damjan.jov@gmail.com 2009-11-03 13:00:09 --- Parts of my patch have already been committed to Git, 1 part is pending review and there is only 1 more for me to send.
If all goes well the full patch will be in the next release (1.1.33).
I don't think I will be running the trial version since after a huge download it still needs .NET 3, WMF 11, and Visual C++ 2005 and 2008 SP1 redistributables just to install...
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #19 from sl@shback winecreations@trashmail.net 2009-11-03 14:36:11 --- Rest assured that I´m burning to test if Sony Vegas Pro finally works with WINE 1.1.33. Is there actually some kind of page telling me when 1.1.33 will be released?
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #20 from Austin English austinenglish@gmail.com 2009-11-03 15:42:49 --- (In reply to comment #19)
Rest assured that I´m burning to test if Sony Vegas Pro finally works with WINE 1.1.33. Is there actually some kind of page telling me when 1.1.33 will be released?
Usually every other Friday, but Wineconf is this weekend, so it may be delayed until next week.
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #21 from sl@shback winecreations@trashmail.net 2009-11-03 16:13:29 --- Thanks, I´ll report back after testing Vegas Pro with Wine 1.1.33 with your code included. One thing straight ahead: You did a great job. :)
-slashback
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #22 from Damjan Jovanovic damjan.jov@gmail.com 2009-11-05 11:08:52 --- All my patches are now in the latest Git, so you can either test with that or Wine 1.1.33 when it comes out. Please attach console output if it doesn't work.
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #23 from Damjan Jovanovic damjan.jov@gmail.com 2009-11-16 03:05:33 --- Wine 1.1.33 is out now, please test it and report back.
http://bugs.winehq.org/show_bug.cgi?id=20354
sl@shback winecreations@trashmail.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #24107|0 |1 is obsolete| |
--- Comment #24 from sl@shback winecreations@trashmail.net 2009-11-17 17:32:51 --- Created an attachment (id=24811) --> (http://bugs.winehq.org/attachment.cgi?id=24811) Console Output of startup procedure - ERROR #2
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #25 from sl@shback winecreations@trashmail.net 2009-11-17 17:33:35 --- Thanks, I tested Sony Vegas Pro 9.0c with WINE 1.1.33 and the result is, that the WIA-Manager error is gone, but instead another error notification pops up. "An Error has occured while starting Vagas Pro -- ERROR 0x800703e6 (Netification is missing).
I'll attach another log of the startup process. Thanks for helping, guys. -slashback
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #26 from sl@shback winecreations@trashmail.net 2009-12-01 03:26:33 --- Did anyone analyze the attached log yet? I´d love to get this application to fully work within WINE - currently there just does not exist an application equivalent to Sony Vegas Pro. Which further steps do you recommend to execute?
-slashback
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #27 from Dan Kegel dank@kegel.com 2009-12-01 08:10:23 --- Hard to say; the crash is in their error reporting client, it's not the real problem. Would probably need a +relay trace. If you generate one, be sure to start up winemine first so you don't trace service startup.
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #28 from sl@shback winecreations@trashmail.net 2009-12-02 04:29:14 --- (In reply to comment #27)
Hard to say; the crash is in their error reporting client, it's not the real problem. Would probably need a +relay trace. If you generate one, be sure to start up winemine first so you don't trace service startup.
I´ll gladly do that. Please tell me the *exact* steps to produce an appropriate +relay.
-slashback
http://bugs.winehq.org/show_bug.cgi?id=20354
--- Comment #29 from Dan Kegel dank@kegel.com 2009-12-02 04:34:33 --- wine winemine & WINEDEBUG=+relay,+seh wine vegas.exe > log.txt 2>&1 gzip log.txt
then attach log.txt.gz
(substitute the real exe for vegas.exe, etc.)
http://bugs.winehq.org/show_bug.cgi?id=20354
butraxz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |butraxz@gmail.com
--- Comment #30 from butraxz@gmail.com 2012-05-23 13:52:44 CDT --- This bug has not been updated for three years. Is this still an issue i current (1.5.4) or newer wine ?
http://bugs.winehq.org/show_bug.cgi?id=20354
JD Hupp winehq@prpcompany.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq@prpcompany.com
--- Comment #31 from JD Hupp winehq@prpcompany.com 2012-10-18 09:33:14 CDT --- I'm having what looks like a problem related to the same bug. I have posted the issue in the forums at http://forum.winehq.org/viewtopic.php?f=8&t=17427&p=81023
I'm trying to use Canon RemoteCapture 2.7.5 for a USB-connected Powershot G1 on Lubuntu 12.04 running WINE 1.4.
In Windows, RemoteCapture connects to the camera when it is in PC-communication mode and allows the user to snap preview shots, adjust camera settings, and also snap shots that are copied to the PC.
When I run the program in WINE and choose Connect (to Connect to the camera), it responds with:
Camera error: Check the lens cover and the cable connecting, then reconnect.
The program output in a terminal window:
WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-ZFgwvv/pkcs11: No such file or directory fixme:storage:create_storagefile Storage share mode not implemented. fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),1,3,(nil),0,(nil)) - stub! fixme:wia:wiadevmgr_QueryInterface interface {00000003-0000-0000-c000-000000000046} not implemented fixme:wia:wiadevmgr_QueryInterface interface {00000003-0000-0000-c000-000000000046} not implemented fixme:wia:wiadevmgr_EnumDeviceInfo (0x129718, 16, 0xd3e5b8): stub fixme:sti:stillimagew_GetDeviceList (0x15f770, 0, 0x0, 0x32f2f8, 0x32f300): stub
Because of the wiadevmgr messages I tried to Install Canon's WIA driver via WINE also. It arrived at a point where the installer said something vaguely like "Make sure your camera is on and connected. When you click OK to close the installer, Windows will continue the installation." Of course, clicking OK at that point simply closed the WINE/WIA-installer window.
Results were still the same after the above attempt.
Results are the same whether the camera's memory card is mounted or unmounted. (In Lubuntu, the gphoto2 command-line-interface for remote control/access only works with the card unmounted.)
http://bugs.winehq.org/show_bug.cgi?id=20354
Mikael Ståldal temp17@staldal.nu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |temp17@staldal.nu
--- Comment #32 from Mikael Ståldal temp17@staldal.nu --- I have a problem with Adobe Lightroom 4.4.1, the import dialog fails to open. I think it is related to this, since I get this message in the console several times: fixme:wia:wiadevmgr_EnumDeviceInfo (0x129ad0, 16, 0xb4e538): stub
I don't want to use WIA, I just want to import files on my disk, but Lightroom get stuck and the import dialog never shows up.
Would it be possible to make an implementation of wiadevmgr_EnumDeviceInfo which always returns an empty IEnumWIA_DEV_INFO, telling the app that there are no WIA devices available?
I found the documentation here:
http://msdn.microsoft.com/en-us/library/windows/desktop/ms630142%28v=vs.85%2...
http://msdn.microsoft.com/en-us/library/windows/desktop/ms630162%28v=vs.85%2...
http://bugs.winehq.org/show_bug.cgi?id=20354
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |3ec06f8082bcb987dff588a6e97 | |58c140721886a Status|NEW |RESOLVED CC| |focht@gmx.net Resolution|--- |FIXED
--- Comment #33 from Anastasius Focht focht@gmx.net --- Hello folks,
this bug should have been closed a long time ago with the initial WIA service infrastructure bringup and not 'recycled' for multiple issues anymore (no metabugs!)
Comment #31 and following talk about an issue which covered by bug 27775 -> IWiaDevMgr->EnumDeviceInfo stub.
Resolving this bug 'fixed' now.
Selecting commit http://source.winehq.org/git/wine.git/commitdiff/3ec06f8082bcb987dff588a6e97... ('wiaservc: Add self registration.')
Thanks Damjan
Regards
https://bugs.winehq.org/show_bug.cgi?id=20354
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #34 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.9.
https://bugs.winehq.org/show_bug.cgi?id=20354
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |wia