Bug 630253 - gnome-keyring always ask for password and takes 100% CPU (couldn't allocate secure memory)
Summary: gnome-keyring always ask for password and takes 100% CPU (couldn't allocate s...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-keyring
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 630988 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-04 12:42 UTC by Mildred
Modified: 2015-03-03 22:52 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-08-16 20:46:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mildred 2010-09-04 12:42:48 UTC
Description of problem:

The GNOME keyring always asks for my passwords, sometimes many times in a row. The keyring is not unlocked at startup. After some time, I have multiple (3/4) processes of gnome-keyring-daemon that takes most of the CPU. Killing with SUGTERM doesn't work and I have to SIGKILL.

Version-Release number of selected component (if applicable):

gnome-keyring-pam-2.31.91-1.fc14.x86_64
gnome-keyring-2.31.91-1.fc14.x86_64
gnome-keyring-devel-2.31.91-1.fc14.x86_64

How reproducible: always
Steps to Reproduce: Use an application that asks the GNOME keyring
Actual results: Password is always requested
Expected results: The keyring should be unlocked for the session


Additional info:

The syslog says:

Sep  4 14:22:28 meryl gnome-keyring-daemon[3707]: couldn't connect to control socket at: /tmp/keyring-3h2BuG/control: Connection refused
Sep  4 14:22:33 meryl kernel: DMA-API: debugging out of memory - disabling
Sep  4 14:29:07 meryl gnome-keyring-prompt: Gtk: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory
Sep  4 14:29:08 meryl gnome-keyring-prompt: Bonobo: Bonobo must be initialized before use
Sep  4 14:29:18 meryl gnome-keyring-daemon[3707]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
Sep  4 14:29:19 meryl gnome-keyring-prompt: Gtk: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory
Sep  4 14:29:19 meryl gnome-keyring-prompt: Bonobo: Bonobo must be initialized before use

Comment 1 Matthias Clasen 2010-09-07 23:28:56 UTC
*** Bug 630988 has been marked as a duplicate of this bug. ***

Comment 2 Matthias Clasen 2010-09-07 23:31:15 UTC
Filed upstream: https://bugzilla.gnome.org/show_bug.cgi?id=628984

Comment 3 Fedora End Of Life 2012-08-16 20:46:41 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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