Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 21121 - startkde doesn't process all shutdown script directories
Summary: startkde doesn't process all shutdown script directories
Status: VERIFIED LATER
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High critical (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-16 14:49 UTC by D Wollmann
Modified: 2003-11-10 07:40 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description D Wollmann 2003-05-16 14:49:46 UTC
KDE 3.1.1a

The startkde script (/usr/kde/3.1/bin/startkde) is supposed to process "shutdown
scripts" after KDE exit, but improperly parses the list of 'exe' paths returned
from kde-config, so only the first path in the list is processed as expected
(usually ~/.kde/shutdown/).

startkde includes the following code:

# Run scripts found in $KDEDIRS/shutdown
for prefix in `kde-config --path exe| sed -e 's^bin/^shutdown/^g;s^:^ ^'`
do
    # run each script...
done

The second substitution expression passed to sed (s^:^ ^) doesn't include the /g
modifier, so it replaces only the first path separator with the input field
separator, yielding:

/home/user/.kde/shutdown/ /usr/kde/3.1/shutdown/:/usr/shutdown/

Adding the /g modifier so that the argument to sed becomes
's^bin/^shutdown/^g;s^:^ ^g' fixes the problem.

I checked bugs.kde.org to see if this issue was known upstream and found no
mention of it.
Comment 1 Caleb Tennis (RETIRED) gentoo-dev 2003-07-07 13:32:37 UTC
Submitted to kde: 
 
http://bugs.kde.org/show_bug.cgi?id=60896 
Comment 2 Caleb Tennis (RETIRED) gentoo-dev 2003-10-02 08:13:46 UTC
closing this as a LATER - it's been reported ot kde folks...now we just have
to get them to act on it.
Comment 3 Caleb Tennis (RETIRED) gentoo-dev 2003-11-10 07:40:29 UTC
Okay, has been fixed upstream in KDE for 3.2