Red Hat Bugzilla – Bug 58983
startkde makes wrong assumptions about the shell environment
Last modified: 2007-04-18 12:39:22 EDT
startkde assumes that df produces output in standard form (i.e. $BLOCK_SIZE or
$DF_BLOCK_SIZE isn't set to human-readable or si) and that the noclobber shell
option isn't set
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. arrange for "export BLOCK_SIZE=human-readable" and "set -o noclobber"
to be in a start-up file that is processed when the startkde script is
loaded (~/.bashrc will probably work, I don't really understand how bash
decides to load these files)
2. run startkde
The script dies because $space_tmp and $space_home aren't purely numbers
(they have letters like "M" or "G" in them).
If you fix that, the script dies because
"testfile_tmp=`mktemp /tmp/KDE.startkde.XXXXXX`; echo TEXT_TEXT >
$testfile_tmp" doesn't work with noclobber set.
Expected Results: Everything Just Works (TM).
It's bad idea to use noclobber, many scripts may/will fail if you
set this variable. Nonetheless I've added a workaround to startkde.