Awn

Cannot start awn after installation with bzr

Asked by Yotam Benshalom

Gutsy, Xgl/fglrx.

After installing dependencies and running:
yotam@ubuntu:~$ ./autogen.sh && make && sudo make install
The compilation went fine. But when I run it I get:
yotam@ubuntu:~$ avant-window-navigator
avant-window-navigator: error while loading shared libraries: libawn.so.0: cannot open shared object file: No such file or directory

What is wrong?

Question information

Language:
English Edit question
Status:
Solved
For:
Awn Edit question
Assignee:
No assignee Edit question
Solved by:
Rodrigo Donado
Solved:
Last query:
Last reply:
Revision history for this message
Best Rodrigo Donado (frezeeer) said :
#1

Hi:

the package libawn-bzr has the file you want. hope that helps

Revision history for this message
Yotam Benshalom (benshalom) said :
#2

I gave up on installing from bzr and used a .deb, but thanks.

Revision history for this message
Jasey (jason-rivers) said :
#3

I also have this problem:

$ avant-window-navigator: error while loading shared libraries: libawn.so.0: cannot open shared object file: No such file or directory

the package libawn-bzr won't install under Gutsy, it fails with the following:

libawn-bzr:
 Depends: libwnck18 (>=2.15.90) but it is not installable

Gutsy does not have libwnck18 in it's repo's, and if you try installing from a .deb it tells you there is a newer version already installed, i'm guessing that is the package libwnck22 ?

this is also stopping avant-window-navigator-bzr from installing through apt aswell.

Jason

Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) said :
#4

Are you using the Gutsy packages from thins repo: http://syzygy42.tuxfamily.org/

Revision history for this message
LiFeleSs (lifeless85) said :
#5

mine says: avant-window-navigator: error while loading shared libraries: libawn.so.0: cannot open shared object file: No such file or directory
but if i do:
"
cd src
./avant-window-navigator
"
i managed to run avant
i've compiled/installed the curves one, but from what i've understood it is merged, so it takes the files wich is needed directly from the bzr of the main trunk, so this should be an useless information ... right ?

maybe it just run because my previous un-install didn't erased all the old files, or maybe because the install script isn't copying all the fils in the right place ... how can i get on top of this doubt ?

Revision history for this message
LiFeleSs (lifeless85) said :
#6

ah i was using the package built from the repo mentioned by andrewsomething

Revision history for this message
LiFeleSs (lifeless85) said :
#7

i got rid of this problem, simply some dependency where missing, after nstalling the list of package in this post:
https://answers.launchpad.net/awn/+question/10821

which is:
sudo apt-get install build-essential automake1.9 autotools-dev libxdamage-dev libxcomposite-dev libgnome2-common libgnome2-dev libgnome-desktop-dev libgnome-vfs-dev libgtk2.0-dev libwnck-dev libgconf2-dev libglib2.0-dev libdbus-glib-1-dev libgnomevfs2-0 libgnome-desktop-2 libgnome2-0 libwnck-common python-gtk2 python-gconf bzr gnome-common

and recompiled awn-curves everything seems ok.
except the know bugs ;)

Revision history for this message
Joe Smith (yasumoto7) said :
#8

Thanks a lot LiFeleSs! That fixed everything for me :)

Revision history for this message
LiFeleSs (lifeless85) said :
#9

it's always a pleasure to help, i hope i can do more in the future ^_^
now i'm on my way in understanding why a lot of awn.extras applets did not works properly on my ubuntu.
i'll post soon.

Revision history for this message
Andrew Pritchard (awpritchard) said :
#10

what I did (which worked but is kind of a stupid workaround) after make-ing and make install-ing is just

sudo cp /usr/local/lib/libawn* /usr/lib

apparently it's looking for its libs in /usr/lib but not /usr/local/lib so all you do is move 'em where it wants 'em

Revision history for this message
Mark Lee (malept) said :
#11

That would be bad, especially if you wanted to uninstall it.

The proper answer to this question is, run `sudo ldconfig` after installing. An explanation of this is on the wiki:

http://wiki.awn-project.org/InstallingFromSource#Instructions (step 5)