There is NO WARRANTY, to the extent permitted by law.Note: Use "gpg --full-gen-key" for a full featured key generation dialog.So, let's go to diagnostics about the current problem: $ grep -v ^# .gnupg/| grep -v ^$ default-key 62EB2A51keyserver hkp://net photo-viewer "display -title 'Key ID 0x%k'" $ grep -v ^# .gnupg/| grep -v ^$ default-cache-ttl 0 max-cache-ttl 0 $ which gpg /usr/bin/gpg $ which gpg2 $ dpkg -S $(which gpg) gnupg: /usr/bin/gpg $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.10 DISTRIB_CODENAME=yakkety DISTRIB_DESCRIPTION="Ubuntu 16.10"When I try to run gpg, the following happens, regardless of whether or not I move my .gnupg away or not.I killed the gpg-agent before moving the .gnupg, didn't change anything.6d859a5 Get compile error for failing test 8bf760a now try mono 95578de fix maven warning f804d12 need PR #993 to run on TRAVIS-CI cbd3fad fix maven warnings e255480 added myself as contributor 55fce54 reverted fix 68cdaea now trying mono! So dropped my version, which also required some fix for Safari, in favor of this one that I don't have to maintain 0c29b54 Update generated test source 09588d2 Update templates for other languages similarly af00e52 Correctly append newline to test output 797cf08 Delete remaining commented out syncs.940cbcf Uncomment syncs before adaptive Predict 6c0b7d9 Improve compatibility across contexts: nodejs, web ui and web worker e7cdc22 Largely rewritten to support usage in web worker thread without breaking compatibility with Node JS require a80052f Fixed a bug when locating Java Script runtime, and refactored common code b65d521 Fix test generator to support browser tests generation when generating all tests ebf8b9a Fix templates which were referring to a missing class bf00f6b Switch to selenium v46 ee3d29c Fixes an issue pointed out by Mike Cargal, where null literals where registered as 'null' instead of null in both lexical Names and symbolic Names, thus resulting in erroneous error messages when handling parsing errors.The filepath indicated in the log is therefore wrong (? With a fresh user account, synchronisation works flawlessly for the first couple of files, then the problem kicks in rather arbitrarily. The issue seems to arise more frequently, if the user has many files - c.f. To try to relieve some of the pressure, I unchecked everything that it syncs with, and am slowly introducing the files back into the system. I believe I have successfully synced 60mb in 3 hours. I'm leaving my post intact in case others are having my problem. It seems I upgraded nginx but forgot to restart the service.