Menu

#347 convenient encryption status not accurately reflected in icons or menu options

fixed
nobody
None
1.7.2
Minor
All
1.8.2
nobody
2016-01-02
2014-10-10
No

See discussion starting here:

http://thread.gmane.org/gmane.comp.mozilla.enigmail.general/18884

On 09.07.14 00:10, i wrote:

i am seeing the following misbehavior with the 1.7 beta i packaged
from yesterday (i have "convenient encryption" set as the
default):

When i reply to a message from someone for whom i have a key, more
often than not, the default leaves the message unencrypted.

When i send a new message to that person, or when i shift-tab up to
the address bar and then tab back down to the subject entry box,
the message becomes encrypted again.


Patrick Brunschwig responded:

I can reproduce this. It is "just" a display problem. The logic works
correctly when sending the message, but the menu and the icons in the
lower right corner are incorrect.


(dkg again):
I can confirm that this is still an issue in 1.7.2.

Discussion

  • Harlan Stenn

    Harlan Stenn - 2014-11-03

    If I'm reading my "top" message which happens to be unencrypted and an encrypted message arrives, I'm prompted for my GPG passphrase. When I enter this, I get a "top line" on the message saying Enigmail has decrypted this current unencrypted message and also a lock icon to the right of the Subject: of the current unencrypted message (to the left of the date) identifying this message as having an encryption status. If I click on the lock icon I get a popup saying: "Enigmail Security Info, Decrypted message, [OK]"

    Is this the same problem?

    Oh, I'm running 1.7.2.

     

    Last edit: Harlan Stenn 2014-11-03
  • Ludwig Hügelschäfer

    No, you're seeing the behaviour of bug 284

     
  • Patrick Brunschwig

    As far as I can tell, this bug should be fixed on master. Could you please retest?

     
  • Patrick Brunschwig

    • status: open --> fixed
    • Fixed in version: --- --> 1.8.2
     
  • Patrick Brunschwig

    No feedback anymore. I think that this was fixed in v1.8.x

     

Log in to post a comment.