make a desktop shortcut in Linux?
 

just wondering if there's a way to link the "/foo/LimeWire/sh runlime.sh" command to a desktop shortcut in KDE. i've tried all the stuff i could think of (granted i'm a newbie) but i can' t seem to get it to work. I must say that the install of 1.6 went very smoothly and very easily by the way and the program loads nicely on my k6-3-450 machine.
Thanks

Desktop shortcut means an 'Icon' or a 'keyboard combination' like CRTL_ALT_Backspace :D ?

Adding an application is quite simple (out of my head): From the KDE-Menu, click configure panel -> add application -> old program
In case you start LW via the jre, choose the jre in /usr/java/where_it_is
on the next tab, add the command line entries (something like -cp /opt/LW RunLimeWire)
...select a nice icon...thats it

Can't make a desktop link
 

I've been trying to do this forever. A link to the application does not work. Whenever I click on the link, it just times out and Limewire does not appear. Limewire however, runs great from the terminal. And yes, I'm sure I made the link correctly (i think) :P

shortcut
 

i'v e got several icons here and there that look pretty cool 'cause i chose a cool graphic, but none of them will start limewire (they don't seem to do a [inapropriate language deleted] thing as far as i can tell)

plz excuse inapropriate language
 

sorry about the language - i didn't think what i wrote was terribly vulgar but i'm not in charge around here. i'll try not to use similar language in future posts.

have a look at the FAQ
 

http://www.gnutellaforums.com/showth...=3328#section2

more precisely: A 2-8

Running Limewire
 

Use the solution in the FAQ (section 2-8) or you can try the shell script I wrote for my own use. My script does two things. It lets you run LimeWire from anywhere (desktop icon, menu icon, any directory in a terminal, whatever) and, to make LimeWire behave like other unix programs, it creates a .limewire directory in your home directory for LimeWire to write it's configuration files to.

My script is attached. It works brilliantly for me but I've only tested it on my system (RedHat 7.1, KDE2.2, LimeWire1.7, JDK1.3.1). It should work on most systems out there. Give it a try anyway. :-)

To install:

1. Go to the LimeWire directory and backup the old runlime.sh with: mv runlime.sh runlime.old

2. Copy runlime.sh.txt to the LimeWire directory.

3. Rename runlime.sh.txt to runlime.sh with: mv runlime.sh.txt runlime.sh

4. Make it executable with whatever permissions you choose. e.g. chmod 755 runlime.sh


That's it! You can now link to the new runlime.sh script however you like. Note however that because the configuration will now be stored in the ~/.limewire dir, LimeWire will ask you to configure everything as if you had just installed it. By default everything (Shared dir, Incomplete dir, gnutella.net, etc) will be under .limewire in your home directory. If you don't want your Shared directory to be under ~/.limewire make sure you change this when LimeWire prompts you to.

[Update: Feh, I found a bug. Script didn't work when you ran it from the limewire directory with ./runlime.sh. See next post for the fixed version. :-) ]

runlime.sh
 

A replacement runlime.sh. See previous post for install instructions.

oh, even more simple : you have to be in the limewire directory for Limewire to work. Your shortcut doesn't put you there. Well then, I edited runtime.sh and added a

cd /home/(whatever path to your limewire dir)

just after the text and before

J2SE_PREEMPTCLOSE=1; export J2SE_PREEMPTCLOSE

hard to make more simple ?

Yes, it does. The script is generic. It'll work no matter where LimeWire is installed. The line:

cd `dirname $0`

Changes to the LimeWire directory. The $0 variable returns the command used to execute the script. Then the script changes to ~/.limewire so limewire will write it's config files there. The idea is that you can install the LimeWire .tgz under /usr/local as root and then allow multiple users to run LimeWire with multiple configs.

If you run the script with, say:

sh runlime.sh

Then $0 won't refer to the limewire directory. Run it like ./runlime.sh or /usr/local/LimeWire/runlime.sh. Or, as you suggested, write in the directory names manually. :-)

I take that back
 

Feh, sh runlime.sh does actually work! dirname cleverly translates it to '.' the current directory. :-)

Just a clarification
 

Just to clarify something. You don't *have* to be in the LimeWire directory for LimeWire to work. The only reason you start LimeWire from the LimeWire directory when you use the provided runlime.sh is because it only uses the current directory as the class path:

java -classpath . RunLime

If you add the correct classpaths when you're starting up limewire, you can start it from anywhere.

Hang on a second guys, you lost me completely: After installing LW 1.7 i did the following (KDE 2.2.1): Right mouse on the desktop -> create new -> Program
-> Enter program name, choose application (which is /home/your_user_dir/LimeWire17/LimeWire17), select an icon.....(where is the nice LW-icon?)...and thats it!

problem solved
 

yeah, great, it works!

really?
 

I have installed the naked linux program (1.7c without installer). To me it seems that this version requires a script. A simple link to LimeWire17 doesn't work (mostly because this file doesn't exist in the non-installer version ;-) )

