Bug 62130 - KDM doesn't execute ~/.Xclients when "default" is chosen
KDM doesn't execute ~/.Xclients when "default" is chosen
Product: Red Hat Linux
Classification: Retired
Component: kdebase (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: wdovlrrw
Ben Levenson
Depends On:
Blocks: 61590
  Show dependency treegraph
Reported: 2002-03-27 14:47 EST by Preston Brown
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:
Last Closed: 2002-03-28 16:36:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Preston Brown 2002-03-27 14:47:13 EST
Description of Problem: 
When using KDM, you have the option of choosing a "default", KDE, GNOME, or failsafe login. 
Default should execute the contents of ~/.Xclients.  It does not appear to be happening 
however, instead it seems to be calling startkde directly.  Under KDE 2.x on RHL 7.2, 
having a ~/.Xclients of: 
ssh-agent startkde 
successfully worked (i.e. startkde was executed as a child of the ssh agent password cache) 
but no ssh-agent is running after my upgrade to Skipjack after login.
Comment 1 Bernhard Rosenkraenzer 2002-04-02 08:04:46 EST
Fixed in 3.0.0-1

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