Just to be clear upfront: We have decided to provide Cryptomator for Linux as an AppImage (https://github.com/cryptomator/cryptomator/issues/469#issuecomment-375342207) and PPA. We are of course happy if anyone wants to provide Cryptomator as a Flatpak app but our official support will be limited on AppImage for now (https://github.com/cryptomator/cryptomator/issues/613#issuecomment-375343166) and PPA.

However, we're open for other methods to provide Cryptomator for Linux that are mainly contributed by the community (AUR being our prime example). We'll provide as much information as we can to make them possible.

To get started on providing Cryptomator as a Flatpak app, please read these comments: https://github.com/cryptomator/cryptomator/issues/613#issuecomment-392441852 and https://github.com/cryptomator/cryptomator/issues/613#issuecomment-420179669.

I'm running macOS High Sierra beta 9. When I attempt to copy large amounts of data (database archive from DEVONthink at around 9.32GB and importing around that amount of data into EagleFiler), the drive seems to unmount as it is no longer available. If I lock the drive and unlock it, I can access it again, although whatever data transfer I was doing to that drive fails. This has been happening since beta 4, although it could have been longer.

I put Cryptomator in debug mode and reproduced the issue, but the entire log file is 49.7MB. I don't know if this is the spot to post it, if there is another method to get this to the developers, or if there is something specific I should look for and post a snippet. I did search for "error" and it returned the following:

10:39:23.910 [AppKit Thread] ERROR o.c.u.controllers.UnlockedController - Reveal failed.
org.cryptomator.frontend.webdav.mount.Mounter$CommandFailedException: Command failed with exit code 1. Expected 0. Stderr: 29:55: execution error: Finder got an error: Handler can’t handle objects of this class. (-10010)
10:39:58.884 [AppKit Thread] ERROR o.c.u.controllers.UnlockedController - Regular unmount failed.
10:40:01.316 [pool-5-thread-94] DEBUG org.eclipse.jetty.server.HttpChannel - HttpChannelOverHttp@4075032a{r=11029,c=false,a=DISPATCHED,uri=//localhost:42427/yEy-HXo8SY8z/Backup_Files/} action ERROR_DISPATCH
500 Server Error HTTP/1.1

Basic Info

I'm using Windows 10 1803 I'm running Cryptomator in version: 1.4 My vault is sitting in google Filestream. The "m" folder and masterkey is cached locally

Description

My vault is sometimes crashing. The best way to repoduce it, is if I copy a file into the vault with Altap Salamander. After a few seconds I get this

The drive still shows up in Windows Explorer but kind of unmounts (listing as empty drive) and other Programms also can not access it anymore.

However Cryptomator still thinks it's mounted. If I unmount and remount (the drive letter is still blocked) and unmount and remount again (to get the same Drive Letter) I can resume the copy operation in Salamander.

The vault is sometimes also crashing as I described above only by using the windows explorer, but much less often. Overall I am very happy with the new dokany system, but I hope I can help you to iron out the last bugs.

Description

When a vault is mounted and I try to rename any folder inside of it, computer freezes and in few seconds crashes and restarts. It produced no logs in debug mode.

System Setup

• Operating system and version: macOS Big Sur 11.0.1
• Cryptomator version: 1.5.10
• Volume type: WebDAV

Steps to Reproduce

1. Open a vault
2. Rename a folder

Expected Behavior

Folder is renamed

Actual Behavior

Computer crashes

Reproducibility

Always

Additional Information

Tried to unmount a vault and now Finder doesn't work. Previously it was fine.

Basic Info

• I'm running Cryptomator on: any Linux
• I'm using Cryptomator in version: 1.2.3

Description

Save password is currently not implemented on Linux systems. Due to differences in the distributions this may not be solvable by using a single API but several interfaces, like Gnome Keyring, will have to be supported.

First step is to investigate which interfaces are the most common (would suggest we should aim at 95% market share) and implement them.

For now the following shall be supported:

• [ ] GNOME Keyring
• [ ] more may follow

Note Extracted this issue from #40. This is a separate feature which can be used on its own without #40 being implemented.

Description

Cryptomator does not show the password page on Linux, making it impossible to unlock the vault. It worked fine in 1.14.11.

System Setup

• Operating system and version: Fedora 30 KDE
• Cryptomator version: 1.14.12
• Drive: Fuse

Steps to Reproduce

1. Attempt to open password page on Linux by clicking the vault
2. Only the robot logo shows
3. You can not unlock the vault

Expected Behavior

Being able to unlock the vault

Actual Behavior

The view doesn't change, therefore you can't type in the password.

Reproducibility

Always

Additional Information

[Any additional information, log files, screenshots, configuration, or data that might be necessary to reproduce the issue.]

Basic Info

This is a bug report.

I'm using Windows in version: 10

I'm running Cryptomator in version: 1.3.1

Description

Today I have got early adopter access for Google Drive File Stream. When I tried it with Cryptomator I got an error Unlock Failed. I got the same error even if I made files available offline. When I copied vault to desktop it all vroked as it should. I have attached log file. I am asking if there is any way that Cryptomator could work with Google Drive File Stream?

log.zip

Mac OS X 10.11.3 When trying to set up a new vault I am asked after I have entered the password of the vault for name and password of "localhost" in a new window. When I enter my normal account username (prefilled) I get an error. See attached screenshot. what's wrong?

Log says this: 09.03.16 17:58:22,000 kernel[0]: hfs: mounted Cryptomator on device disk3s1 09.03.16 17:58:22,216 mds[73]: (Volume.Normal:2464) volume:0x7fb3fa829000 ********** Bootstrapped Creating a default store:1 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Cryptomator 09.03.16 17:58:49,810 Cryptomator[4812]: assertion failed: 15D21: libxpc.dylib + 63930 [61AB4610-9304-354C-9E9B-D57198AE9866]: 0x89 09.03.16 18:03:21,602 Google Drive[784]: /dev/disk3s1 430288 404456 25832 94% 50555 3229 94% /Volumes/Cryptomator

Description

Hello, I can't get Cryptomator to work with OpenSuse Tumbleweed and my vault, or any vault for that matter.

System Setup

*Operating System: openSUSE Tumbleweed 20201007 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.8.12-1-default OS Type: 64-bit

• Cryptomator version: 1.5.8
• Volume type: [Dokany/FUSE]

Steps to Reproduce

1. Start the Appimage / or use the builtkit for Linux
2. Add the vault or create a new one
3. Enter Password
4. Program crashes.

Expected Behavior

Decrypts vault, mounts it.

Actual Behavior

Cryptomator crashes

Reproducibility

Always

Additional Information

See log hs_err_pid30274.log hs_err_pid30825.log

The user should have the possibility to set a specific vault for auto unlock with application start.

Like it MS Bitlocker does, with crypted data partitions, if the system partition is crypted and the user selected a data partition for auto unlock at system start.

Basic Info

• I'm running Cryptomator on: Arch Linux, 4.7.6-1-ARCH
• I'm using Cryptomator in version: 1.2.0

Description

When selecting DAV as the scheme, the mounting process will take a long time. It will fallback to WebDAV. Initially it seems to be fine, but there's a huge memory leak. After a few minutes the system will become unresponsive and maybe crash.

This doesn't happen when directly setting WebDAV as the scheme. Mounting is fast and no memory leak.

EDIT: I spoke too soon. It's also memory leaking. Just a lot slower.

Solution

This seems to be a bug in JavaFX or Mesa and x-org. When using a system with Mesa >= 13.0 and X.org >=1.18.4 there should be no problems.

A user reported that a similar problem occured on Linux Mint 18.2 where Mesa and X.org were already updated. In this case updating to Linux Mint 18.3 solved the issue.

Please agree to the following

• [X] I have searched existing issues for duplicates
• [X] I agree to follow this project's Code of Conduct

Summary

Feature request: Secondary Keyfile

Motivation

As a way to ensure solid protection from brute-forcing, it would be nice if Cryptomator offered the ability to use a keyfile instead of a passphrase, or in addition to one.

A keyfile can then be stored on local devices, like smartphones, desktops, and such... never on the cloud server... and this would go a long way to ensure that if the cloud storage is compromised, there is mitigation against brute-forcing. KeePass has this as an option, as well as VeraCrypt, and it comes in handy, just as a layer of security if storing data on a potentially untrusted device.

Considered Alternatives

There isn't any real alternative to this.

Anything else?

TrueCrypt, VeraCrypt, and KeePass all implement this.

Please agree to the following

• [X] I have searched existing issues for duplicates
• [X] I agree to follow this project's Code of Conduct

Summary

Cryptomator 1.6.17 can not be installed from the official Ubuntu PPA due to a dependency to libffi7 that is not available in the Ubuntu 22.10 repositories

What software is involved?

• Operating System: Kubuntu 22.10 (kinetic)
• Cryptomator: 1.6.17

Volume Type

No response

Steps to Reproduce

1. sudo add-apt-repository ppa:sebastian-stenzel/cryptomator
2. sudo apt install cryptomator

Expected Behavior

Version 1.6.17 can be installed

Actual Behavior

Version 1.6.17 can not be installed

Reproducibility

Always

Relevant Log Output

~# apt install cryptomator
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 cryptomator : Depends: libffi7 but it is not installable
E: Unable to correct problems, you have held broken packages.

Anything else?

libffi7 is not included in the Ubuntu 22.10 (kinetic) repositories: https://packages.ubuntu.com/search?keywords=libffi7&searchon=names&suite=kinetic&section=all

1.6.15 was installable without problems.

1.6.15 dependencies:

libasound2 (>= 1.0.16), libc6 (>= 2.27), libfreetype6 (>= 2.3.5), libgcc1 (>= 1:3.0), libgif7 (>= 5.1), libharfbuzz0b (>= 1.2.6), libjpeg8 (>= 8c), liblcms2-2 (>= 2.2+git20110628), libpng16-16 (>= 1.6.2-1), libstdc++6 (>= 5.2), libx11-6, libxext6, libxi6, libxrender1, libxtst6, zlib1g (>= 1:1.2.2), libfuse2, xdg-utils, libjffi-jni

16.17 dependencies:

libasound2 (>= 1.0.16), libatk1.0-0 (>= 1.12.4), libc6 (>= 2.29), libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.10.0), libfontconfig1 (>= 2.12.6), libfreetype6 (>= 2.3.5), libgdk-pixbuf2.0-0 (>= 2.22.0), libgl1, libglib2.0-0 (>= 2.30.0), libgtk-3-0 (>= 3.0.0), libgtk2.0-0 (>= 2.24.0), libpango-1.0-0 (>= 1.22.0), libpangocairo-1.0-0 (>= 1.14.0), libpangoft2-1.0-0 (>= 1.14.0), libx11-6, libxext6, libxi6, libxrender1, libxtst6, libxxf86vm1, zlib1g (>= 1:1.2.3.4), libfuse2, xdg-utils, libjffi-jni, libffi7

Please agree to the following

• [X] I have searched existing issues for duplicates
• [X] I agree to follow this project's Code of Conduct

Summary

Updating from 1.6.15 to 1.6.17 is not exactly smooth

What software is involved?

• Operating System: Win 10
• Cryptomator: 1.6.17
• …

Volume Type

No response

Steps to Reproduce

I installed 1.6.15 and then, without doing anything else, tried to update it to 1.6.17.

This resulted in an error message along the lines of "Older version of WinFSP already installed. You must uninstall the older version before you can install this one".

According to my OS WinFSP is not installed at all.

I clicked "OK" and the Cryptomator installation carried on as if everything is okay. Is it?!

This is confusing, and it leaves me wondering what the status of Cryptomator is.

Expected Behavior

Update smoothly

Actual Behavior

No idea!

Reproducibility

Always

Relevant Log Output

I have not tried, naturally.

Anything else?

No response

Please agree to the following

• [X] I have searched existing issues for duplicates
• [X] I agree to follow this project's Code of Conduct

Summary

First install - Cryptomator runs but no UI is visible (Windows 10)

What software is involved?

• Operating System: Windows 10 Home edition - 10.0.19045 build 19045
• Cryptomator: -1.6.17 x64

Volume Type

No response

Steps to Reproduce

1. Run Cryptomator
2. Icon is visible on the task bar with an empty fly by window. Selecting it does nothing. alt+tab shows Cryptomator an an empty window but once selected the window in not visible.
3. system tray has the cryptomator icon. right click give 3 options - show, preferences and quit. show does nothing preferences display an empty window with the title preference. looks like the main window is there just invisible. by moving the mouse pointer over it, I can detect the edges (pointer changes shape to a double arrow for re-sizing) if I click in somewhere in the empty space, I get an add vault window, it is visible but it is also empty like the preferences window.
4. The quit option works as intended.

Expected Behavior

Application to launch and run as advertised.

Actual Behavior

See description in steps to reproduce.

Reproducibility

Always

Relevant Log Output

10:13:39.701 [main] INFO  o.c.common.settings.SettingsProvider - Settings loaded from C:\Users\jfran\AppData\Roaming\Cryptomator\settings.json
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - user.home: C:\Users\jfran
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - java.library.path: C:\Program Files\Cryptomator;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin;C:\Program Files (x86)\Intel\iCLS Client\;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Intel\iCLS Client\;C:\Windows\System32;C:\Windows;C:\Windows\System32\wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Boxcryptor\bin\;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\Program Files\PuTTY\;C:\Program Files\Java\jdk-9.0.1\bin;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Windows\System32\OpenSSH\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files (x86)\GnuPG\bin;C:\Program Files\OpenSSL-Win64;;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Docker\Docker\resources\bin;C:\ProgramData\DockerDesktop\version-bin;C:\Users\jfran\AppData\Local\Microsoft\WindowsApps;C:\Users\jfran\AppData\Roaming\Python\Python36\Scripts;;C:\Program Files\Cryptomator\app;.
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - user.language: en
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - user.region: null
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - logback.configurationFile: null
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.settingsPath: ~/AppData/Roaming/Cryptomator/settings.json
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.ipcSocketPath: ~/AppData/Roaming/Cryptomator/ipc.socket
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.integrationsWin.keychainPaths: ~/AppData/Roaming/Cryptomator/keychain.json
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.logDir: ~/AppData/Roaming/Cryptomator
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.loopbackAlias: cryptomator-vault
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.pluginDir: ~/AppData/Roaming/Cryptomator/Plugins
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.mountPointsDir: ~/Cryptomator
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.minPwLength: null
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.appVersion: 1.6.17
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.buildNumber: msi-4104
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.showTrayIcon: true
10:13:39.732 [main] INFO  org.cryptomator.common.Environment - cryptomator.p12Path: ~/AppData/Roaming/Cryptomator/key.p12
10:13:39.732 [main] INFO  o.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.6.17 on Windows 10 10.0 (amd64)
10:13:39.732 [main] DEBUG org.cryptomator.logging.DebugMode - Debug mode enabled
10:13:39.748 [main] DEBUG o.c.launcher.SupportedLanguages - Using system locale
10:13:39.821 [main] INFO  org.cryptomator.ipc.Server - Spawning IPC server listening on socket C:\Users\jfran\AppData\Roaming\Cryptomator\ipc.socket
10:13:39.914 [main] DEBUG o.c.launcher.IpcMessageHandler - Received launch args: 
10:13:39.914 [main] DEBUG o.cryptomator.launcher.Cryptomator - Did not find running application instance. Launching GUI...
10:13:40.370 [JavaFX Application Thread] INFO  o.cryptomator.launcher.Cryptomator - JavaFX runtime started after 1148ms
10:13:40.383 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
10:13:40.416 [JavaFX Application Thread] DEBUG o.cryptomator.common.CommonsModule - Starting App Scheduled Executor 01
10:13:40.419 [App Scheduled Executor 01] DEBUG o.cryptomator.common.CommonsModule - Starting App Scheduled Executor 02
10:13:40.429 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
10:13:40.431 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - UiAppearanceProvider: Found implementation: org.cryptomator.windows.uiappearance.WinUiAppearanceProvider in jar /C:/Program%20Files/Cryptomator/app/mods/integrations-win-1.1.2.jar
10:13:40.468 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - UiAppearanceProvider: Implementation is available: org.cryptomator.windows.uiappearance.WinUiAppearanceProvider
10:13:40.705 [JavaFX Application Thread] TRACE o.cryptomator.ui.fxapp.FxApplication - FxApplication.start()
10:13:40.917 [JavaFX Application Thread] DEBUG o.c.ui.fxapp.FxApplicationTerminator - Enabling sudden termination
10:13:40.929 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
10:13:40.932 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - TrayMenuController: Found implementation: org.cryptomator.ui.traymenu.AwtTrayMenuController in jar /C:/Program%20Files/Cryptomator/app/mods/cryptomator-1.6.17.jar
10:13:40.956 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - TrayMenuController: Implementation is available: org.cryptomator.ui.traymenu.AwtTrayMenuController
10:13:41.101 [JavaFX Application Thread] DEBUG o.c.u.traymenu.AwtTrayMenuController - initialized tray icon
10:13:41.123 [JavaFX Application Thread] DEBUG o.cryptomator.common.CommonsModule - Starting App Background Thread 001
10:13:41.942 [JavaFX Application Thread] DEBUG o.cryptomator.ui.common.FontLoader - Loaded family: Font Awesome 5 Free Solid
10:13:41.995 [JavaFX Application Thread] TRACE o.c.u.m.MainWindowTitleController - init MainWindowTitleController
10:13:42.043 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
10:13:42.047 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - KeychainAccessProvider: Found implementation: org.cryptomator.windows.keychain.WindowsProtectedKeychainAccess in jar /C:/Program%20Files/Cryptomator/app/mods/integrations-win-1.1.2.jar
10:13:42.054 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - KeychainAccessProvider: Implementation is available: org.cryptomator.windows.keychain.WindowsProtectedKeychainAccess
10:13:42.363 [JavaFX Application Thread] TRACE o.c.ui.mainwindow.ResizeController - init ResizeController
10:13:42.371 [JavaFX Application Thread] TRACE o.c.u.m.MainWindowController - init MainWindowController
10:13:42.923 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Main window initialized after 3701ms
10:13:52.078 [JavaFX Application Thread] DEBUG o.c.i.common.ClassLoaderFactory - Found jars in cryptomator.pluginDir: 
10:13:52.080 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - AutoStartProvider: Found implementation: org.cryptomator.windows.autostart.WindowsAutoStart in jar /C:/Program%20Files/Cryptomator/app/mods/integrations-win-1.1.2.jar
10:13:52.089 [JavaFX Application Thread] DEBUG o.c.i.common.IntegrationsLoader - AutoStartProvider: Implementation is available: org.cryptomator.windows.autostart.WindowsAutoStart
10:13:52.254 [JavaFX Application Thread] TRACE o.c.f.fuse.mount.WindowsMounter - Found WinFsp installation at C:\Program Files (x86)\WinFsp\bin\winfsp-x64.dll
10:13:53.119 [App Scheduled Executor 01] DEBUG o.c.common.settings.SettingsProvider - Attempting to save settings to C:\Users\jfran\AppData\Roaming\Cryptomator\settings.json
10:13:53.132 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\jfran\AppData\Roaming\Cryptomator\settings.json
10:14:20.570 [JavaFX Application Thread] INFO  o.cryptomator.launcher.Cryptomator - JavaFX application stopped.
10:14:20.589 [main] INFO  o.cryptomator.launcher.Cryptomator - UI shut down
10:14:20.592 [main] DEBUG org.cryptomator.ipc.Server - IPC server closed
10:14:20.593 [main] INFO  o.cryptomator.launcher.Cryptomator - Exit 0
10:14:20.595 [ShutdownTasks] DEBUG org.cryptomator.common.ShutdownHook - Running graceful shutdown tasks...
10:14:20.595 [ShutdownTasks] DEBUG org.cryptomator.ipc.Server - IPC server closed

Anything else?

Dokan v.2.0.6.1000 files were already was present on the computer. Dokan does not show in the windows application list. WinFSP 2022.2 does show in the application list.

I also have VeraCrypt, BoxCryptor and BoxCryptor classic installed in this computer.

I tried re-installing Dokan but the "installation ended prematurely because of an error" I tried to repair the WinFSP install with the same error. Note: turned debug mode on before generating the log... thought it might help.

thank you.

Please agree to the following

• [X] I have searched existing issues for duplicates
• [X] I agree to follow this project's Code of Conduct

Summary

The UI text is all randomized

What software is involved?

• Operating System: Windows 11 22H2
• Cryptomator: 1.6.17

Volume Type

WebDAV

Steps to Reproduce

1. Search for Cryptomator
2. The software open in tray
3. Right click tray icon, open.
4. It display the UI as show in the screen

Expected Behavior

The UI show a text that you can read.

Actual Behavior

The text UI is impossible to read. The text in the tray icon is fine.

Reproducibility

Always

Relevant Log Output

11:27:48.874 [main] INFO  o.c.common.settings.SettingsProvider - Settings loaded from C:\Users\THIBAULT\AppData\Roaming\Cryptomator\settings.json
11:27:48.893 [main] INFO  org.cryptomator.common.Environment - user.home: C:\Users\THIBAULT
11:27:48.893 [main] INFO  org.cryptomator.common.Environment - java.library.path: C:\Program Files\Cryptomator;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files (x86)\Zulu\zulu-17\bin\;E:\VMware Workstation\bin\;C:\Program Files\Zulu\zulu-17\bin\;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\FirefoxPWA\;C:\Program Files\Go\bin;C:\ProgramData\chocolatey\bin;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Users\THIBAULT\AppData\Local\Programs\Python\Python37\Scripts\;C:\Users\THIBAULT\AppData\Local\Programs\Python\Python37\;C:\Users\THIBAULT\scoop\shims;C:\Users\THIBAULT\AppData\Local\Programs\Python\Python37-32\Scripts\;C:\Users\THIBAULT\AppData\Local\Programs\Python\Python37-32\;C:\Users\THIBAULT\AppData\Local\Microsoft\WindowsApps;C:\Users\THIBAULT\spicetify-cli;C:\Users\THIBAULT\AppData\Local\GitHubDesktop\bin;C:\Users\THIBAULT\AppData\Local\Programs\Microsoft VS Code\bin;G:\Bureau\Bitwarden save;C:\VSCodium\bin;C:\Users\THIBAULT\go\bin;C:\Users\THIBAULT\AppData\Roaming\npm;C:\Users\THIBAULT\AppData\Local\Microsoft\WindowsApps;;C:\Program Files\Cryptomator\app;.
11:27:48.894 [main] INFO  org.cryptomator.common.Environment - user.language: fr
11:27:48.894 [main] INFO  org.cryptomator.common.Environment - user.region: null
11:27:48.894 [main] INFO  org.cryptomator.common.Environment - logback.configurationFile: null
11:27:48.894 [main] INFO  org.cryptomator.common.Environment - cryptomator.settingsPath: ~/AppData/Roaming/Cryptomator/settings.json
11:27:48.894 [main] INFO  org.cryptomator.common.Environment - cryptomator.ipcSocketPath: ~/AppData/Roaming/Cryptomator/ipc.socket
11:27:48.894 [main] INFO  org.cryptomator.common.Environment - cryptomator.integrationsWin.keychainPaths: ~/AppData/Roaming/Cryptomator/keychain.json
11:27:48.894 [main] INFO  org.cryptomator.common.Environment - cryptomator.logDir: ~/AppData/Roaming/Cryptomator
11:27:48.895 [main] INFO  org.cryptomator.common.Environment - cryptomator.loopbackAlias: cryptomator-vault
11:27:48.895 [main] INFO  org.cryptomator.common.Environment - cryptomator.pluginDir: ~/AppData/Roaming/Cryptomator/Plugins
11:27:48.895 [main] INFO  org.cryptomator.common.Environment - cryptomator.mountPointsDir: ~/Cryptomator
11:27:48.895 [main] INFO  org.cryptomator.common.Environment - cryptomator.minPwLength: null
11:27:48.895 [main] INFO  org.cryptomator.common.Environment - cryptomator.appVersion: 1.6.17
11:27:48.895 [main] INFO  org.cryptomator.common.Environment - cryptomator.buildNumber: msi-4104
11:27:48.895 [main] INFO  org.cryptomator.common.Environment - cryptomator.showTrayIcon: true
11:27:48.895 [main] INFO  org.cryptomator.common.Environment - cryptomator.p12Path: ~/AppData/Roaming/Cryptomator/key.p12
11:27:48.896 [main] INFO  o.cryptomator.launcher.Cryptomator - Starting Cryptomator 1.6.17 on Windows 11 10.0 (amd64)
11:27:48.965 [main] INFO  org.cryptomator.ipc.Server - Spawning IPC server listening on socket C:\Users\THIBAULT\AppData\Roaming\Cryptomator\ipc.socket
11:27:49.313 [JavaFX Application Thread] INFO  o.cryptomator.launcher.Cryptomator - JavaFX runtime started after 751ms
11:27:54.938 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\THIBAULT\AppData\Roaming\Cryptomator\settings.json
11:27:55.755 [JavaFX Application Thread] INFO  o.cryptomator.ui.fxapp.UpdateChecker - Current version: 1.6.17, lastest version: 1.6.17
11:27:57.252 [App Scheduled Executor 01] INFO  o.c.common.settings.SettingsProvider - Settings saved to C:\Users\THIBAULT\AppData\Roaming\Cryptomator\settings.json

Anything else?

Didn't opened cryptomator for a few days or weeks. And this started to happen today. Repair does not solve it. Software reinstall also does not solve this.

This is the first part to provide Autoupdate for Cryptomator.

This PR requires an extension to the integrations-api (thanks to @infeo and the other Cryptomator devs for their help on how to use the optional integrations-api interfaces): https://github.com/cryptomator/integrations-api/pull/15

and a reflection of the change in integrations-win: https://github.com/cryptomator/integrations-win/pull/16

Some notes on WinSparkle

WinSparkle is designed the way, that it brings up a pop-up (enable or disable the search for updates etc.) on the second start of an application / Cryptomator. So you have to start Cryptomator, end it and start it again to show the pop-up.

It might help to delete the according Registry entry Software\Skymatic GmbH\Cryptomator\WinSparkle for testing purposes as WinSparkle also knows, whether is has been started in the past and delays further pop-ups. WinSparkle stores all this in the Registry entries and deleting them brings up the pop-up on second start of Cryptomator. See: https://github.com/vslavik/winsparkle/wiki/Registry-Settings

WinSparkle expects a base64 encoded SHA1 hash of the installer binary copied to the appcast.xml, that contains information about updates. WinSparkle provides scripts to generate these hashes and the key pair needed as a starting point.