Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 67583

Summary:	startkde and /etc/skel/.kde problem
Product:	[Retired] Red Hat Linux	Reporter:	aleahy
Component:	kdebase	Assignee:	Than Ngo <than>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	derrien, mgarski
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-11-05 15:44:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description aleahy 2002-06-27 19:35:48 UTC

Description of Problem:   There's a bug in /usr/bin/startkde.  On line 44, it
performs:

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

which makes sure $HOME/.kde exists.  Then down on line 56 it performs the test:

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

Given what happened on line 44, there's no way to pass this test.  So the
contents of /etc/skel/.kde will never get copied to the user's directory.




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


How Reproducible:




Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Marcin Garski 2004-11-04 22:04:53 UTC

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

in Fedora Core, so IMHO this bug should be closed, but I'll leave it
for Ngo Than, because maybe there is some "hidden" bug in this report ;)

Comment 2 Than Ngo 2004-11-05 15:44:05 UTC

it's already fixed in the current FC release.

Comment 3 Marcin Garski 2004-11-05 15:46:38 UTC

*** Bug 89153 has been marked as a duplicate of this bug. ***