Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac Air, 2022, Apple Silicon, M2 ... freeze on vault lock... #2436

Closed
2 tasks done
henderjon opened this issue Sep 11, 2022 · 14 comments
Closed
2 tasks done

Mac Air, 2022, Apple Silicon, M2 ... freeze on vault lock... #2436

henderjon opened this issue Sep 11, 2022 · 14 comments
Labels
type:bug Something isn't working
Milestone

Comments

@henderjon
Copy link

Please agree to the following

Summary

cryptomator completely freezes when I ask it to lock vault

What software is involved?

  • Operating System: MacOS Monterrey 12.5.1
  • Cryptomator: 1.6.14
  • Cryptomator unlocks vaults fine and I can add files to vault. When I tell Cryptomator to "lock" the individual vault or even "lock all" Cryptomator completely freezes. The entire OS is interrupted. Cryptomator stops responding and I can't force quit. Mac can't restart. The process is gone from Activity Monitor. The only way to to interact with Cryptomator in any way is to force restart.

Volume Type

WebDAV

Steps to Reproduce

  1. [First Step] Unlock a vault
  2. [Second Step] Add a file
  3. Try to lock vault.

Expected Behavior

Cryptomator locks and resumes normal operation.

Actual Behavior

Cryptomator doesn't quit and won't restart and completely locks up.

Reproducibility

Always

Relevant Log Output

18:13:55.565 [main] INFO  o.c.common.settings.SettingsProvider - Settings loaded from /Users/henderjon/Library/Application Support/Cryptomator/settings.json
18:13:55.571 [main] INFO  org.cryptomator.common.Environment - user.home: /Users/henderjon
18:13:55.571 [main] INFO  org.cryptomator.common.Environment - java.library.path: :/Applications/Cryptomator.app/Contents/app:/Users/henderjon/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - user.language: en
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - user.region: null
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - logback.configurationFile: null
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - cryptomator.settingsPath: ~/Library/Application Support/Cryptomator/settings.json
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - cryptomator.ipcSocketPath: ~/Library/Application Support/Cryptomator/ipc.socket
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - cryptomator.integrationsWin.keychainPaths: null
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - cryptomator.logDir: ~/Library/Logs/Cryptomator
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - cryptomator.pluginDir: ~/Library/Application Support/Cryptomator/Plugins
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - cryptomator.mountPointsDir: null
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - cryptomator.minPwLength: null
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - cryptomator.appVersion: 1.6.14
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - cryptomator.buildNumber: dmg-3947
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - cryptomator.showTrayIcon: true
18:13:55.572 [main] INFO  org.cryptomator.common.Environment - cryptomator.p12Path: ~/Library/Application Support/Cryptomator/key.p12
18:13:55.572 [main] INFO  o.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.6.14 on Mac OS X 12.5.1 (aarch64)
18:13:55.572 [main] DEBUG org.cryptomator.logging.DebugMode - Debug mode enabled
18:13:55.572 [main] DEBUG o.c.launcher.SupportedLanguages - Using system locale
18:13:55.586 [main] INFO  org.cryptomator.ipc.Server - Spawning IPC server listening on socket /Users/henderjon/Library/Application Support/Cryptomator/ipc.socket
18:13:55.889 [main] DEBUG o.c.launcher.IpcMessageHandler - Received launch args: 
18:13:55.895 [main] DEBUG o.cryptomator.launcher.Cryptomator - Did not find running application instance. Launching GUI...
18:13:56.221 [JavaFX Application Thread] INFO  o.cryptomator.launcher.Cryptomator - JavaFX runtime started after 800ms
18:13:56.225 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
18:13:56.227 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - TrayIntegrationProvider: Found implementation: org.cryptomator.macos.tray.MacTrayIntegrationProvider in jar /Applications/Cryptomator.app/Contents/app/mods/integrations-mac-1.1.2.jar
18:13:56.234 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - TrayIntegrationProvider: Implementation is available: org.cryptomator.macos.tray.MacTrayIntegrationProvider
18:13:56.334 [JavaFX Application Thread] DEBUG o.cryptomator.common.CommonsModule - Starting App Scheduled Executor 01
18:13:56.335 [App Scheduled Executor 01] DEBUG o.cryptomator.common.CommonsModule - Starting App Scheduled Executor 02
18:13:56.336 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
18:13:56.337 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - UiAppearanceProvider: Found implementation: org.cryptomator.macos.uiappearance.MacUiAppearanceProvider in jar /Applications/Cryptomator.app/Contents/app/mods/integrations-mac-1.1.2.jar
18:13:56.337 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - UiAppearanceProvider: Implementation is available: org.cryptomator.macos.uiappearance.MacUiAppearanceProvider
18:13:56.411 [JavaFX Application Thread] TRACE o.cryptomator.ui.fxapp.FxApplication - FxApplication.start()
18:13:56.678 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationTerminator - Enabling sudden termination
18:13:56.679 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
18:13:56.680 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - TrayMenuController: Found implementation: org.cryptomator.ui.traymenu.AwtTrayMenuController in jar /Applications/Cryptomator.app/Contents/app/mods/cryptomator-1.6.14.jar
18:13:56.684 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - TrayMenuController: Implementation is available: org.cryptomator.ui.traymenu.AwtTrayMenuController
18:13:56.770 [JavaFX Application Thread] DEBUG o.c.u.traymenu.AwtTrayMenuController - initialized tray icon
18:13:56.778 [JavaFX Application Thread] DEBUG o.cryptomator.common.CommonsModule - Starting App Background Thread 001
18:13:57.208 [JavaFX Application Thread] DEBUG o.cryptomator.ui.common.FontLoader - Loaded family: Font Awesome 5 Free Solid
18:13:57.221 [JavaFX Application Thread] TRACE o.c.u.m.MainWindowTitleController - init MainWindowTitleController
18:13:57.233 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
18:13:57.234 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - KeychainAccessProvider: Found implementation: org.cryptomator.macos.keychain.MacSystemKeychainAccess in jar /Applications/Cryptomator.app/Contents/app/mods/integrations-mac-1.1.2.jar
18:13:57.235 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - KeychainAccessProvider: Implementation is available: org.cryptomator.macos.keychain.MacSystemKeychainAccess
18:13:57.990 [JavaFX Application Thread] TRACE o.c.ui.mainwindow.ResizeController - init ResizeController
18:13:57.991 [JavaFX Application Thread] TRACE o.c.u.m.MainWindowController - init MainWindowController
18:13:58.002 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - visible windows: 1
18:13:58.235 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - visible windows: 0
18:13:58.254 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Main window initialized after 2833ms
18:15:16.189 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
18:15:16.190 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - AutoStartProvider: Found implementation: org.cryptomator.macos.autostart.MacAutoStartProvider in jar /Applications/Cryptomator.app/Contents/app/mods/integrations-mac-1.1.2.jar
18:15:16.191 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - AutoStartProvider: Implementation is available: org.cryptomator.macos.autostart.MacAutoStartProvider
18:15:16.284 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - visible windows: 1
18:15:17.219 [App Scheduled Executor 01] DEBUG o.c.common.settings.SettingsProvider - Attempting to save settings to /Users/henderjon/Library/Application Support/Cryptomator/settings.json
18:15:17.226 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/henderjon/Library/Application Support/Cryptomator/settings.json
18:15:18.781 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - visible windows: 2
18:15:19.808 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - visible windows: 1
18:15:20.814 [App Scheduled Executor 02] DEBUG o.c.common.settings.SettingsProvider - Attempting to save settings to /Users/henderjon/Library/Application Support/Cryptomator/settings.json
18:15:20.817 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to /Users/henderjon/Library/Application Support/Cryptomator/settings.json
18:15:22.825 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - visible windows: 0
19:45:15.176 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - visible windows: 1
19:45:21.319 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - visible windows: 0
19:45:33.703 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - visible windows: 1
19:49:34.009 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationWindows - visible windows: 0

