Bug 89153 - /etc/skel/.kde never copied from startkde
Summary: /etc/skel/.kde never copied from startkde
Keywords:
Status: CLOSED DUPLICATE of bug 67583
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdebase
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-04-18 16:15 UTC by Derrien
Modified: 2007-04-18 16:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:52:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Derrien 2003-04-18 16:15:59 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920
Netscape/7.0

Description of problem:
At the beginning of startkde we have :

[ -d "$HOME"/.kde/share/config ] || mkdir -p "$HOME"/.kde/share/config

so the following test :

if [ ! -d "$HOME"/.kde -a -d /etc/skel/.kde ]; then
  ( cd /etc/skel && tar cpf - .kde ) | ( cd "$HOME" && tar xpf - )
fi

is always false and /etc/skel/.kde is never copied in the user HOME...



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


How reproducible:
Always

Steps to Reproduce:
1.execute startkde
2.
3.
    

Actual Results:  /etc/skel/.kde is not copied in $HOME/.kde

Expected Results:  /etc/skel/.kde is copied in $HOME/.kde

Additional info:

Comment 1 Dave Shield 2003-07-30 14:50:52 UTC
This bug has been present since RedHat 7.3 (see bug reports #52502 & #67583)

It could be fixed very simply by moving the "test || mkdir" line to come
after the "tar /etc/.skel" block.

It was reported to me that this had been done almost two years ago,
so it's somewhat disappointing that this bug is still present.

Comment 2 Marcin Garski 2004-11-05 15:46:25 UTC
This bug is fixed in the current FC release.

*** This bug has been marked as a duplicate of 67583 ***

Comment 3 Red Hat Bugzilla 2006-02-21 18:52:44 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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