Home → Stable →

10.8.4: GPGServices freezes window if service fails

• Edit

lonestarm3

17 Aug, 2013 11:45 AM

Which of our tools is giving you problems?

GPGServices, 1.9 Build 505

What version of OS X are you using?

10.8.4

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

If service (example verify) fails and Verification Results window is closed without "cancelling" first, the GPGServices progress popup window cannot be closed without rebooting the computer. The close "x" at end of progress bar has no effect.

Please describe what you did expect instead

Expected closing GPGServices window to close both. That is the way other similar apps normally function

If you remember, please describe the steps leading up to the problem

1. Right click target file
   
2. Select service
   
3. After service fails, close window without canceling first

I am not sure if this is a bug or not, but if not modifying the action to force closing results window when services window is closed would be a suggested change.
It is very easy to accidentally fail (forget) to cancel before closing and while it does not do any "damage" it is a considerable inconvenience to have to reboot and then redo the work that preceded the event.

Thanks

1. Support Staff 1 Posted by Steve on 17 Aug, 2013 03:54 PM

   

   Hi lonestar3,

   what actions do cause GPGServices to fail? Seems to be reproducible for you.

   • Edit

2. 2 Posted by lonestarm3 on 17 Aug, 2013 04:25 PM

   

   Actions which "fail" followed by closing the results window without clicking "OK" button. May be my fault for reflexively (too quick?) clicking the close button at upper left of window instead.

   I have several time used verify and the target file encrypted but not signed. The result window reports failure and if window closed by the close button upper left on pane, then the progress window is non responsive - even if Access reopened. Repeating adds a second progress bar, but the first one still unresponsive. If user clicks "Ok" as he should, no problem.
    
   Would be nice if an error recovery option or algorithm would trap error without having to reboot machine to get rid of it.
   (Would also help if dumb user like me would remember every time to do it right in the first place:-)

   • gpg.jpeg 17 KB
   • Edit

3. Support Staff 3 Posted by Steve on 22 Aug, 2013 11:15 AM

   

   Hi Lonestarm3,

   I can confirm this problem. Never clicked on that red dot until now. This is very broken behavior and we've now a ticket for this problem:

   https://gpgtools.lighthouseapp.com/projects/67607-gpgservices/ticke...

   I'm closing this discussion. It will be re-opened as soon as the ticket is closed so you'll receive a notification. Feel free to open a new discussions should you run into further problems or need assistance.

   • Edit

4. Steve closed this discussion on 22 Aug, 2013 11:15 AM.

5. Support Staff 4 Posted by Steve on 04 Nov, 2013 09:56 PM

   

   Hi Lonestarm3,

   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

6. Steve closed this discussion on 04 Nov, 2013 09:56 PM.

7. lonestarm3 re-opened this discussion on 05 Nov, 2013 12:12 AM

8. 5 Posted by lonestarm3 on 05 Nov, 2013 12:12 AM

   

   Steve,
   Think this was sent to me in error. The problem described was way back in October and was corrected then.
   The only problem I have had recently was that after upgrading to 10.9 "Mavricks" I could encrypt a file but not decrypt.
   I downloaded and reinstalled latest version of GpgTools suite and so far have had no more problems.
   Thanks,
   Jerry

   On Nov 4, 2013, at 15:56, "Steve" <[email blocked]> wrote:

   • Edit

9. Support Staff 6 Posted by Steve on 05 Nov, 2013 11:57 PM

   

   Hey Jerry,

   not really in error. The problem we discovered back then was: https://gpgtools.lighthouseapp.com/projects/67607/tickets/166

   And that has been fixed just now. But I'm glad things are currently running smooth with the latest stable release.

   All the best :)
   steve

   • Edit

10. Steve closed this discussion on 05 Nov, 2013 11:57 PM.