[Bug 46206] New: Altium Designer 17 account sign in fails as of 3.19

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=46206

            Bug ID: 46206
           Summary: Altium Designer 17 account sign in fails as of 3.19
           Product: Wine
           Version: 3.19
          Hardware: x86-64
               URL: https://s3.amazonaws.com/altium-release-manager/Altium
                    _Designer_17/OfflineSetup_Altium_Designer_Public_17_1_
                    9.zip
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: wine-bugs at winehq.org
          Reporter: jhansonxi at gmail.com
      Distribution: Ubuntu

Account sign-ins are broken in Altium Designer 17.1.9 (and probably other
releases) as of Wine 3.19.

Steps to reproduce:

1. Launch Altium Designer.

2. Close floating window (Storage, etc.) which will likely trigger an error
(probably bug #39765 which I'll verify later)

3. At MyAccount/License Management page click "Sign in" link

4. At "Account Sign In" dialog (which can get stuck behind main window) enter
anything for user name and password, check the "I have read and understand the
warning" privacy invasion checkbox, then the "Sign in" button.

Expected behavior:
Dialog box closes then reappears a moment later when sign-in fails.

Wine 3.19-3.21 behavior:
Dialog closes then an "Out of memory" error dialog is displayed.


Installation:

1. Download the offline installer from the URL (3.6GB).  Extract to
subdirectory.

2. winetricks -q corefonts dotnet461 mdac28 win7

I used winetricks 20180815-next.  Verified NET Runtimes with
netfx_setupverifier-20180517.exe.  Manually triggered GAC rebuild via ngen.exe
since winetricks didn't seem to do so and it cluttered up the logs when it
randomly started on its own.

3. Run the Altium installer.  To save time deselect the optional items.


Other:
There's a nuisance rundll32.exe error at start-up reporting "This application
could not be started".  It doesn't seem to be related to this bug although I
haven't found the cause of it yet.

-- 
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.