---- Reported by jim@yorba.org 2013-06-25 11:02:00 -0700 ----

Original Redmine bug id: 7157
Original URL: http://redmine.yorba.org/issues/7157
Searchable id: yorba-bug-7157
Original author: Jim Nelson
Original description:

Lately I've been seeing runs where Geary prompts me for my IMAP password when
it first executes. This is in the log:

    
    
     [deb] 10:55:21 secret-mediator.vala:37: Unable to fetch password in libsecret keyring for user: jimbonator@gmail.com
    

When I enter my password and press Enter, Geary exits. This is in the log:

    
    
    [msg] 10:55:26 Remote error from secret service: org.freedesktop.DBus.Error.InvalidArgs: The secret was transferred or encrypted in an invalid way.
    [deb] 10:55:26 geary-controller.vala:577: Unable to open account Gmail account jimbonator@gmail.com: The secret was transferred or encrypted in an invalid way.
    

In the past we saw situations where gnome-keyring would not return the
passwords (or return an error, I forget which) on random runs (#4253). They
seemed to go away, and then later we switched to libsecret. I suspect this
problem is similar in nature to the gnome-keyring problem of yore.

Related issues:
related to geary - 4253: Geary occasionally "forgets" password (Open)



---- Additional Comments From geary-maint@gnome.bugs 2013-07-11 15:32:00 -0700 ----

### History

####

#1

Updated by Avi Levy 5 months ago

I've been seeing this for at least the past week, maybe longer - but it only
happens when restarting Geary frequently (for instance, while working on a
patch). Since it didn't turn up during normal usage of Geary, I refrained from
filing a bug.

####

#2

Updated by Jim Nelson 4 months ago

  * **Target version** changed from _0.4.0_ to _0.5.0_



--- Bug imported by chaz@yorba.org 2013-11-21 20:19 UTC  ---

This bug was previously known as _bug_ 7157 at http://redmine.yorba.org/show_bug.cgi?id=7157

Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution