Version 1.6.1 on Linux hangs when creating a vault

A_S · October 26, 2021, 8:23am

OS: Linux Mint 20 based on Ubuntu
Volume Type: FUSE

After I press the button Create Vault nothing happens - wait icon runs for ever.
[JavaFX Application Thread] DEBUG o.c.u.a.AddVaultWelcomeController - AddVaultWelcomeController.createNewVault()
[JavaFX Application Thread] DEBUG org.cryptomator.common.CommonsModule - Starting App Background Thread 003

Everything works fine with version 1.5.17
Any idea what can be wrong?

infeo · October 27, 2021, 3:24pm

Welcome to the Cryptomator Community ,

Is this the button at the end of the “Add new Vault” wizard or which button are we talking about? A screenshot would be helpful (:

A_S · October 27, 2021, 5:09pm

Add Vault dialog
Add_Vault

infeo · October 28, 2021, 3:13pm

From the technical perspective, on your system Cryptomator is stuck in this piece of code:

github.com

cryptomator/cryptomator/blob/a79e385594e7d466ae1caa4d39b759ccc4058767/src/main/java/org/cryptomator/ui/addvaultwizard/CreateNewVaultPasswordController.java#L177-L207

    
      
          	private void initializeVault(Path path) throws IOException {
          		// 1. write masterkey:
          		Path masterkeyFilePath = path.resolve(MASTERKEY_FILENAME);
          		try (Masterkey masterkey = Masterkey.generate(csprng)) {
          			masterkeyFileAccess.persist(masterkey, masterkeyFilePath, newPasswordSceneController.passwordField.getCharacters());
          
          
			// 2. initialize vault:
          			try {
          				MasterkeyLoader loader = ignored -> masterkey.copy();
          				CryptoFileSystemProperties fsProps = CryptoFileSystemProperties.cryptoFileSystemProperties().withCipherCombo(CryptorProvider.Scheme.SIV_CTRMAC).withKeyLoader(loader).build();
          				CryptoFileSystemProvider.initialize(path, fsProps, DEFAULT_KEY_ID);
          
          
				// 3. write vault-internal readme file:
          				String vaultReadmeFileName = resourceBundle.getString("addvault.new.readme.accessLocation.fileName");
          				try (FileSystem fs = CryptoFileSystemProvider.newFileSystem(path, fsProps); //
          					 WritableByteChannel ch = Files.newByteChannel(fs.getPath("/", vaultReadmeFileName), StandardOpenOption.CREATE_NEW, StandardOpenOption.WRITE)) {
          					ch.write(US_ASCII.encode(readmeGenerator.createVaultAccessLocationReadmeRtf()));
          				}
          			} catch (CryptoException e) {
          				throw new IOException("Failed initialize vault.", e);

This file has been truncated. show original

The comments (lines starting with //) describe the different phases. Before 2, a file called masterkey.cryptomator should be placed into your vault storage location. Before 3, the d directory and the vault.cryptomator file shoul additionally exist. Before 4, inside the d directory there should exist 2 folders and file, stacked inside each other. And at the end of the method, a file called IMPORTANT.rtf should exists additionally in your vault directory.

When you try to create a vault, which of the files and directories mentioned above are present?

A_S · October 28, 2021, 7:11pm

I was too impatient - vault creation just takes a long time - up to 5 min

at first the masterkey.cryptomator.tmp is created and then a long time nothing happens
and then after x minutes all the other files and directories are created

I missed to mention that the vault is written into a mounted webdav directory.
For mounting I use davfs2 and fstab
$webdavurl /mnt/$mntdir davfs defaults,_netdev,user,uid=$localuser,gid=$localusergroup 0 0

However same behavior if you create a vault in a local directory.

**18:41**:28.778 [JavaFX Application Thread] DEBUG o.c.u.a.AddVaultWelcomeController - AddVaultWelcomeController.createNewVault()
**18:45**:59.961 [App Background Thread 006] DEBUG o.cryptomator.cryptofs.ReadonlyFlag - Vault opened for read and write.
18:46:00.137 [App Background Thread 006] TRACE o.c.cryptofs.fh.FileHeaderHolder - Generating file header for /mnt/web.de/bug_test6/d/NY/WZRORUAZPHBAXOJ35DVFBN32LB7ECJ/noGyZqMsmKgsPpumgMGf6THLrCwBHvnCjts_.c9r
18:46:00.137 [App Background Thread 006] DEBUG o.c.c.common.ReseedingSecureRandom - Seeding CSPRNG with 55 bytes...
18:46:58.818 [App Background Thread 006] DEBUG o.c.c.common.ReseedingSecureRandom - Seeded CSPRNG.
18:46:58.819 [App Background Thread 006] TRACE o.c.cryptofs.fh.OpenCryptoFile - First channel for this openFile. Initializing file size...
18:46:58.820 [App Background Thread 006] TRACE o.c.cryptofs.ch.CleartextFileChannel - org.cryptomator.cryptofs.ch.CleartextFileChannel@29ad2d4 - Writing file header.
18:46:59.575 [App Background Thread 006] INFO  o.c.u.a.CreateNewVaultPasswordController - Created vault at /mnt/web.de/bug_test6

**18:48**:39.507 [JavaFX Application Thread] DEBUG o.c.u.a.AddVaultWelcomeController - AddVaultWelcomeController.createNewVault()
**18:53**:51.172 [App Background Thread 006] DEBUG o.cryptomator.cryptofs.ReadonlyFlag - Vault opened for read and write.
18:53:51.534 [App Background Thread 006] TRACE o.c.cryptofs.fh.FileHeaderHolder - Generating file header for /mnt/web.de/bug_test7/d/4I/XTOAXA5SWVL7ZTNL7FMV23T72JL776/HnUVT4kIs3kwCJRCKYOH8-CSwnstqE9QQSax.c9r
18:53:51.535 [App Background Thread 006] DEBUG o.c.c.common.ReseedingSecureRandom - Seeding CSPRNG with 55 bytes...
18:54:19.455 [App Background Thread 006] DEBUG o.c.c.common.ReseedingSecureRandom - Seeded CSPRNG.
18:54:19.456 [App Background Thread 006] TRACE o.c.cryptofs.fh.OpenCryptoFile - First channel for this openFile. Initializing file size...
18:54:19.456 [App Background Thread 006] TRACE o.c.cryptofs.ch.CleartextFileChannel - org.cryptomator.cryptofs.ch.CleartextFileChannel@66571b87 - Writing file header.
18:54:19.681 [App Background Thread 006] INFO  o.c.u.a.CreateNewVaultPasswordController - Created vault at /mnt/web.de/bug_test7
18:54:20.685 [App Scheduled Executor 02] DEBUG o.c.common.settings.SettingsProvider - Attempting to save settings to /home/andreas/.config/Cryptomator/settings.json
18:54:20.686 [App Scheduled Executor 02] INFO  o.c.common.settings.SettingsProvider - Settings saved to /home/andreas/.config/Cryptomator/settings.json
18:54:25.572 [JavaFX Application Thread] DEBUG o.c.common.vaults.VaultStats - stop recording stats
18:54:25.573 [JavaFX Application Thread] DEBUG o.c.ui.launcher.AppLifecycleListener - Allow quitting without prompt: false
18:54:25.613 [JavaFX Application Thread] DEBUG o.cryptomator.ui.fxapp.FxApplication - Start unlock workflow for bug_test7

infeo · October 29, 2021, 10:36am

Did you installed Cryptomator via apt/ppa or are you using the AppImage?

I can reproduce the problem with the apt installed version. ~~With the AppImage, the vault creation finishes instantly.~~

Edit: I take that back, only the first time, afterwards it takes as long as the ppa.

infeo · October 29, 2021, 11:52am

I created a bug ticket on the issue tracker:

github.com/cryptomator/cryptomator

Linux Mint 20: Vault creation takes very long time

opened 11:52AM - 29 Oct 21 UTC

infeo

type:bug

### Please agree to the following - [X] I have searched [existing issues](https…://github.com/cryptomator/cryptomator/issues?q=) for duplicates - [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md) ### Summary Creating a new vault on Linux Mint 20 with Cryptomator takes very long until it is finished (at least 5min). ### What software is involved? - Operating System: Linux Mint 20, Linux user 5.4.0-89-generic #100-Ubuntu - Cryptomator: 1.6.1 ### Volume Type _No response_ ### Steps to Reproduce 1. Click "Add Vault" button in main GUI 2. Navigate through the wizard to the "Create Password" screen 3. Click "Create Vault" button ### Expected Behavior Action finishes in a timely manner and next screen is shown. ### Actual Behavior Action takes very long, around 5min. ### Reproducibility Always ### Relevant Log Output ```shell Extendend https://github.com/cryptomator/cryptomator/blob/a79e385594e7d466ae1caa4d39b759ccc4058767/src/main/java/org/cryptomator/ui/addvaultwizard/CreateNewVaultPasswordController.java#L177-L207 with addtional log output. ---- 13:41:05.202 [App Background Thread 003] INFO o.c.u.a.CreateNewVaultPasswordController - Initialize vault 13:42:48.750 [App Background Thread 003] INFO o.c.u.a.CreateNewVaultPasswordController - Successfully generated masterkey. 13:46:47.604 [App Background Thread 003] INFO o.c.u.a.CreateNewVaultPasswordController - Masterkeyfile persisted 13:46:47.616 [App Background Thread 003] INFO o.c.u.a.CreateNewVaultPasswordController - Vault config created 13:46:47.632 [App Background Thread 003] DEBUG o.cryptomator.cryptofs.ReadonlyFlag - Vault opened for read and write. 13:46:47.648 [App Background Thread 003] TRACE o.c.cryptofs.fh.FileHeaderHolder - Generating file header for /home/alf/asd/d/7L/Q7EFA4DUASKFZLXENY2EEKINCYUIMD/jO_HiZ-u-7DpZqAZv582So5ALLJIlI4dCPAo.c9r 13:46:47.649 [App Background Thread 003] DEBUG o.c.c.common.ReseedingSecureRandom - Seeding CSPRNG with 55 bytes... 13:47:14.765 [App Background Thread 003] DEBUG o.c.c.common.ReseedingSecureRandom - Seeded CSPRNG. 13:47:14.766 [App Background Thread 003] TRACE o.c.cryptofs.fh.OpenCryptoFile - First channel for this openFile. Initializing file size... 13:47:14.773 [App Background Thread 003] TRACE o.c.cryptofs.ch.CleartextFileChannel - org.cryptomator.cryptofs.ch.CleartextFileChannel@560d6582 - Writing file header. 13:47:14.777 [App Background Thread 003] INFO o.c.u.a.CreateNewVaultPasswordController - Stored README inside vault. 13:47:14.778 [App Background Thread 003] INFO o.c.u.a.CreateNewVaultPasswordController - Created vault at /home/alf/asd ``` ### Anything else? This was first mentioned in our forum, see https://community.cryptomator.org/t/version-1-6-1-on-linux-hangs-when-creating-a-vault/8725/3. The testsystem was a VM.

overheadhunter · October 29, 2021, 3:42pm

This is not a permanent solution, but it helps us locate the source of the problem

I suspect your system is running out of entropy. To verify this theory: Does installing haveged help (might require reboot)?