Anything else?

No response

@henderjon henderjon added the type:bug Something isn't working label Sep 11, 2022
@overheadhunter
Copy link
Member

Similar behaviour has been reported previously: #1824

WebDAV seems to be just terribly broken on ARM Macs. I mean: Even if Cryptomator (or some other WebDAV service) sends malformed responses or times out, the OS should still be in control to safely disconnect from such as server.

As suggested in #1824, the only real option is to install and use macFUSE for mounting the vaults.

@henderjon
Copy link
Author

Something I noticed that might help ... I was right-clicking the dock icon and choosing "Show All Windows" ... nothing would happen. I started adding desktops/workspaces (Mission Control). Even though I had none set up, Cryptomator's window was being display off screen.

I had to find a second monitor before I could see the window. Once I did that, everything seemed to start working as expected again ...

@liqfx
Copy link

liqfx commented Sep 17, 2022

The below works on M1 Macbook Pro 14" running Monterey 12.6 and Cryptomator 1.6.14 as a work around.

  1. Open Cryptomator and unlock vault.
  2. Do what you want in open vault (open, edit files etc)
  3. When you’re ready to lock vault open finder
  4. In the sidebar on the left under “Locations” you will see “localhost”. Click on in.
  5. On the right you will see “Connected as: WebDAV” and on the far right is a disconnect button.
  6. Click the disconnect button.
  7. Once localhost volume is disconnected, return to cryptomator app and now click “Lock”
  8. The vault should lock without problem and you can close Cryptomator.

Much prefer this method to having to use MacFUSE because I can leave the system in normal security mode without opening up the kernal extensions.

Hope this helps someone

@piridium
Copy link

I've got the same issue on a M1Max and the solution proposed by @liqfx to first disconnect the localhost volume works for me, too.

@theskollie
Copy link

@liqfx solution works for now. would love to see a solid fix for this

@nicojerome
Copy link

Can confirm this issue on M1 MacBook Air with Ventura 13.0.1. Need to Eject the localhost or disconnect WebDav first before locking the vault. Otherwise, the entire application freezes and becomes non-responsive. Only a (system) restart helps.

It's actually kinda scary behavior. Every time I forget about disconnecting the WebDav first, the application freezes while locking the vault and I always pray that it didn't damage the vault.