And how do you start the 'naked linux program' ?

something like 'jre -cp .....'?

Naked Linux
 

The 'naked linux program' is just a gzipped tar file. It comes with the .jar files and a runlime.sh shell script. You have to run this script in the same directory as the jar files hence the replacement runlime.sh script business. I installed LimeWire this way too and wrote an alternative script for my own use. You can see it at:

http://www.cyberspace.org/~kohl/limewirelinuxhowto.html

The howto was written for 1.7 and probably could use updating now (re where to download). I'll get around to that in the next couple of weeks. :)

I tried both the FAQ method ("cd [my limedir] && sh runlime.sh") and twist's runlime.sh, but neither work from the GNOME menu. It still starts fine from a terminal though...

When ran from the menu it seems as if Limewire actually starts, connects and scans the shared dirs, but no UI appears! There are about two million jre processes hanging around...

BTW, this is with 1.7c. 1.7b started OK from the menu.

1.7c
 

I've just installed 1.7c and it works fine for me from the KDE menu when I use my script. It might be something that the GNOME menu does. But it seems strange that 1.7 works for you and 1.7c doesn't. They start up the same way.

Did you change anything else in your system between installing 1.7 and 1.7c?

Re: 1.7c
 

Yes, I swiped my entire Redhat 7.1 + Ximian GNOME installation and installed Redhat 7.2 with RH's GNOME.

I discovered that both the FAQ and the edited runlime.sh methods actually work from the menu if I check the "Run in terminal" option in the GNOME menu editor.

In the terminal I always get many instances of this warning

Font specified in font.properties not found [--symbol-medium-r-normal--*-%d-*-*-p-*-adobe-fontspecific]

but that doesn't stop Limewire from running OK, as long as it's started from the terminal or from the menu with "run in terminal" selected.

I still don't want to have an unnecessary terminal window hanging around, so the problem isn't solved.

Hrm
 

Don't know about the GNOME problem. I'll have to install and experiment a bit with GNOME to see what's going on.

I can help you with the font properties problem though. I had the same problem. Check out Font properties section of the Java release notes and download and install the revised font properties file:

http://java.sun.com/j2se/1.3/relnotes.html

Re: Hrm
 

Thanks!
Though as you predicted it didn't have any effect on the menu problem, and I also got a new warning in the terminal:

Warning: Cannot convert string "MetaCtrl<Key>Insert" to type VirtualBinding

It still runs fine from a terminal.

Hi,

inbetween I also found the 'naked' version 1.7c, tried and installed...with the same effect as mentioned above.
Without having seen the above comments, I just tweaked the startscrippt and added a
'cd $HOME/LimeWire'
to get it up and running

Re: Hrm
 

I think this is a problem with the Swing classes rather than with LimeWire. I notice this error sometimes as well. It appears to be harmless.

Shortcut Problems
 

I've been trying all the methods in this thread to get a shortcut working.. but a lot are hard to follow.. can anyone give me a summary?

What you do: tweak your startscript:

#!/bin/sh
#
# Runs LimeWire. This script must be executed in your LimeWire
# install directory.
#
# We must set the J2SE_PREEMPTCLOSE environment variable to 1 to
# work around some limitations in the JDK1.3. For more information
# see http://java.sun.com/j2se/1.3/relnotes.html#vm
#
J2SE_PREEMPTCLOSE=1; export J2SE_PREEMPTCLOSE
cd $HOME/LimeWire
java -classpath . RunLime

---then go to the desktop,
Right mouse on the desktop -> create new -> Program
-> Enter program name, choose application (runlime.sh)
..thats it.

1.8
 

Now I can't get the new 1.8 to run from the GNOME menu either. :-P

...but 1.8 (with installer) is fine in KDE...no tweaking

Cheers