Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 177130 - PATH is not transmitted through startkde
PATH is not transmitted through startkde
Status: CLOSED DUPLICATE of bug 177258
Product: Fedora
Classification: Fedora
Component: kdebase (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2006-01-06 10:55 EST by Sammy
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-13 17:40:46 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 Sammy 2006-01-06 10:55:43 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8) Gecko/20060103 Fedora/1.5-4 Firefox/1.5

Description of problem:
I noticed that some applications that I start from the KDE desktop don't have
the full system PATH defined to them. For example, I have graphical editors
that have a window for executing shell commands. If you start the application
from the konsole it has the full PATH.

I put an echo $PATH into startkde and got this:


Whereas my path (say in konsole, coming from bash) is:


If I put this PATH into startkde and export it everyhting works fine. Perhaps
we need to source something in startkde.

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

How reproducible:

Steps to Reproduce:
1. Start an application from the desktop that can execute shell commands (not konsole)

Additional info:
Comment 1 Sammy 2006-01-09 12:08:49 EST
This seems to be related to the new bash. startkde is not considered a login
shell and therefor initilization files are not sourced. The following change
fixes the problem:

#!/bin/sh ------> #!/bin/bash -l

Comment 2 Sammy 2006-01-10 10:24:18 EST
Please see:


Something has changed in the kde/kdm startup to cause this but I could
not find it.
Comment 3 Ray Strode [halfline] 2006-01-13 17:40:46 EST

*** This bug has been marked as a duplicate of 177258 ***
Comment 4 Tim Waugh 2006-01-17 04:51:10 EST
Please try with bash-3.1-5.

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