@woshiniming007
Copy link

woshiniming007 commented Dec 7, 2022

This solution does not work for me. When I click the eject button, the system has actually gone into a stuck state and I cannot not lock in the cryptomator or restart the mac. I can only force a reboot. 😭

@piridium
Copy link

piridium commented Dec 7, 2022

This solution does not work for me. When I click the eject button, the system has actually gone into a stuck state and I cannot not lock in the cryptomator or restart the mac. I can only force a reboot. 😭

This solution does not always work for me either...
Experience shows that the chances of success are greater if all programs that have accessed files in the vault (especially MS Word) are closed first, then all Finder windows of the vault are closed, and only then is the volume ejected and the vault locked.

@nicojerome
Copy link

This solution does not work for me. When I click the eject button, the system has actually gone into a stuck state and I cannot not lock in the cryptomator or restart the mac. I can only force a reboot. 😭

This solution does not always work for me either... Experience shows that the chances of success are greater if all programs that have accessed files in the vault (especially MS Word) are closed first, then all Finder windows of the vault are closed, and only then is the volume ejected and the vault locked.

Exactly. Just experienced the same as well. Heres how to replicate:

  1. Open Vault
  2. Add File (eg Image)
  3. Open this image in Preview app
  4. Close Preview window with the red X bitton (but don't close Preview app)
  5. Try Locking vault ... doesnt work (File in use)
  6. Click Retry .... doenst work
  7. Eject the vault drive in Finder or Disconnect WebDav (according to solution above)
  8. Try Locking vault again ... Cryptomator app freezes entirely, Mac freezes in many other areas as well, becomes unusable. Not even force quitting the Cryptomator app works, only a Mac Restart helps

The solution above with the Ejecting first before locking the vault doesn't work when apps that accessed some files of the vault are still open. It used to work for me but now the only workaround for this freezings issue seems to be this:

  1. Close all apps
  2. Eject vault/webdav
  3. Only then Lock Vault

@tobihagemann tobihagemann added this to the 1.7.0 milestone Jan 9, 2023
@infeo
Copy link
Member

infeo commented Mar 6, 2023

Cryptomator 1.7.0 supports the new volume type FUSE-T, which is easier to install than MacFuse and more stable than WebDAV. It is the recommendation for M1 Macs.

@infeo infeo closed this as completed Mar 6, 2023
@Uj947nXmRqV2nRaWshKtHzTvckUUpD

fuse-t freezes like hell the whole MAC OS (v13) all apps using documents from inside the vault freeze as well. can't even reboot the laptop. instead had to hard power off. this needs to be fixed asap

@ethicnology
Copy link

I'm living the same nightmare on M2

This solution does not work for me. When I click the eject button, the system has actually gone into a stuck state and I cannot not lock in the cryptomator or restart the mac. I can only force a reboot. 😭

This solution does not always work for me either... Experience shows that the chances of success are greater if all programs that have accessed files in the vault (especially MS Word) are closed first, then all Finder windows of the vault are closed, and only then is the volume ejected and the vault locked.

Exactly. Just experienced the same as well. Heres how to replicate:

1. Open Vault

2. Add File (eg Image)

3. Open this image in Preview app

4. Close Preview window with the red X bitton (but don't close Preview app)

5. Try Locking vault ... doesnt work (File in use)

6. Click Retry .... doenst work

7. Eject the vault drive in Finder or Disconnect WebDav (according to solution above)

8. Try Locking vault again ... Cryptomator app freezes entirely, Mac freezes in many other areas as well, becomes unusable. Not even force quitting the Cryptomator app works, only a Mac Restart helps

The solution above with the Ejecting first before locking the vault doesn't work when apps that accessed some files of the vault are still open. It used to work for me but now the only workaround for this freezings issue seems to be this:

1. Close **all** apps

2. Eject vault/webdav

3. Only then Lock Vault

@piridium
Copy link

piridium commented Sep 7, 2023

fuse-t freezes like hell the whole MAC OS (v13) all apps using documents from inside the vault freeze as well. can't even reboot the laptop. instead had to hard power off. this needs to be fixed asap

Fortunately, I can not confirm this. I installed fuse-t and fuse-t-sshfs via homebrew and so far I did not experience any vault or os freezes.
I might add that I am still using to the procedure "close all apps / eject drive / lock vault" but I don't know if this has any effect.
@fusionneur I assume you did, besides installing fuse-t, enable 'fuse-t' in the cryptomator settings, didn't you?

@Uj947nXmRqV2nRaWshKtHzTvckUUpD

fuse-t freezes like hell the whole MAC OS (v13) all apps using documents from inside the vault freeze as well. can't even reboot the laptop. instead had to hard power off. this needs to be fixed asap

Fortunately, I can not confirm this. I installed fuse-t and fuse-t-sshfs via homebrew and so far I did not experience any vault or os freezes. I might add that I am still using to the procedure "close all apps / eject drive / lock vault" but I don't know if this has any effect. @fusionneur I assume you did, besides installing fuse-t, enable 'fuse-t' in the cryptomator settings, didn't you?

yes, I opened an issue where it's being tracked #3085

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests