Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I usually just put symlinks in the autostart directory, and that works fine. Just make sure that the file being linked to is executable, and all should be good.
Code:
jim@musicbox:~$ ls -al .kde/Autostart/
total 4
drwx------ 2 jim jim 136 2005-09-30 22:36 .
drwx------ 4 jim jim 200 2005-09-29 00:48 ..
-rw-r--r-- 1 jim jim 1605 2005-09-29 00:48 .directory
lrwxrwxrwx 1 jim jim 16 2005-09-30 22:36 konsole -> /usr/bin/konsole
lrwxrwxrwx 1 jim jim 21 2005-09-30 01:20 xscreensaver -> /usr/bin/xscreensave
Could be any type of problem. Here are the 2 that I think are the most likely.
1) Is it executable? Most things in /usr/bin are, but if you put this there yourself, it may just have read, or read/write permissions. you can find out with
Code:
ls -al /usr/bin/(scriptname)
I won't go into how to interpret the info you get back in detail, but doing searches on permissions can help you. If you want this to be run, then most likely each possibile user (owner, group, and others) should have the ability to execute it. Another easy way to test:
Code:
/usr/bin/(scriptname)
If that executes the script, than permissions are most likely fine. If it doesn't execute, then your permissions are screwed up. That isn't 100% accurate, but is quick and easy.
2) Do you have the extension (if the script has one) associated with something else? I have seen Fedora Core boxes where when you try to download .rpm files, real player tries to play the .rpm as an audio file. If your script has some extension (.cgi, .exe, .*) you should check into that possibility.
One thing about this script is that when I view it in Nautilus it shows up as a text file not a script. How can it be changed from a text file to a script file?
Create a New -> "link to application" in the KDE context menu. Then select properties and change the name, set the working directory, and enter the script name in the execute dialog. Or press "browse" and find it that way. The main point is that there should be a <script-name>.desktop in the ~/.kde/Autostart/ directory, rather than a file link.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.