https://bugs.winehq.org/show_bug.cgi?id=50083
Bug ID: 50083 Summary: ASCOM Platform 6.5 - Installation failed Product: Wine Version: 5.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: bammzilla@astronomy.com.ph Distribution: ---
Created attachment 68544 --> https://bugs.winehq.org/attachment.cgi?id=68544 Screenshots of popup error screens during install
The ASCOM Platform allows windows desktop planetarium programs to control astronomical hardware such as telescopes, domes, and cameras.
The software is freely distributable and open source, released under the Creative Commons Attribution-ShareAlike 3.0 License, but written under the .NET Platform.
The latest version is ASCOM Platform 6.5, written under .NET Framework 4.8 and Visual Studio 2019.
To prepare the installation, I ran winetricks -q vcrun2019 dotnet35sp1 dotnet452 dotnet472 dotnet48. No errors were reported in the installation of dotnet.
I then launched the installer with the following command:
WINEDEBUG=+nls wine ASCOMPlatform65.exe >> ASCOMPlatform65.log 2>&1
The installation went smoothly but popped up several error screens and ended with an installation failed.
Screenshots of the error screens are attached.
The WINEDEBUG log file is gzipped and attached.
ASCOMPlatform installer log files are zipped and attached.
Download the installer from the following link: https://github.com/ASCOMInitiative/ASCOMPlatform/releases/download/v6.5Relea...
Full source code of ASCOM Platform is available here: https://github.com/ASCOMInitiative/ASCOMPlatform
ASCOMPlatform License file: https://github.com/ASCOMInitiative/ASCOMPlatform/blob/master/LICENSE.txt
Information about ASCOM can be found here: https://ascom-standards.org/Community/
https://bugs.winehq.org/show_bug.cgi?id=50083
--- Comment #1 from Bamm Gabriana bammzilla@astronomy.com.ph --- Created attachment 68545 --> https://bugs.winehq.org/attachment.cgi?id=68545 ASCOMPlatform setup program log files.
https://bugs.winehq.org/show_bug.cgi?id=50083
--- Comment #2 from Bamm Gabriana bammzilla@astronomy.com.ph --- Created attachment 68546 --> https://bugs.winehq.org/attachment.cgi?id=68546 WINEDEBUG log file (compressed)
I recompressed it as xz because Bugzilla did not allow me to attach the original gzipped file I made since it was too big.
https://bugs.winehq.org/show_bug.cgi?id=50083
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://web.archive.org/202 | |10124131534/https://github. | |com/ASCOMInitiative/ASCOMPl | |atform/releases/download/v6 | |.5SP1Release/ASCOMPlatform6 | |5SP1.exe Ever confirmed|0 |1 CC| |focht@gmx.net Status|UNCONFIRMED |NEW Keywords| |download, Installer Component|-unknown |advapi32
--- Comment #3 from Anastasius Focht focht@gmx.net --- Hello folks,
confirming on behalf of OP. There is a patch posted to wine-devel, mentioning "ASCOM Platform installer":
https://www.winehq.org/pipermail/wine-devel/2021-January/179654.html
It doesn't reference this bug id explicitly though.
---
Generate notes on creating backups/snapshots since you posted download links to github in your comment #0 ...
When creating a ticket I recommend that you immediately create a snapshot of the artifact using Internet Archive (archive.org).
https://addons.mozilla.org/en-US/firefox/addon/wayback-machine_new/
Github is not a "safe backup" when comes to binary release assets. Various Github projects purge their assets after new releases - even if they are hosted on AWS CDN. This makes it hard to retest / reproduce bugs any time.
Example of ASCOM Platform 6.5 release from your comment #0:
https://github.com/ASCOMInitiative/ASCOMPlatform/releases/tag/v6.5Release
https://github.com/ASCOMInitiative/ASCOMPlatform/releases/download/v6.5Relea... = broken download link
Binary release assets are gone, source code tarball is still there in project assets.
Latest release ASCOM Platform 6.5 - Service Pack 1:
https://github.com/ASCOMInitiative/ASCOMPlatform/releases/tag/v6.5SP1Release
Binary release assets are hosted on AWS CDN, source code tarballs in project assets.
https://github.com/ASCOMInitiative/ASCOMPlatform/releases/download/v6.5SP1Re... (valid as of today, 20210124)
---
There is the possibility to archive things using Github mechanics but that's on the project owner/developer responsibility. Never rely on that - even if archived assets exist in the project - they can be still purged as well.
I've created a snapshot via Internet Archive here:
https://web.archive.org/20210124131534/https://github.com/ASCOMInitiative/AS...
Note, when you encounter AWS or similar CDN's that encode a lot of parameters in the final URL, there is a trick to construct a "sane" URL after the snapshot has been created:
https://web.archive.org/<datetimestamp>/<original-url>
Replace '<datetimestamp>' from the snapshot date.
When visiting the link for download you will briefly see:
--- snip --- Loading...
https://github.com/ASCOMInitiative/ASCOMPlatform/releases/download/v6.5SP1Re... | 13:14:35 January 24, 2021
Got an HTTP 302 response at crawl time
Redirecting to...
https://github-production-release-asset-2e65be.s3.amazonaws.com/131588847/60... --- snip ---
It will still resolve to the original artifact.
Above information is generic and probably belongs to a Wiki but well ;-)
$ sha1sum ASCOMPlatform65SP1.exe 7b0d5f8f8cdda70c9fc3da93283451f34ec3b94d ASCOMPlatform65SP1.exe
$ du -sh ASCOMPlatform65SP1.exe 59M ASCOMPlatform65SP1.exe
$ wine --version wine-6.0
Regards
https://bugs.winehq.org/show_bug.cgi?id=50083
--- Comment #4 from Bamm Gabriana bammzilla@astronomy.com.ph --- Sorry for the late reply.
Thank you Anastasius for the confirm, the patch, and for instructions to use Internet Archive. I wasn't aware that github behaved that way. Next time I will no longer link directly to a binary release asset. I'm sorry for my blunder :D
It turns out the installer for 6.5SP1 is identical to the one used in 6.5, and only the installed files were updated. It produced exactly the same errors.
A lot of time has passed since you showed me the patch, and I guessed that it should be in by now. So I tested in the latest Wine 6.20.
I downloaded the source and checked "dlls/advapi32/security.c" and sure enough the source already contained the code in the patch. Since I don't need to apply the patch anymmore, I just installed wine-devel 6.20 and retested on a clean prefix.
~ $ rm -rf .wine ~ $ wine wineboot -u ~ $ winetricks -q vcrun2019 dotnet35sp1 dotnet452 dotnet472 dotnet48 ~ $ wine ./Downloads/ASCOM/ASCOMPlatform65SP1.exe
Note that my current test is ASCOMPlatform 6.5 SP1 on Wine 6.20 whereas my previous test was ASCOMPlatform 6.5 on Wine 5.0.2.
The new test went exactly the same way as the old test I did last year. All three error dialogs still showed up, and the installer quit before finishing with the same error message.
It seems that the patch didn't change anything. :(
I'm on Ubuntu Focal if that matters but I don't think it should, since I got the same result in Debian 11 Bullseye.
I experimented with changing advapi32 to native and got the same results.
I then copied advapi32.dll from Windows on VirtualBox and replaced them on my wine prefix (both the system32 and syswow64 respectively), set advapi32 to native and got the same results (I thought this would make it crash but it didn't).
Hence I suspect the issue is not with advapi32. I don't know why the patch worked for Zebediah who wrote it. (I suspect that Zebediah is somewhat of an astronomy enthusiast like me, since her profile on the CodeWeavers page mentions my favorite childhood show, The Magic School Bus).
Can Zebediah be added to this bug? She might be interested to fix it.
https://bugs.winehq.org/show_bug.cgi?id=50083
Bamm Gabriana bammgabriana@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=50083
--- Comment #5 from Bamm Gabriana bammgabriana@gmail.com --- Hello Zebediah, I added you because I am hoping you can help me identify the issue here, or come up with a workaround, since I see that you installed this program before. All I want is to have a wineprefix with ASCOM successully installed, into which I can install various astronomy programs that require it.
https://bugs.winehq.org/show_bug.cgi?id=50083
--- Comment #6 from Zebediah Figura z.figura12@gmail.com --- I do remember trying to install that software at one point. I remember there being multiple error messages, at least some of which were non-fatal, and I don't think that advapi32 patch fixed more than one of them.
If I get the chance I will try to look at it again, but I would not count on me getting the chance in the near future.
https://bugs.winehq.org/show_bug.cgi?id=50083
--- Comment #7 from Bamm Gabriana bammgabriana@gmail.com --- (In reply to Zebediah Figura from comment #6)
I do remember trying to install that software at one point. I remember there being multiple error messages, at least some of which were non-fatal, and I don't think that advapi32 patch fixed more than one of them.
Thanks. I thought you had succeeded in installing it, so I thought your experience would help me get it running.
If I get the chance I will try to look at it again, but I would not count on me getting the chance in the near future.
That's ok, I'm also working on a few workarounds, including installing it in a Windows VM and seeing which registry entries get added and manually writing those to my Wine prefix. I also noticed a file that gets installed in Windows but not in Wine; probably it gets copied after the crash point.
Bug is still present in Wine 6.21.
https://bugs.winehq.org/show_bug.cgi?id=50083
--- Comment #8 from Zebediah Figura z.figura12@gmail.com --- (In reply to Bamm Gabriana from comment #7)
(In reply to Zebediah Figura from comment #6)
I do remember trying to install that software at one point. I remember there being multiple error messages, at least some of which were non-fatal, and I don't think that advapi32 patch fixed more than one of them.
Thanks. I thought you had succeeded in installing it, so I thought your experience would help me get it running.
Honestly I might have succeeded. It was quite a while ago and I really can't remember unfortunately.
https://bugs.winehq.org/show_bug.cgi?id=50083
--- Comment #9 from Bamm Gabriana bammgabriana@gmail.com --- Now that Wine 10 RC1 is out I will be testing this again.
FYI this is still present in Wine 9.0.
Updated to ASCOM Platform 6.6, same issues. Is there a need for a new bug for a newer version of ASCOM Platform, or do I just keep all the updates here?
-
WineHQ Bugzilla