Running insync on mounted Truecrypt device volume in Freya

Bugs and issues
#1

Help needed trying to have insync point to a mounted truecrypt volume in elementary OS Freya.

Use truecrypt to create and mount a 107 GB Device Volume called: “/media/truecrypt1/Google Drive/”

Then, run insync, sign in to google using two step verification, and give insync all requested permissions.

Then, try to browse via insync to mounted volume “/media/truecrypt1/Google Drive/” but it does not show up as a possible directory to sync to.

All help appreciated!

#2

Hi there, will be tagging our engineer @lpugoy and he will be get back to you :smile:

#3

Thanks!

Also have other issues regarding two step verification and long file names.

With respect to two step, after logging out of desktop, insync starts but cannot sign into google account, which has two step verification turned on. It displays a message that it is signing on but nothing happens. The work around is to un-install and re-install insync.

With respect to long file names, insync reports that certain files cannot be synced as the paths are too long.

All help appreciated!

#4

Hi there, what OS are you on?

As for your first issue, I will tag our engineer @marte in this and he will get back to you :smile:

#5

Using elementary OS, Freya, Ubuntu based OS.

#7

@Jackal: Apologies for not replying sooner. For the long file names, there is a current limitation with encrypted file systems where the maximum filename is limited to only 143 characters. Please see here (https://bugs.launchpad.net/ecryptfs/+bug/344878) for details. Unfortunately since this is a limitation of the underlying file system we have no control over it.

For the truecrypt volume, the user that Insync is running as might not have enough permissions to access it. Please confirm.

For the two step verification, please send your logs to support@insynchq.com for investigation: How to find the log files.