Gpgtools MacGPG2 → 2.0.30_2016.07

Comments and changes to this ticket

• 

  steve February 4th, 2015 @ 11:38 PM

  • no changes were found...

  • MacGPG2_crash.txt 11.3 KB
• 

  Support February 4th, 2015 @ 11:39 PM

  Assigned to Tender discussion #726.

• 

  Luke Le July 5th, 2015 @ 01:28 AM

  Might be related to Libmacgpg #147

• 

  Support July 8th, 2015 @ 12:35 PM

  • Tag set to “”

  Assigned to Tender discussion #1549.

• 

  Support August 20th, 2015 @ 08:02 PM

  • Tag set to “”

  Assigned to Tender discussion #44933.

• 

  Support September 14th, 2015 @ 10:45 AM

  • Tag cleared.

  Assigned to Tender discussion #45646.

• 

  steve October 2nd, 2015 @ 11:57 PM

  Persisting

  Mac OS X 10.11 (15A284)
  Libmacgpg 0.6.1 753n (f27b8ad)
  GPGMail 2.6b2 1105b
  GPG Keychain 1.2.1 1147
  GPGServices 1.10.1 871
  MacGPG2 2.0.29 859n (6b5a3c9)
  GPGPreferences 1.5 846

  GPGMail had just decrypted and verified (successfully) an incoming mail. Nonetheless at the top of the mail was "Unbekannter Fehler beim Entschlüsseln" with the following details:

  Unbekannter Fehler beim Entschlüsseln.
  
  Beim Entschlüsseln der Nachricht ist ein unbekannter Fehler aufgetreten.
  
  GPG Fehlermeldung:
  gpg: [fd 5]: read error: Device not configured
  
  Bitte kontaktieren Sie uns mit der GPG Fehlermeldung unter https://gpgtools.tenderapp.com/
  

  As observed presiously it seems no functionality is harmed and the OpenPGP indicator in Mail > Preferences > GPGMail remains green. Yet the error message might be irritating to users and since the crash shows in console rather frequently, we should have a look into details soon.

• 

  steve October 3rd, 2015 @ 12:01 AM

  • no changes were found...

  • 10.11_crash_log 11.7 KB
• 

  steve October 3rd, 2015 @ 12:03 AM

  Looks related. Happened 6 seconds before the crash:

  02.10.15 22:13:29,027 Mail[7706]: Failed to open emlx and partial.emlx files (/Users/username/Library/Mail/V3/IMAP-xxxxx@gpgtools.org@xxxxxx.xxxxxxxxxxxx.de/xxxxxxxxxx.mbox/xxxxxxxxxxxx.mbox/de.mbox/xxxxxxxxxxxxxx.mbox/xxxxxxxx-xxxx-xxxx-xxxx-0AD062C4CC45/Data/2/1/5/Messages/512962.partial.emlx)
  02.10.15 22:13:29,000 kernel[0]: gpg2: guarded fd exception: fd 5 code 0x1 guard 0x7fff884d82a8

  And more crash info from 02.10.15 22:13:35

  Process: gpg2 [44413]
  Path: /usr/local/MacGPG2/bin/gpg2
  Identifier: gpg2
  Parent Process: org.gpgtools.Libmacgpg.xpc [23814]
  Responsible: org.gpgtools.Libmacgpg.xpc [23814]
  1 gpg2 0x00000001000692da file_filter + 603
  2 gpg2 0x0000000100068a21 iobuf_close + 263
  3 gpg2 0x000000010003d498 decrypt_message + 281
  4 gpg2 0x00000001000096e4 main + 24038
  5 gpg2 0x00000001000037bc start + 52
  0x100000000 - 0x10009ffff +gpg2 (???) <59405BD1-FA77-3240-A8B3-5055A65052EE> /usr/local/MacGPG2/bin/gpg2 0x1000ba000 - 0x1000cbff7 +libz.1.2.8.dylib (1.2.8) /usr/local/MacGPG2/lib/libz.1.2.8.dylib 0x1000cf000 - 0x1000d9fff +libintl.8.dylib (10.2) /usr/local/MacGPG2/lib/libintl.8.dylib 0x1000de000 - 0x100163ff7 +libgcrypt.20.dylib (21.4) <8F3A1A5B-0D49-369D-8CF2-93088DAE1C82> /usr/local/MacGPG2/lib/libgcrypt.20.dylib 0x10017a000 - 0x100188ff7 +libgpg-error.0.dylib (17) /usr/local/MacGPG2/lib/libgpg-error.0.dylib 0x10018e000 - 0x10019afff +libassuan.0.dylib (7) /usr/local/MacGPG2/lib/libassuan.0.dylib 0x1001a0000 - 0x100299ff7 +libiconv.2.dylib (8.1) /usr/local/MacGPG2/lib/libiconv.2.dylib

• 

  steve October 9th, 2015 @ 12:18 PM

  another gpg2 crash with same proceedure. first the info about an emlx file (partial) and 5 or 6 seconds later the gpg2 crash.

  • gpg2_crash_2015-10-08 12.1 KB
  • gpg2_crash_2015-10-08.jpg 27.8 KB
• 

  Support October 30th, 2015 @ 06:10 PM

  • Tag set to “”

  Assigned to Tender discussion #47037.

• 

  Support November 13th, 2015 @ 12:49 PM

  • Tag cleared.

  Assigned to Tender discussion #47402.

• 

  steve December 18th, 2015 @ 02:42 PM

  • Title changed from “EXC_GUARD crash” to “EXC_GUARD crashssl”
• 

  steve December 18th, 2015 @ 02:45 PM

  • State changed from “new” to “fixed”
  • Assigned user set to “Mento”
  • Milestone set to “2.0.30_2016.07”

  Potentially fixed. Waiting for user feedback.

  Idea for fix was: start no parallel verifications, but one after the other.

• 

  steve January 8th, 2016 @ 06:16 PM

  • State changed from “fixed” to “verified”

  So far no further crashes on my own system (which reliably produced the crashes in question every other day) and also not on user systems, which where affected by this problem.

  Setting to verified.

• 

  Support January 9th, 2016 @ 03:54 PM

  • Tag set to “”

  Assigned to Tender discussion #1149.

• 

  Support December 1st, 2016 @ 05:15 PM

  • Tag changed from “” to “#tag id: 460388, name:”

  Assigned to Tender discussion #50028.

• 

  steve May 18th, 2017 @ 07:08 PM

  • Tag cleared.