https://bugs.winehq.org/show_bug.cgi?id=38290
Bug ID: 38290 Summary: LabVIEW installer (2009sp1, 2012 Fall, 2014 Fall) fails with msi.dll ACCESS_VIOLATION Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs@winehq.org Reporter: enrico.segre@weizmann.ac.il Distribution: ---
when setup.exe is run from desktop without particular wineprefix, as I reported for the AppDB ( https://appdb.winehq.org/objectManager.php?sClass=application&iId=4556 ). I see that several other bugs related to msi and labview (5399, 8895, 26537, 27841, 28849, 29099 for example) have already been filed and closed, so forgive if that is a duplicate, or if there is a trivial workaround which I ignore.
https://bugs.winehq.org/show_bug.cgi?id=38290
Enrico Segre enrico.segre@weizmann.ac.il changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |enrico.segre@weizmann.ac.il
https://bugs.winehq.org/show_bug.cgi?id=38290
--- Comment #1 from Nikolay Sivov bunglehead@gmail.com --- Hi, Enrico.
Please update your Wine first, 1.6.2 is very old.
(In reply to Enrico Segre from comment #0)
when setup.exe is run from desktop without particular wineprefix
You always run with some wineprefix, even if you don't specify it explicitly.
https://bugs.winehq.org/show_bug.cgi?id=38290
--- Comment #2 from Enrico Segre enrico.segre@weizmann.ac.il --- (In reply to Nikolay Sivov from comment #1)
Please update your Wine first, 1.6.2 is very old.
it's the one coming with ubuntu 14.04 which is not that old... I'll upgrade and report.
https://bugs.winehq.org/show_bug.cgi?id=38290
--- Comment #3 from Enrico Segre enrico.segre@weizmann.ac.il --- and 1.6.2 is the current stable. Ok, I grabbed 1.7.38 and tried the installers of 2014 fall and 2012 fall. Both fail exactly the same way I reported on the AppDB.
https://bugs.winehq.org/show_bug.cgi?id=38290
--- Comment #4 from Hans Leidekker hans@meelstraat.net --- (In reply to Enrico Segre from comment #3)
and 1.6.2 is the current stable. Ok, I grabbed 1.7.38 and tried the installers of 2014 fall and 2012 fall. Both fail exactly the same way I reported on the AppDB.
Please get a WINEDEBUG=+msi,+seh,+tid trace with 1.7.38 and a fresh prefix.
https://bugs.winehq.org/show_bug.cgi?id=38290
--- Comment #5 from Enrico Segre enrico.segre@weizmann.ac.il --- doh! with a fresh prefix (and 1.7.38) 2012 just installed, with only two glitches:
-the installers for each subproduct showed a 0% complete bar all the time, while the secondary barPublishing product information/Copying new files/Computing space requirements/Removing files updated correctly;
-WINEDEBUG=+msi,+seh,+tid wine setup.exe >> /tmp/output.txt 2>&1 locked the dvd, so I couldn't swap to the Driver dvd as the installer would need, and I have aborted that part of the installation.
The trace grew to 657M, clearly I won't attach. I'll keep testing and report.
https://bugs.winehq.org/show_bug.cgi?id=38290
--- Comment #6 from Austin English austinenglish@gmail.com --- (In reply to Enrico Segre from comment #5)
The trace grew to 657M, clearly I won't attach. I'll keep testing and report.
You can use bzip2 / rzip / xz to compress logfiles pretty well.
https://bugs.winehq.org/show_bug.cgi?id=38290
--- Comment #7 from Enrico Segre enrico.segre@weizmann.ac.il --- yeah, sure. But at this point I'm a bit confused, I ran several other installation tests of different versions of LabVIEW, getting inconsistent results - quirks of the installers, different installer errors about missing components, fatal errors of the installed programs, and I have no more a clear picture of what is happening. In principle I think I restarted each attempt from a clean prefix (winetricks-> delete all data inside this wineprefix), sometimes trying different bitness or windows version, but am no more sure. To name one, as of my previous comment I had a running 2012 (except for broken vision VIs), I couldn't get even the installer to complete, later on. In light of the confusion, perhaps better to set this report aside for a while, till I have univocal data.
https://bugs.winehq.org/show_bug.cgi?id=38290
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #8 from winetest@luukku.com --- Can you retest this bug? Bug 39406 has version 2014 and it crashes clearly on another component which could mean that this bug is actually fixed.
https://bugs.winehq.org/show_bug.cgi?id=38290
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME URL| |https://web.archive.org/web | |/20181022065706/http://down | |load.ni.com/evaluation/labv | |iew/ekit/other/downloader/2 | |014LV-WinEng.exe Status|UNCONFIRMED |RESOLVED Summary|LabVIEW installer (2009sp1, |LabVIEW 2009sp1, 2012, 2014 |2012 Fall, 2014 Fall) fails |installers crash |with msi.dll | |ACCESS_VIOLATION | CC| |focht@gmx.net Keywords| |download, Installer
--- Comment #9 from Anastasius Focht focht@gmx.net --- Hello folks,
I can't reproduce MSI (client/server) crash with old Wine 1.6.2 version the bug was reported with. The installer finishes successfully. I suspect OP recycled an existing/broken WINEPREFIX.
Resolving 'WORKSFORME' unless someone proves (logs!) that Wine was indeed broken with LabVIEW installers and got fixed at some point. Even then that would have been most likely a duplicate anyway.
Stable download link via Internet Archive:
https://web.archive.org/web/20181022065706/http://download.ni.com/evaluation...
$ sha1sum 2014LV-WinEng.exe b16e80402d7567b49e0f47a673fe53accbd1e029 2014LV-WinEng.exe
$ du -sh 2014LV-WinEng.exe 1.4G 2014LV-WinEng.exe
$ wine --version wine-1.6.2
Regards
https://bugs.winehq.org/show_bug.cgi?id=38290
--- Comment #10 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=38290
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #11 from Austin English austinenglish@gmail.com --- Closing.