Bug 455398 - Requester asking for keyring password
Requester asking for keyring password
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-15 07:56 EDT by Daniel Malmgren
Modified: 2008-07-15 08:55 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-15 08:55:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Daniel Malmgren 2008-07-15 07:56:54 EDT
Description of problem:
The first time I start evolution in a session (when evolution-alarm-notify isn't
already started) I get a requester asking me for the password to my default keyring.

Version-Release number of selected component (if applicable):
evolution-2.22.3.1-1.fc9.x86_64
gnome-keyring-2.22.3-1.fc9.x86_64

Additional info:
The requester says:
Enter password for default keyring to unlock
The application "evolution-alarm-notify"
(/usr/libexec/evolution/2.22/evolution-alarm-notify) wants
access to the default keyring but it is locked.

However, disabling the connection to my Google calendar fixes this. I want to
see my Google calendar though...

In the keyring handler there is an item for the password to my Google calender,
and under programs for that item evolution-alarm-notify is in the list (with
correct path). I don't know what more to check...
Comment 1 Matthew Barnes 2008-07-15 08:55:21 EDT
That's normal behavior.  Your keyring is guarded by a master password and must
be unlocked the first time an application wants access to it.  Your keyring
password is what unlocks the keyring for the application.

Note You need to log in before you can comment on or make changes to this bug.