Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 455398 - Requester asking for keyring password
Summary: Requester asking for keyring password
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-07-15 11:56 UTC by Daniel Malmgren
Modified: 2008-07-15 12:55 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-07-15 12:55:21 UTC

Attachments (Terms of Use)

Description Daniel Malmgren 2008-07-15 11:56:54 UTC
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):

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 12:55:21 UTC
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.