http://bugs.winehq.org/show_bug.cgi?id=29809
Bug #: 29809 Summary: Hype the Time Quest Installer Goes Over 100% Product: Wine Version: 1.3.16 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: jthomas97411@yahoo.com Classification: Unclassified
Wine 1.3.16 is as far back as I tested. For 1.3.16, 1.3.20, 1.4 rc 1, and 1.4 rc 2, if you uncheck the Microsoft DirectX Media check, this will allow the installer to succeed, whereas if you don't uncheck that, it will fail.
When it fails (DirectX check left checked), it stops at about 100%. When it succeeds (DirectX check unchecked), it goes to 116%, in the case of the versions mentioned above.
There were some versions there for a while, somewhere not too far after 1.3.29, that went to 117% when you didn't uncheck the DirectX test and they failed, and when you did uncheck the DirectX test, the installer stopped at 100% and succeeded. Whereas with these other versions it doesn't go over if you _don't_ uncheck it and does go over if you _do_ uncheck_ it. It still held true that unchecking let it succeed and leaving it checked caused it to fail.
So this is a separate bug from the installer simply crashing.
Notice how this is different than the DirectX check bug: 29806. This is about the installer going over 100%.
I get this 9 times in terminal from when the installer crashes in the case of 1.3.16, 1.3.20, 1.4 rc 1, and 1.4 rc 2:
fixme:advpack:ExecuteCabW Cab archive not extracted!
Jake
http://bugs.winehq.org/show_bug.cgi?id=29809
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.3.16 |1.4-rc2
--- Comment #1 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2012-02-05 12:49:24 CST --- Again, set the latest Wine version you've tested.
http://bugs.winehq.org/show_bug.cgi?id=29809
--- Comment #2 from Jake Thomas jthomas97411@yahoo.com 2012-02-05 12:55:50 CST --- But I did test version 1.3.28..._and_ 1.4 rc 2. Shouldn't we post the first version of Wine to have the bug (unless we haven't gone that far back, in which case we post however far back we went)?
http://bugs.winehq.org/show_bug.cgi?id=29809
--- Comment #3 from Austin English austinenglish@gmail.com 2012-02-05 17:17:03 CST --- (In reply to comment #2)
But I did test version 1.3.28..._and_ 1.4 rc 2. Shouldn't we post the first version of Wine to have the bug (unless we haven't gone that far back, in which case we post however far back we went)?
It's not terribly important, unless it's a regression, then the bug is in all versions (until it's fixed, of course).
http://bugs.winehq.org/show_bug.cgi?id=29809
--- Comment #4 from Jake Thomas jthomas97411@yahoo.com 2012-02-05 23:14:01 CST --- Ok. Knowing that people assume that a bug is for all Wine versions unless explicitly declared as a regression helps. That makes sense.
So you'd actually want to keep the bug report updated to the most recent version of Wine that still has the bug to show that the bug is still in effect and verified to still be in effect, correct?
http://bugs.winehq.org/show_bug.cgi?id=29809
--- Comment #5 from Vitaliy Margolen vitaliy-bugzilla@kievinfo.com 2012-02-06 08:29:27 CST --- (In reply to comment #4)
So you'd actually want to keep the bug report updated to the most recent version of Wine
Yes, you should add a comment of such. But please keep initial reported Wine version unchanged.
http://bugs.winehq.org/show_bug.cgi?id=29809
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Installer
https://bugs.winehq.org/show_bug.cgi?id=29809
--- Comment #6 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.16 or newer) wine?
https://bugs.winehq.org/show_bug.cgi?id=29809
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #7 from Austin English austinenglish@gmail.com --- (In reply to Austin English from comment #6)
This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.16 or newer) wine?
Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=29809
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org