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

Cryptomator window is completely white when restarting macOS and selecting "Lock and quit" #3339

Open
2 tasks done
nickasd opened this issue Feb 18, 2024 · 5 comments
Open
2 tasks done
Labels
misc:gui os:mac type:bug Something isn't working

Comments

@nickasd
Copy link

nickasd commented Feb 18, 2024

Please agree to the following

Summary

Cryptomator window is completely white when restarting macOS and selecting "Lock and quit"

What software is involved?

  • Operating System: macOS 14.3.1
  • Cryptomator: 1.12.0

Volume Type

FUSE-T

Steps to Reproduce

  1. Unlock some vault.
  2. Restart macOS. Select "Lock and quit" in Cryptomator to confirm the restart.
  3. Wait until Cryptomator launches, if necessary activate it by clicking the Dock icon.

Expected Behavior

Cryptomator should relaunch as during a normal launch.

Actual Behavior

The Cryptomator window is completely white.

Screenshot 2024-02-18 alle 15 22 19

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

@nickasd nickasd added the type:bug Something isn't working label Feb 18, 2024
@overheadhunter
Copy link
Member

@tobihagemann I suppose you have 14.3.1 as well? Can you reproduce this?

I can't really explain why "lock and quit" should have any influence on the behaviour after a fresh start, though.

@nickasd
Copy link
Author

nickasd commented Feb 23, 2024

@tobihagemann I suppose you have 14.3.1 as well? Can you reproduce this?

I can't really explain why "lock and quit" should have any influence on the behaviour after a fresh start, though.

Yes. It happened once, then I tried by explicitly locking the vault before restarting macOS and it didn't happen, and when I did "lock and quit" again, it happened again.

@tobihagemann
Copy link
Member

Just wanted to mention that I'm unable to reproduce this. I also can't explain why "lock and quit" should make any difference in this scenario. Sounds more like a coincidence to me.

What do you mean by the following?

Wait until Cryptomator launches, if necessary activate it by clicking the Dock icon.

Which settings have you changed? Did you enable "Launch Cryptomator on system start"? And what about "Hide window when starting Cryptomator"?

@nickasd
Copy link
Author

nickasd commented Mar 4, 2024

What do you mean by the following?

Wait until Cryptomator launches, if necessary activate it by clicking the Dock icon.

I mean in case the app window is not visible, you can show it by clicking the app Dock icon.

Which settings have you changed? Did you enable "Launch Cryptomator on system start"? And what about "Hide window when starting Cryptomator"?

I didn't change any settings. I just have macOS automatically restore all apps and windows that were open when shutting down.

@tobihagemann
Copy link
Member

I just wanted to mention that I was able to observe this behavior after my Mac crashed after a power outage. 😅 I believe this is quite important to reproduce the error:

I just have macOS automatically restore all apps and windows that were open when shutting down.

The only thing I noticed in my log files was that the state of some vaults couldn't be checked because they were located in cloud storage services that use the File Provider Extension. And they probably didn't start up yet.

12:58:43.962 [JavaFX Application Thread] WARN  o.c.common.vaults.VaultListManager - Failed to determine vault state for <redacted>
java.io.IOException: Operation timed out
	at java.base/sun.nio.ch.UnixFileDispatcherImpl.read0(Native Method)
	at java.base/sun.nio.ch.UnixFileDispatcherImpl.read(Unknown Source)
	at java.base/sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source)
	at java.base/sun.nio.ch.IOUtil.read(Unknown Source)
	at java.base/sun.nio.ch.IOUtil.read(Unknown Source)
	at java.base/sun.nio.ch.FileChannelImpl.read(Unknown Source)
	at java.base/sun.nio.ch.ChannelInputStream.read(Unknown Source)
	at java.base/sun.nio.ch.ChannelInputStream.read(Unknown Source)
	at java.base/java.nio.file.Files.read(Unknown Source)
	at java.base/java.nio.file.Files.readAllBytes(Unknown Source)
	at java.base/java.nio.file.Files.readString(Unknown Source)
	at org.cryptomator.desktop@1.12.3/org.cryptomator.common.vaults.VaultConfigCache.readConfigFromStorage(VaultConfigCache.java:61)
	at org.cryptomator.desktop@1.12.3/org.cryptomator.common.vaults.VaultConfigCache.reloadConfig(VaultConfigCache.java:30)
	at org.cryptomator.desktop@1.12.3/org.cryptomator.common.vaults.VaultListManager.create(VaultListManager.java:100)
	at java.base/java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
	at java.base/java.util.AbstractList$RandomAccessSpliterator.forEachRemaining(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.evaluateToArrayNode(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline.toArray(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline.toArray(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline.toList(Unknown Source)
	at org.cryptomator.desktop@1.12.3/org.cryptomator.common.vaults.VaultListManager.addAll(VaultListManager.java:83)
	at org.cryptomator.desktop@1.12.3/org.cryptomator.common.vaults.VaultListManager.<init>(VaultListManager.java:52)
	at org.cryptomator.desktop@1.12.3/org.cryptomator.launcher.DaggerCryptomatorComponent$CryptomatorComponentImpl$SwitchingProvider.get(DaggerCryptomatorComponent.java:9494)
	at dagger@2.50/dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
	at org.cryptomator.desktop@1.12.3/org.cryptomator.launcher.DaggerCryptomatorComponent$FxApplicationComponentImpl$SwitchingProvider.get(DaggerCryptomatorComponent.java:8939)
	at dagger@2.50/dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
	at org.cryptomator.desktop@1.12.3/org.cryptomator.launcher.DaggerCryptomatorComponent$FxApplicationComponentImpl$SwitchingProvider.get(DaggerCryptomatorComponent.java:8926)
	at dagger@2.50/dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
	at org.cryptomator.desktop@1.12.3/org.cryptomator.launcher.DaggerCryptomatorComponent$FxApplicationComponentImpl.application(DaggerCryptomatorComponent.java:8897)
	at org.cryptomator.desktop@1.12.3/org.cryptomator.launcher.Cryptomator$MainApp.start(Cryptomator.java:143)
	at javafx.graphics@21.0.1/com.sun.javafx.application.LauncherImpl.lambda$launchApplication1$9(Unknown Source)
	at javafx.graphics@21.0.1/com.sun.javafx.application.PlatformImpl.lambda$runAndWait$12(Unknown Source)
	at javafx.graphics@21.0.1/com.sun.javafx.application.PlatformImpl.lambda$runLater$10(Unknown Source)
	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
	at javafx.graphics@21.0.1/com.sun.javafx.application.PlatformImpl.lambda$runLater$11(Unknown Source)
	at javafx.graphics@21.0.1/com.sun.glass.ui.InvokeLaterDispatcher$Future.run(Unknown Source)

And if I recall correctly, I was able to open Cryptomator "normally" by closing the window and re-opening it via the menu bar icon. However, the vaults that timed out were somehow broken, and I had to restart Cryptomator in order to unlock them.

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

No branches or pull requests

4 participants