https://bugs.winehq.org/show_bug.cgi?id=45753
Bug ID: 45753 Summary: Office 2010 reruns setup on starting any app Product: Wine Version: 3.15 Hardware: x86 OS: Linux Status: NEW Keywords: regression Severity: normal Priority: P2 Component: shell32 Assignee: wine-bugs@winehq.org Reporter: dimesio@earthlink.net Regression SHA1: 27edd4e35c1eb3827dfb20578733242d9ed3d460 Distribution: SUSE
This was tested with an existing wineprefix, where Office 2010 was already installed; bug 45208 blocks testing a fresh install.
When starting an installed app, the setup program starts with a message that it is configuring Office. That quickly fails; after closing that window, another one appears with a message that Office was unable to validate the license.
The regression test identified 27edd4e35c1eb3827dfb20578733242d9ed3d460 as the first bad commit.
https://bugs.winehq.org/show_bug.cgi?id=45753
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dmitry@baikal.ru
https://bugs.winehq.org/show_bug.cgi?id=45753
--- Comment #1 from Rosanne DiMesio dimesio@earthlink.net --- I just finished a regression test for what I thought was a separate problem, but it came down to the same commit. The second problem is that .lnk files are no longer displayed on Wine's virtual desktop. This is also an existing wineprefix, but a separate one from Office 2010.
https://bugs.winehq.org/show_bug.cgi?id=45753
--- Comment #2 from Dmitry Timoshkov dmitry@baikal.ru --- This should be retested in new Wine prefix because of an incompatible change in the environment setup.
https://bugs.winehq.org/show_bug.cgi?id=45753
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |45208
--- Comment #3 from Rosanne DiMesio dimesio@earthlink.net --- The .lnk files appear on the virtual desktop in a fresh install, at the inconvenience of having to reinstall apps that were and still are working perfectly fine in the old wineprefix, just to get those links back.
Bug 45208 currently blocks retesting Office 2010 and does not look likely to be fixed any time soon. If it happens in my lifetime, I will certainly retest.
However, I do want to point out that many apps have limited numbers of activations, and expecting people to use them up because of arbitrary changes to the wineprefix seems unreasonable.
https://bugs.winehq.org/show_bug.cgi?id=45753
--- Comment #4 from Dmitry Timoshkov dmitry@baikal.ru --- (In reply to Rosanne DiMesio from comment #3)
However, I do want to point out that many apps have limited numbers of activations, and expecting people to use them up because of arbitrary changes to the wineprefix seems unreasonable.
The changes are not arbitrary, they fix a real bug, and they also bring the Wine prefix environment more closely to Windows 7 and newer variants, which is currently the default reported Wine version.
I guess that the same incompatible change would happen during the Windows XP to Windows 7 upgrade.
https://bugs.winehq.org/show_bug.cgi?id=45753
--- Comment #5 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Dmitry Timoshkov from comment #4)
I guess that the same incompatible change would happen during the Windows XP to Windows 7 upgrade.
I imagine you're right, but both the wineprefixes in question were set to XP and I did not change that. Forced upgrades did not come to Windows until Windows 10.
https://bugs.winehq.org/show_bug.cgi?id=45753
--- Comment #6 from Dmitry Timoshkov dmitry@baikal.ru --- (In reply to Rosanne DiMesio from comment #5)
I guess that the same incompatible change would happen during the Windows XP to Windows 7 upgrade.
I imagine you're right, but both the wineprefixes in question were set to XP and I did not change that. Forced upgrades did not come to Windows until Windows 10.
I'm afraid that using Wine implies the continues forced upgrade... Anyway, this needs a retest before throwing even more speculations, and the retest should be done with default Windows 7 configuration.
https://bugs.winehq.org/show_bug.cgi?id=45753
--- Comment #7 from Austin English austinenglish@gmail.com --- (In reply to Dmitry Timoshkov from comment #6)
(In reply to Rosanne DiMesio from comment #5)
I guess that the same incompatible change would happen during the Windows XP to Windows 7 upgrade.
I imagine you're right, but both the wineprefixes in question were set to XP and I did not change that. Forced upgrades did not come to Windows until Windows 10.
I'm afraid that using Wine implies the continues forced upgrade... Anyway, this needs a retest before throwing even more speculations, and the retest should be done with default Windows 7 configuration.
Users could disable updates to the prefix as a workaround
https://bugs.winehq.org/show_bug.cgi?id=45753
alasky@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alasky@codeweavers.com
https://bugs.winehq.org/show_bug.cgi?id=45753
Josh DuBois duboisj@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |duboisj@codeweavers.com
--- Comment #8 from Josh DuBois duboisj@codeweavers.com --- (In reply to Dmitry Timoshkov from comment #6)
(In reply to Rosanne DiMesio from comment #5)
I guess that the same incompatible change would happen during the Windows XP to Windows 7 upgrade.
I imagine you're right, but both the wineprefixes in question were set to XP and I did not change that. Forced upgrades did not come to Windows until Windows 10.
I'm afraid that using Wine implies the continues forced upgrade... Anyway, this needs a retest before throwing even more speculations, and the retest should be done with default Windows 7 configuration.
Is this really what Wine has always done, or what it should do? I would have hoped that an existing WinXP prefix would not receive a configuration change which would break a previously working prefix / application.
Is it simply too complicated to avoid (either in this case or in general)?
https://bugs.winehq.org/show_bug.cgi?id=45753
--- Comment #9 from Dmitry Timoshkov dmitry@baikal.ru --- (In reply to Josh DuBois from comment #8)
I guess that the same incompatible change would happen during the Windows XP to Windows 7 upgrade.
I imagine you're right, but both the wineprefixes in question were set to XP and I did not change that. Forced upgrades did not come to Windows until Windows 10.
I'm afraid that using Wine implies the continues forced upgrade... Anyway, this needs a retest before throwing even more speculations, and the retest should be done with default Windows 7 configuration.
Is this really what Wine has always done, or what it should do?
It's been always this way. We're just following what Windows does and there are unavoidable incompatible changes. In this particular case there were changes in environment variables.
https://bugs.winehq.org/show_bug.cgi?id=45753
--- Comment #10 from Rosanne DiMesio dimesio@earthlink.net --- (In reply to Dmitry Timoshkov from comment #9)
We're just following what Windows does and there are unavoidable incompatible changes.
Well, no, you're not. I did not change the Windows version from XP, and neither did your patch. What you've done is create a version that reports itself as XP but behaves like a newer version. That would never happen in real Windows.
https://bugs.winehq.org/show_bug.cgi?id=45753
--- Comment #11 from Nikolay Sivov bunglehead@gmail.com --- Rosanne, could you check if fd044802b9de14416b4d5fa723d2596d39402c97 fixes this?
https://bugs.winehq.org/show_bug.cgi?id=45753
--- Comment #12 from Rosanne DiMesio dimesio@earthlink.net --- It doesn't fix it. Office still reruns setup and complains about being unable to validate the license. It also doesn't fix the .lnk files missing from the virtual desktop in my Skyrim wineprefix.
https://bugs.winehq.org/show_bug.cgi?id=45753
--- Comment #13 from Dmitry Timoshkov dmitry@baikal.ru --- Does it work better after 4a6855a575c02aa1569aab8b2e96720fc02f3f26?
https://bugs.winehq.org/show_bug.cgi?id=45753
Ivan Kalvachev iive@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |iive@yahoo.com
--- Comment #14 from Ivan Kalvachev iive@yahoo.com --- *** Bug 45790 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=45753
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #15 from Rosanne DiMesio dimesio@earthlink.net --- That fixes it. Thanks!
https://bugs.winehq.org/show_bug.cgi?id=45753
Rosanne DiMesio dimesio@earthlink.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |4a6855a575c02aa1569aab8b2e9 | |6720fc02f3f26
https://bugs.winehq.org/show_bug.cgi?id=45753
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #16 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 3.16.
https://bugs.winehq.org/show_bug.cgi?id=45753 Bug 45753 depends on bug 45208, which changed state.
Bug 45208 Summary: Microsoft Office 2010 installer crashes at around 50 % mark https://bugs.winehq.org/show_bug.cgi?id=45208
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX
https://bugs.winehq.org/show_bug.cgi?id=45753 Bug 45753 depends on bug 45208, which changed state.
Bug 45208 Summary: Microsoft Office 2010 installer crashes at around 50 % mark https://bugs.winehq.org/show_bug.cgi?id=45208
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX |---
-
wine-bugs＠winehq.org