Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 601339

Summary: kde should start gnome-keyring
Product: Red Hat Enterprise Linux 5 Reporter: ritz <rkhadgar>
Component: kdebaseAssignee: Than Ngo <than>
Status: CLOSED NOTABUG QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.5   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 749994 (view as bug list) Environment:
Last Closed: 2011-10-17 08:34:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch none

Description ritz 2010-06-07 17:58:04 UTC 
Description of problem:
When running KDE, NetworkManager does not save wireless keys.

steps to re-produce:
  1. Connect to wireless network
  2. Enter wireless key when prompted (via NetworkManager)
  3. Access internet
  4. Rebootthe system and re-login
  5. NetworkManager auto-connects to wireless networkand prompts again for wireless key

Actual result:
"$ ps aux|grep keyring" does not list keyring process. 

Expected result
gnome-keyring should run.

Additional Information:
  gnome-keyring does not start with kde. This would need to be started via /etc/kde/env, as gnome-keyring requires GNOME_KEYRING_SOCKET variable to set. This is required, as gnome-keyring 0.6 does not use dbus.
Comment 1 ritz 2010-06-07 18:02:41 UTC 
Created attachment 421905 [details]
patch
Comment 2 RHEL Program Management 2011-05-31 14:42:36 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.