Bug 5670 - keychain/ssh-agent doesn't auto-run at login: /etc/profile.d/99keychain.sh isn't invoked
Summary: keychain/ssh-agent doesn't auto-run at login: /etc/profile.d/99keychain.sh is...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-29 03:45 CEST by Richard Neill
Modified: 2014-05-04 11:04 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Richard Neill 2012-04-29 03:45:18 CEST
It used to be that simply installing keychain was all that was needed: as soon as the user logged in at kdm/gdm, there would be a prompt for the SSH passphrase.

This doesn't happen any more. As far as I can tell, the file:
  /etc/profile.d/99keychain.sh
is no longer invoked by the X login process.

Manually sourcing /etc/profile.d/99keychain.sh will work. 


I'm not sure I fully understand the interaction of /etc/bashrc,  xsession, and /etc/profile.d/*.sh   (and ~/.bash_profile, ~/.bashrc)
Comment 1 Marja Van Waes 2012-05-26 13:06:38 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 2 Richard Neill 2012-05-26 21:37:23 CEST
I think so...but I'm afraid I can't track this one down properly without re-doing a clean install. The keychain maintainer would know in a few seconds.
roelof Wobben 2013-01-04 10:21:29 CET

CC: (none) => ennael1, r.wobben

Comment 3 roelof Wobben 2013-01-04 10:21:58 CET
@anne : Could you shine a light on this matter. 

Roelof
Comment 4 Marja Van Waes 2014-05-04 11:04:40 CEST
No one reported this since pre-Mageia 2 cauldron, so closing as old.

In current cauldron, after logging in I do get prompted for the passphrase when a konsole/terminal gets auto-started (so when I left one open before shutting down, or when I log in in runlevel 3), but not when no konsole/terminal is started.

That's exactly how I want it to be :-)

Keywords: NEEDINFO => (none)
Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD


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