Installer: After update GPGMail was not working anymore
I installed the update 2016.08 of GPG Suite. After doing so the GPGMail component was not working anymore. The message in mail was “Please check your Installation and configuration”. I restarted mail multiple times and also followed the troubleshooting in https://gpgtools.tenderapp.com/kb/gpgmail-faq/what-does-the-status-..., but nothing worked. By coincident i rebooted my notebook after some time and all of the sudden it started to work again.
Expected
For me this is a bug, because the update should have told me, that
a reboot is needed in order to get it to work again.
Mac OS X 10.11.6 (15G31)
Libmacgpg 0.7 769
GPGMail 2.6.1 1151
GPG Keychain 1.3.1 1233
GPGServices 1.11 907
MacGPG2 2.0.30 875
GPGPreferences 2.0 887
Pinentry 0.9.7 2
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Steve on 18 Aug, 2016 12:12 PM
Hey Oliver,
welcome to the GPGTools community support platformand thanks for reporting here. Twitter is far from ideal for good support or bug reports. Sorry you are having problems using GPG Suite.
You are right that a hint to restart your mac would have resolved the problem. But it's not that trivial to identify what exactely caused the problem in the first place. And without having a clear indicator about that, it is really difficult to determine when to show the restart hint.
Are you able to retrieve any related error message from the time you were seeing the issue when you open console.app and search for mail.app or GPGMail or libmacgpg or gpg?
All the best,
steve
2 Posted by oliver on 18 Aug, 2016 12:28 PM
usually i would never use twitter for that, but i was looking for a "normal, standard easy to use and report" bug tracker for quite a while and couldn’t find any. and your “discussion groups” are not a bugtracker nor easy to access.
anyway…
my logs have been rotated already so console is showing nothing at all anymore.
with a grep i could find something like this:
./gpg-home-fixer.log:2016-08-16 16:39:05: [fixGpgHome] started with arguments: oliver /Users/oliver/.gnupg
./gpg-home-fixer.log:d2e82a39aaef128c61a91b1ca08d9931922d3327 /usr/local/MacGPG2/bin/gpg2
./gpg-home-fixer.log:990cae62c6aaf4529c54e28b5c929ade0245f6ee /usr/local/MacGPG2/bin/gpg-agent
./gpg-home-fixer.log:2016-08-16 16:39:05: [fixGpgHome] Fixing '/Users/oliver/.gnupg'...
./gpg-home-fixer.log:gpg: WARNING: unsafe ownership on configuration file `/Users/oliver/.gnupg/gpg.conf'
./gpg-home-fixer.log:2016-08-16 16:39:05: [fixGpgHome] Fixing done
./gpg-home-fixer.log:2016-08-16 16:39:05: [fixGpgHome] fixGPGAgent started
./gpg-home-fixer.log:2016-08-16 16:39:05: [fixGpgHome] Fixing '/Users/oliver/.gnupg/gpg-agent.conf'...
./gpg-home-fixer.log:2016-08-16 16:39:05: [fixGpgHome] Start gpg-agent.
./gpg-home-fixer.log:2016-08-16 16:39:05: [fixGpgHome] UID = 0
./gpg-home-fixer.log:2016-08-16 16:39:05: [fixGpgHome] Start gpg-agent using uid: 'oliver'
./gpg-home-fixer.log:GPG_AGENT_INFO=/Users/oliver/.gnupg/S.gpg-agent:13704:1; export GPG_AGENT_INFO;
./gpg-home-fixer.log:2016-08-16 16:39:06: [fixGpgHome] fixGPGAgent done
./gpg-home-fixer.log:2016-08-16 16:39:06: [fixGpgHome] done
./gpgmail-uuid-patcher.log:[uuid-patcher] Trying to find GPGMail bundle…
Support Staff 3 Posted by Steve on 18 Aug, 2016 01:37 PM
Hey Oliver,
thanks for the follow up.
We don't want bug reports in our bug tracker. It's not where they belong. Once a problem has been isolated, we will create bugs or feature requests accordingly.
The support platform is linked in the top menu on our homepage: https://gpgtools.org/ as well as on the twitter discription: https://twitter.com/GPGTools. We are not trying to hide that important information.
We have a ticket for this problem. I connected this discussion with the existing ticket. That means, should this discussion get closed, it will be re-opened as soon as the ticket is closed. That way you'll stay in the loop and get notified as soon as we have news. Feel free to open a new discussions should you run into further problems or need assistance.
Kindly,
steve
Steve closed this discussion on 20 Apr, 2017 02:25 PM.