Bug 62188 - the gnome switchdesk config file doesnt start ssh-agent
the gnome switchdesk config file doesnt start ssh-agent
Status: CLOSED CURRENTRELEASE
Product: Red Hat Public Beta
Classification: Retired
Component: switchdesk (Show other bugs)
skipjack-beta1
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Mike A. Harris
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-03-28 03:27 EST by Jef Spaleta
Modified: 2007-04-18 12:41 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-09-25 21:45:12 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 Jef Spaleta 2002-03-28 03:27:43 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020314

Description of problem:
The way the gdm Session scripts are written ssh-agent is not started if the
switchdesk gnome config is in place.

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


How reproducible:
Always

Steps to Reproduce:
1.Choose Gnome session in gdm with the switchdesk packaged installed
2.If switchdesk is not present...the next segment of Xsession logic will call
ssh-agent 

	

Expected Results:  I would expect that that the switchdesk gnome client would
attempt to make a call to ssh-agent gnome-session, 

There are several places inside the Xsession script where the actually
gnome-session command can get called.  In some places gnome-session is started
with ssh-agent...and in other parts of the logic gnome-session is called
directly.  It would be nice if all the defualt logic included a call to ssh-agent.  

Additional info:
Comment 1 Mike A. Harris 2002-10-26 01:02:33 EDT
ssh-agent is started by xinitrc et al in Red Hat Linux 8.0, this should
resolve the problem.

Closing bug as CURRENTRELEASE

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