Home → Stable →

GPG Keychain Acces error in one of two accounts - MacBook Pro 10.6.8

• Edit

Miguel

21 Aug, 2013 01:10 PM

GPG Keychain Access 1.1.2
10.6.8

Please describe your problem. Add as much detail as possible.

Can't start GPG Keychainaccess - GPG Config Error in one account, in another account same machine, same previleges works perfectly

• 20130821.png 25.5 KB

1. Support Staff 1 Posted by Luke Le on 21 Aug, 2013 08:49 PM

   

   Hi Miguel,

   while it should not be necessary, installing the GPG Suite on this account as well will fix the problem.

   A future release will fix this for good.

   • Edit

2. 2 Posted by Miguel on 22 Aug, 2013 11:02 AM

   

   Luke, thanks a lot for the fast answer but I'm afraid it didn't solved my problem.
   I now installed GPG Suite on both accounts and even created a third account just to try, the result was GPG runs fine on two of the accounts but not one the one I actually use the most.
   The error message is still the same.
   If you have any further tips how I can solve this I'll appreciate

   • GPG_Error_20130822.png 25.5 KB
   • Edit

3. Support Staff 3 Posted by Luke Le on 24 Aug, 2013 09:06 PM

   

   Hi Miguel,

   could you please open the Terminal (easiest to find via Spotlight) and type the following two lines, press enter after each:

   cat ~/.gnupg/gpg.conf
   cat ~/.gnupg/gpg-agent.conf
   

   Please post the output here.

   • Edit

4. 4 Posted by Miguel on 25 Aug, 2013 02:56 PM

   

   lounge:~ mrmwaduma$ cat ~/.gnupg/gpg.conf
   cat: /Users/mrmwaduma/.gnupg/gpg.conf: No such file or directory
   lounge:~ mrmwaduma$ cat ~/.gnupg/gpg-agent.conf
   cat: /Users/mrmwaduma/.gnupg/gpg-agent.conf: No such file or directory
   lounge:~ mrmwaduma$

   • Edit

5. Support Staff 5 Posted by Luke Le on 12 Sep, 2013 01:46 PM

   

   Hi Miguel,

   ouch, this looks like permission problems.
   Could you please open Terminal (easiest to find via Spotlight) and type the following two lines, press enter after each:

   ls -led@ ~
   gpg --version
   

   Thanks.

   • Edit

6. 6 Posted by Miguel on 12 Sep, 2013 02:23 PM

   

   Hey Luke,
   still stucked, meanwhile I repaired permissions several times and reinstalled GpgTools from the root user, nothing changed though…

   lounge:~ mrmwaduma$ ls -led@ ~
   drwx------+ 25 mrmwaduma wheel 850 17 Jan 2013 /Users/mrmwaduma
    0: group:everyone deny delete
   lounge:~ mrmwaduma$

   lounge:~ mrmwaduma$ gpg --version
   gpg (GnuPG/MacGPG2) 2.0.20
   libgcrypt 1.5.3
   Copyright (C) 2013 Free Software Foundation, Inc.
   License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
   This is free software: you are free to change and redistribute it.
   There is NO WARRANTY, to the extent permitted by law.

   Home: ~/.gnupg
   Supported algorithms:
   Pubkey: RSA, ELG, DSA
   Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
           CAMELLIA128, CAMELLIA192, CAMELLIA256
   Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
   Compression: Uncompressed, ZIP, ZLIB, BZIP2
   lounge:~ mrmwaduma$

   • Edit

7. Support Staff 7 Posted by Luke Le on 12 Sep, 2013 03:46 PM

   

   Hi Miguel,

   these permissions are not good.
   Did you ever change them manually or did you use the Migration Assistant of Apple?

   To fix them please run the following command:

   sudo chmod -v 755 /Users/mrmwaduma
   

   and reboot.
   After that, please try install the GPG Suite again.

   • Edit

8. Support Staff 8 Posted by Luke Le on 12 Sep, 2013 04:22 PM

   

   Hi Miguel,

   I just found out that this problem might be a different OS X bug.
   Somehow under some circumstances (TimeMachine restore, Migration Assistant, or similar) the home folder is flagged as write protected.

   To fix that, please run the following command:

   chflags nouchg ~
   

   • Edit

9. Support Staff 9 Posted by Steve on 13 Oct, 2013 12:12 PM

   

   No further user feedback. Closing.

   Miguel, did Luke's suggestion work for you? If not, feel free to re-open this discussion any time.

   All the best, steve

   • Edit

10. Steve closed this discussion on 13 Oct, 2013 12:12 PM.

11. Alegria re-opened this discussion on 14 Oct, 2013 10:25 AM

12. 10 Posted by Alegria on 14 Oct, 2013 10:25 AM

    

    Steve, hello,

    I thought I had already replied… Luke's suggestion worked just fine, all running now, thanks a lot,

    Miguel

    A 2013/10/13, às 13:12, Steve escreveu:

    • Edit

13. Support Staff 11 Posted by Steve on 25 Oct, 2013 07:31 PM

    

    Miguel, hm, your reply didn't make it here. But that's good news. Glad, this is solved for you. I'm closing this discussion. If you need further assistance or have questions you can re-open this discussion here or open a new one any time.

    Best, steve

    • Edit

14. Steve closed this discussion on 25 Oct, 2013 07:31 PM.

15. Mento re-opened this discussion on 04 Nov, 2013 12:45 PM

16. 12 Posted by Mento on 04 Nov, 2013 12:45 PM

    

    Hi Miguel,

    we were unable to reproduce the problem. But we attempted to fix the problem.

    Could you please download and install our latest nightly build and see if the problem persists.

    All the best, steve

    Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected. Thanks for helping us test this fix.

    • Edit

17. Steve closed this discussion on 06 Nov, 2013 11:24 AM.