[Bug 43186] New: 1Password 6.5.401 crashes on login with System.TypeInitializationException

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

Bug ID: 43186
           Summary: 1Password 6.5.401 crashes on login with
                    System.TypeInitializationException
           Product: Wine
           Version: 2.10
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: bcrypt
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 58459
  --> https://bugs.winehq.org/attachment.cgi?id=58459
Stack trace

I applied the PBKDF2 patch
(https://www.winehq.org/pipermail/wine-patches/2017-June/162842.html) to master
(at commit c7f0777fc55229d910461a7a38e21f1e17c8913a), and compiled 32-bit Wine
on 64-bit Ubuntu 16.04.2 LTS.

With a fresh Wine prefix, I followed the steps in
https://bugs.winehq.org/show_bug.cgi?id=43079#c2 (executing the dotnet*
winetricks steps by hand because I couldn't get winetricks to cope with wine in
the git build directory). Upon logging in, 1Password crashed with the following
exception:

Unhandled Exception: System.TypeInitializationException: The type initializer
for 'AgileBits.OnePassword.WindowsDesktopAuthenticatedAes' threw an exception.
---> System.Runtime.InteropServices.COMException: Message 0x not found in file
. (Exception from HRESULT: 0x8007013D)

I believe this may be related to the following warning I receive when I run the
bcrypt tests (wine32-build$ ../wine-source/tools/runtest -p
dlls/bcrypt/tests/bcrypt_test.exe.so):

fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"AES" not supported
bcrypt.c:839: Test marked todo: AES provider not available
fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"AES" not supported
bcrypt.c:928: Test marked todo: AES provider not available
fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"AES" not supported
bcrypt.c:1019: Test marked todo: AES provider not available

[Bug 43186] 1Password 6.5.401 crashes on login with System.TypeInitializationException

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

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from [e-mail] ---
Does any of these help?

https://github.com/wine-compholio/wine-staging/tree/master/patches/bcrypt-Im...

[Bug 43186] 1Password 6.5.401 crashes on login with System.TypeInitializationException

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

Alistair Leslie-Hughes  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
                 CC|                            |[e-mail]
      Fixed by SHA1|                            |b677b58b608212c21fd1f6d2be8
                   |                            |b77583988e88b
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from Alistair Leslie-Hughes  ---
AES support was added in commit
https://source.winehq.org/git/wine.git/?a=commit;h=b677b58b608212c21fd1f6d2b...

Please reopen if the issue still occurs.

[Bug 43186] 1Password 6.5.401 crashes on login with System.TypeInitializationException

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

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #3 from Louis Lenders  ---
Note: Downloaded newest version of 1Password, and seems to be yet another bug,
program doens`t start. Will open a new bugreport.

[Bug 43186] 1Password 6.5.401 crashes on login with System.TypeInitializationException

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

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #4 from Alexandre Julliard  ---
Closing bugs fixed in 3.5.