[Bug 213494] Re: [Hardy] Glipper dies when desktop starting

[chappejw]

I have fixed the glipper start up problem with an easier solution.

First of all after installing 'glipper' with 'sudo apt-get install
glipper' when we do a 'which glipper' we see that it is not found in the
PATH. Hmm interesting... When I do a 'whereis glipper' it shows...

glipper: /usr/lib/glipper /usr/share/glipper

Then it is not available unless the full path is specified... so, here
is the solution. We want to create a soft link to a new /usr/bin/glipper
from /usr/lib/glipper/glipper. This will allow glipper to be found in
our existing path.

1) First create a soft link to the glipper executable...

sudo ln -s -T /usr/lib/glipper/glipper /usr/bin/glipper

now if you do a 'which glipper' you will see it is found at
/usr/bin/glipper

2) Of course we know that glipper is supposed to be a gnome applet,
however it will still have the "The panel encountered a problem while
loading OAFIID:Glipper...." problem unless we ensure it will start
properly from /usr/bin/glipper so... go to System > Preferences >
Sessions and on the Startup Programs tab click the +Add button

3) With the Add Startup Program box open

Name: glipper
Command: /usr/bin/glipper
Comment: Glipper Clipboard Manager etc....

...and click OK

4) now, we want the applet to start so...

right click your panel and select Clipboard manager then +Add button

5) ok you are pretty much done. To make sure everything is good to go on startup, restart your computer and
    you will have glipper available on your Gnome panel... the Glipper pop-up shortcut is <ctrl>+<alt>+<c>
    so make sure you did not set those keys for another shortcut combo.

6) Done..!

Hope that helps every one who wants to use Glipper on Ubuntu Hardy
Heron... it's a great simple tool..!

Jake



** Attachment added: "System > Preferences > Sessions"
   http://launchpadlibrarian.net/17313861/Screenshot-Sessions%20Preferences.png

-- 
[Hardy] Glipper dies when desktop starting
https://bugs.launchpad.net/bugs/213494
You received this bug notification because you are a member of Ubuntu
Sponsors for universe, which is a direct subscriber.