First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 21121
Alias:
Product:
Component:
Status: CLOSED
Resolution: LATER
Assigned To: Gentoo KDE team <kde@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: D Wollmann <converter42@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 21121 depends on: Show dependency tree
Bug 21121 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.




View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2003-05-16 14:49 0000
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 From Caleb Tennis 2003-07-07 13:32:37 0000 -------
Submitted to kde: 
 
http://bugs.kde.org/show_bug.cgi?id=60896 

------- Comment #2 From Caleb Tennis 2003-10-02 08:13:46 0000 -------
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 From Caleb Tennis 2003-11-10 07:40:29 0000 -------
Okay, has been fixed upstream in KDE for 3.2

First Last Prev Next    No search results available      Search page      Enter new bug