http://bugs.winehq.org/show_bug.cgi?id=17372
Summary: Adobe Framemaker 9 installer crashes Product: Wine Version: 1.1.14 Platform: Other URL: http://www.adobe.com/go/tryframemaker_win OS/Version: other Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: msxml3 AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
fixme:msxml:xmlnode_put_nodeTypedValue fixme:msxml:Internal_QueryInterface interface {df0b3d60-548f-101b-8e65-08002b2bd119} not implemented wine: Unhandled exception 0x40000015 at address 0x7efd0073:0x004556d8 (thread 0030), starting debugger...
winetricks msxml3 lets it get much further.
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #1 from Alistair Leslie-Hughes leslie_alistair@hotmail.com 2009-02-15 03:14:57 --- Created an attachment (id=19469) --> (http://bugs.winehq.org/attachment.cgi?id=19469) Display type
Can you apply this patch, and list the line of xmlnode_put_nodeTypedValue?
The missing interface might stop the crash, but its only being queried since xmlnode_put_nodeTypedValue isn't implemented.
http://bugs.winehq.org/show_bug.cgi?id=17372
Andrew Nguyen arethusa26@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|Other |x86 OS/Version|other |Linux
--- Comment #2 from Andrew Nguyen arethusa26@gmail.com 2010-02-01 23:26:45 --- This is certainly belated, but applying the requested trace patch and running the Adobe Framemaker 9 installer on wine-1.1.37-312-g7aaaf73 yields the same crash and:
fixme:msxml:xmlnode_put_nodeTypedValue 8
which seems to be type VT_BSTR. Native msxml3 still serves as a usable workaround.
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #3 from Austin English austinenglish@gmail.com 2010-09-12 02:41:25 CDT --- Still in wine-1.3.2-115-gd822555.
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #4 from Nikolay Sivov bunglehead@gmail.com 2010-10-16 13:34:00 CDT --- Please try this patch set http://bugs.winehq.org/attachment.cgi?id=31303. It's over 1.3.5 and report results.
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #5 from Andrew Nguyen arethusa26@gmail.com 2010-10-30 18:05:37 CDT --- Created an attachment (id=31615) --> (http://bugs.winehq.org/attachment.cgi?id=31615) Adobe Framermaker 9 installer +msxml,+tid trace
Applying attachment 31596 on top of 1.3.6, the initial Adobe Framermaker 9 install crash is avoided. Near the end of the installation, a "Bootstrapper" dialog appears with the message:
"Failed to load configuration file: BootstrapperConfig.XML"
accompanied with the output:
err:msxml:doparse XML declaration allowed only at the start of the document
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #6 from Nikolay Sivov bunglehead@gmail.com 2010-10-30 18:55:53 CDT --- I see, so it's making progress, that's good. Native msxml won't parse duplicated prologs too, so the question is were such broken document comes from.
Could you try to find out if this boostrap*.xml is bundled with installer or generated on fly?
The only one ::save() I see is:
--- 0024:trace:msxml:domdoc_save (0x12afa98)->(var(vt 8, L"C:\Program Files\Common Files\Adobe\HelpConfig\en_US\FrameMaker9.helpcfg")) ---
Is it this file that loaded again by any chance? Also please specify libxml2 version you're running with.
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #7 from Andrew Nguyen arethusa26@gmail.com 2010-10-30 23:06:34 CDT --- Created an attachment (id=31618) --> (http://bugs.winehq.org/attachment.cgi?id=31618) +file,+msxml,+tid trace (lzma compressed)
(In reply to comment #6)
Could you try to find out if this boostrap*.xml is bundled with installer or generated on fly?
It's generated near the beginning of the installation. There is a BootstrapperConfig.xml data blob in the "Installer Resources" directory in the install files, which I think the installer derives the "new" BootstrapperConfig.xml from. I believe the installer encrypts/decrypts XML content using crypt32 from these data blobs when it reads and writes to a blob.
I created a new +file,+msxml,+tid trace and added a trace to domdoc_get_xml to see when exactly the installer was creating the new XML file. Lines 24004 through 26260 show the exact creation process and the resulting bad XML output.
The only one ::save() I see is:
0024:trace:msxml:domdoc_save (0x12afa98)->(var(vt 8, L"C:\Program Files\Common Files\Adobe\HelpConfig\en_US\FrameMaker9.helpcfg"))
Is it this file that loaded again by any chance?
It's not that file, which is unrelated to the problem.
Also please specify libxml2 version you're running with.
apt-cache reports:
Version: 2.7.6.dfsg-1ubuntu1
for the libxml2 package on my Ubuntu 10.04 system.
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #8 from Nikolay Sivov bunglehead@gmail.com 2010-10-31 03:32:36 CDT --- Thanks, Andrew. A problem is clear now. It creates manually the whole document including prolog. After that it does ::get_xml() from document, and this results in duplicated prolog, because:
- we don't unlink added prolog, cause 'standalone' field is not updated after adding '<?xml' node; - we don't disable automatic prolog embedding on get_xml(), and there's no way to do it for xmlNodeDump().
The quick workaround is to force 'standalone' value, it will unlink application defined prolog, but add its own which is incomplete cause document knowns nothing about encoding set in prolog.
Proper way is to disable declaration on doc dump, I'll look at that.
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #9 from Nikolay Sivov bunglehead@gmail.com 2010-11-06 14:13:03 CDT --- Try this patch please http://bugs.winehq.org/attachment.cgi?id=31758 , and attach new logs.
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #10 from Andrew Nguyen arethusa26@gmail.com 2010-11-07 02:13:26 CST --- (In reply to comment #9)
Try this patch please http://bugs.winehq.org/attachment.cgi?id=31758 , and attach new logs.
The patch resolves the bootstrapper issue and allows the installer to proceed to install prerequisites. There does appear to be an unrelated crash during a particular prerequisite install, though.
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #11 from Nikolay Sivov bunglehead@gmail.com 2010-11-07 04:36:21 CST --- Good. So next crash is not fixable with native msxml* ?
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #12 from Andrew Nguyen arethusa26@gmail.com 2010-11-07 04:37:29 CST --- (In reply to comment #11)
Good. So next crash is not fixable with native msxml* ?
That's right, the crash happens even with native msxml libraries.
http://bugs.winehq.org/show_bug.cgi?id=17372
--- Comment #13 from Nikolay Sivov bunglehead@gmail.com 2010-11-09 14:05:19 CST --- A msxml fix for that was committed (99e3873f30acc20baed4275f5056ced5a835a47f ).
Please attach current crash log. If next problem is clear we'll mark this fixed and open another one.
http://bugs.winehq.org/show_bug.cgi?id=17372
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |99e3873f30acc20baed4275f505 | |6ced5a835a47f Status|NEW |RESOLVED CC| |focht@gmx.net Resolution| |FIXED
--- Comment #14 from Anastasius Focht focht@gmx.net 2012-01-01 11:08:55 CST --- Hello,
no answer for considerable time, marking fixed with commit http://source.winehq.org/git/wine.git/commitdiff/99e3873f30acc20baed4275f505... (comment #13)
File new bugs for remaining problems.
Regards
http://bugs.winehq.org/show_bug.cgi?id=17372
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Alexandre Julliard julliard@winehq.org 2012-01-13 13:50:28 CST --- Closing bugs fixed in 1.3.37.
-
wine-bugs＠winehq.org