http://bugs.winehq.org/show_bug.cgi?id=34795
Bug #: 34795 Summary: SolidWorks 2010: No correct headers' name for material databases in manager Product: Wine Version: 1.7.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msxml4 AssignedTo: wine-bugs@winehq.org ReportedBy: lukasz.wojnilowicz@gmail.com Classification: Unclassified
Created attachment 46402 --> http://bugs.winehq.org/attachment.cgi?id=46402 Appearance comparison
Steps to reproduce: 1) remove ~/.wine 2) winetricks vcrun2005 vcrun2008 mfc40 dotnet30 3) install SolidWorks 2010 4) start SolidWorks 2010 5) create new part 6) RMB on material 7) choose "edit material" 8) choose any material and click "apply"
Behaviour: Left side of image (see attachment)
Expected behaviour: Right side of image (see attachment)
Additional info: "sh winetricks msxml6" helps.
http://bugs.winehq.org/show_bug.cgi?id=34795
--- Comment #1 from NSLW lukasz.wojnilowicz@gmail.com 2013-10-24 11:23:24 CDT --- Created attachment 46403 --> http://bugs.winehq.org/attachment.cgi?id=46403 WINEDEBUG=+msxml,+tid on wine-1.7.4-300-ga562af5
http://bugs.winehq.org/show_bug.cgi?id=34795
--- Comment #2 from Nikolay Sivov bunglehead@gmail.com 2013-10-28 08:16:28 CDT --- This one is a really bad:
--- 0009:trace:msxml:external_entity_loader ("colorswatch.xsd" (null) 0xf1df86f8) 0009:trace:msxml:wineXmlMatchCallback file:///etc/xml/catalog 0009:trace:msxml:wineXmlMatchCallback colorswatch.xsd I/O warning : failed to load external entity "colorswatch.xsd" 0009:warn:msxml:Schema_parse error code 3084: Element '{http://www.w3.org/2001/XMLSchema%7Dimport': Failed to locate a schema at location 'colorswatch.xsd'. Skipping the import. 0009:err:msxml:Schema_parse error code 3004: element decl. 'swatchcolor', attribute 'type': The QName value '{http://www.solidworks.com/sldcolorswatch%7Dopticalcolor' does not resolve to a(n) type definition. ---
We already have a report with similar symptoms - bug 25049. I remember trying to find a way to make it resolve a path, but failed to make it work, already forgot details. I'll need to look closer.
http://bugs.winehq.org/show_bug.cgi?id=34795
--- Comment #3 from NSLW lukasz.wojnilowicz@gmail.com 2013-10-28 08:20:01 CDT --- (In reply to comment #2)
We already have a report with similar symptoms - bug 25049. I remember trying to find a way to make it resolve a path, but failed to make it work, already forgot details. I'll need to look closer.
Do you need any further log (It's fairly easy to retrieve)? Should this bug be considered duplicate?
http://bugs.winehq.org/show_bug.cgi?id=34795
--- Comment #4 from Nikolay Sivov bunglehead@gmail.com 2013-10-28 08:31:09 CDT --- No, thanks. Let's keep both open for now. Once we have a patch, we'll see.
http://bugs.winehq.org/show_bug.cgi?id=34795
Sylvain Petreolle spetreolle@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |spetreolle@yahoo.fr
http://bugs.winehq.org/show_bug.cgi?id=34795
--- Comment #5 from NSLW lukasz.wojnilowicz@gmail.com 2013-12-07 04:45:50 CST --- Still issue in Wine 1.7.8
https://bugs.winehq.org/show_bug.cgi?id=34795
--- Comment #6 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.37 or newer) wine? If so, please attach the terminal output in 1.7.37 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=34795
Sylvain Petreolle spetreolle@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|spetreolle@yahoo.fr |
https://bugs.winehq.org/show_bug.cgi?id=34795
Dmitry windes@rambler.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |windes@rambler.ru
--- Comment #7 from Dmitry windes@rambler.ru --- (In reply to Austin English from comment #6)
This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.37 or newer) wine? If so, please attach the terminal output in 1.7.37 (see http://wiki.winehq.org/FAQ#get_log).
No, there's no such bad behavior of msxml6.dll's on Wine 6.23 and upper (till highest 7.12 now).