launcher

[Peter Garrett]

On Fri, 25 Aug 2006 16:20:12 +0100
Norman Silverstone <norman at littletank.org> wrote:

> 
> > First, I'm assuming the file is executable. If not, run for example
> > chmod +x ~/Desktop/yourfolder/file-to-execute
> 
> When I double click the file in the folder a window appears from which I
> chose run and the application ran.

OK :) So it is executable. Good to know.
> 
> < snip >
> 
> > Third, in the "Command" field, type the full path to the now executable
> > file, which would be
> 
> > ( or /home/your-username/Desktop/yourfolder/file-to-execute )
> 
> I did this but, when I clicked the icon on the desktop nothing happened.

Well, that's odd. Are you quite sure the path is correctly typed ?
( sounds absurdly obvious, I know)

What is this mysterious application? Perhaps that might be a clue to its
misbehaviour ;-)
> 
> > Note the capital "D" in "Desktop".
> > 
> > Not sure why you would put the file in a directory on your desktop though -
> > much neater to put it in ~/bin  or something like that - or if you want all
> > users to be able to execute it, put it in /usr/local/bin  .
> 
> Because I am very ignorant about the workings of Linux so tend to take
> the easy way out.

I like the honesty of the answer ! ( I haven't forgotten my own early days
with Linux, and how puzzling some things seemed then) .

As I suggested above, it might be useful to know what the application is -
some apps have unusual requirements. Other than that, I'm having trouble
working out why the full path to an executable file fails to run it,
unless the window it pops up is actually a terminal, in which case ticking
"run in terminal" for your launcher might do the trick.

Have you tried running it directly from a terminal? Just type

/path/to/mystery/app

and see if it spits out any cryptic information into the terminal. That
output might also be useful...

After 2 AM here - good luck with, it and let us know what you get from the
above ideas.

Peter