Bug 170324 - Selecting a script already existing in .kde/Autostart leads to a loop
Summary: Selecting a script already existing in .kde/Autostart leads to a loop
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_autostart (show other bugs)
Version: 4.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-03 16:47 UTC by Dominik Tritscher
Modified: 2009-02-09 22:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Patch for bugs 170324 and 171136 (2.06 KB, patch)
2008-10-11 13:25 UTC, Thomas Fischer 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Tritscher 2008-09-03 16:47:15 UTC 
Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Ubuntu Packages

I tried to add a shell script already existing in .kde/Autostart, which leads to a loop, if I choose to overwrite existing file.
Steps to reproduce:
1. Go to systemsettings > Advanced > Autostart
2. Choose "Add Script"
3. Select a .sh-file in .kde/Autostart/
4. deselect "add as shortcut"
5. hit "Ok"
6. You get the regular kde copy dialog that appears one name conflicts, asking whether you would like to overwrite or rename.
7. Select "Overwrite" and the same dialog appears again.
This loop can be left by choosing "Cancel" or "Rename".
Expect behaviour: Don't copy scripts that already exists that already exists in Autostart folder.
Comment 1 Thomas Fischer 2008-10-11 13:25:18 UTC 
Created attachment 27812 [details]
Patch for bugs 170324 and 171136

I wrote a small patch that checks the given script file if it is (a) executable (bug 171136) and (b) if the file is not already in the Autostart folder (bug 170324).
Additionally, this patch fixes a sizing issue with the combobox when adding an new script.
Comment 2 Dominik Tritscher 2009-02-09 22:44:33 UTC 
Just checked this with KDE4.2 and this seems to be fixed now. At least it works for me.