June 2018 - Wine-Bugs - list.winehq.org

[Bug 45325] Ubisoft detection tool dont recognize correctly cpu

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45325 --- Comment #2 from mrdeathjr28(a)yahoo.es --- WINEDEBUG=+relay,+seh,+tid,+timestamp 311mb - 8.6gb descompresssed https://mega.nz/#!rIl1FbaZ!wZ5jIZqHXSqSQVJlH2jeQpnLbRFjmn606CzcUFBwRzk -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 14, 2018

[Bug 35902] Certificates signed using ECDSA signature can not be verified (>= Win Vista - affects EA Origin, Uplay, Blizzard App, MoonBot)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=35902 Daniel Llewellyn <daniel(a)bowlhat.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daniel(a)bowlhat.net -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 14, 2018

[Bug 44887] Pressure sensitivity lost when file requester is opened in ZBrush

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44887 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- Does the issue appear with the demo from https://pixologic.com/zbrush/trial/ ? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 14, 2018

[Bug 44997] Installation support is broken for ElsterFormular 19.3.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44997 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- Works for me with wine-3.10. What exactly is the problem? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 14, 2018

[Bug 45317] updating wine mono does not change version in uninstaller.exe

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45317 --- Comment #14 from Piotr Caban <piotr.caban(a)gmail.com> --- Created attachment 61614 --> https://bugs.winehq.org/attachment.cgi?id=61614 mono msi database changes that also allow downgrade It still doesn't solve the problem of older installers but with this change you can also downgrade mono by doing simple "msiexec /i ...". -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 14, 2018

[Bug 45317] updating wine mono does not change version in uninstaller.exe

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45317 --- Comment #13 from Piotr Caban <piotr.caban(a)gmail.com> --- Created attachment 61613 --> https://bugs.winehq.org/attachment.cgi?id=61613 what needs to be changed on every release (example) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 14, 2018

[Bug 45317] updating wine mono does not change version in uninstaller.exe

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45317 --- Comment #12 from Piotr Caban <piotr.caban(a)gmail.com> --- Created attachment 61612 --> https://bugs.winehq.org/attachment.cgi?id=61612 mono msi database changes This is an example of changes that needs to be made to uninstall older version of mono package. With this changes it behaves quite bad when older version is installed (we end up with 2 version of package being listed in uninstaller). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 14, 2018

[Bug 45317] updating wine mono does not change version in uninstaller.exe

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45317 --- Comment #11 from Piotr Caban <piotr.caban(a)gmail.com> --- It's not a problem for winetricks. It is already checking the UUID from mono running "uninstaller --list |grep Mono |cut -f1 -d\|". It should probably be changed to at least "grep "Wine Mono". There's no problem with transition to this new scheme as long as you don't want to downgrade mono. After changing the installer it should remove all the older versions on install. If you want to downgrade mono, you will need to uninstaller newer version first. I'm not sure what you mean by the "more complicated logic for removing old product". It should be done by msi in RemoveExistingProducts action. Do you think about adding some kind of hack to deal with older installers? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 14, 2018

[Bug 45317] updating wine mono does not change version in uninstaller.exe

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45317 --- Comment #10 from Vincent Povirk <madewokherd(a)gmail.com> --- OK, so it sounds like I need to add an Upgrade table and some upgrade-related actions, keep the UpgradeCode the same between releases, and change the ProductCode every release? I don't know how we can cleanly transition to this from existing releases that do not have an Upgrade table. Also, we will need a way for third-party tools like winetricks to remove Wine Mono regardless of what version is installed. My understanding is that uninstaller --remove uses the ProductCode which would no longer be constant. I guess that in C we would use MsiEnumRelatedProducts to search by upgrade code. Maybe the (now more complicated) logic for removing the old product on upgrade or when needed by winetricks can do in addons.c? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 14, 2018

[Bug 45317] updating wine mono does not change version in uninstaller.exe

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45317 --- Comment #9 from Piotr Caban <piotr.caban(a)gmail.com> --- I've done much more testing and I think that the correct way is to do a "major upgrade" on every mono update. I think so because of the way how update needs to be installed by the user: - major upgrade - it's enough to click on the msi file to install the update, depending on msi file content old version will be preserved or removed - minor upgrade - has identical user deployment methods as small update - small update - needs to be installed as patch or complete reinstall, if you decide to do the minor upgrade new mono versions will need to be installed in following way: msiexec /I wine-mono-4.7.2.msi REINSTALL=ALL REINSTALLMODE=vomus There are also many restrictions regarding what can be done in small and minor upgrade, I don't think you want to pay attention to that on every release. I'll send some tests to msi to show that current behaviour is incomplete but kind of correct. I'll also take a look on how mono msi files are created and attach some propositions for how it can be changed. Vincent, you said that you've never changed the ProductCode because it will "make the new MSI a different package". UpgradeCode is what links them together. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

June 14, 2018