You are not logged in.
Pages: 1
hey guys I have been using arch for a few months now with no problems, but as the title of this post says after an update about a week ago kopete stopped working. Now judging from the message I got when I ran it through terminal "kopete: error while loading shared libraries: libldap-2.3.so.0: cannot open shared object file: No such file or directory" I figured that an update to libledap( whatever that is) was the culprit. So I waited checking for updates everyday. Well obviously judging from my predicament here that update hasn't came yet.
now for my question: is this problem isolated to me? where can I go to see if anyone else has the same problem (google is no help to a novice like me)? If it is an update issue should i revert libldap-2.3 to its previous version?
P.S I still love arch!!!!
Last edited by jascase901 (2009-10-09 23:20:19)
Offline
I had a very similar problem that stopped alpine working when libldap updated - I even think the terminal output was the same message.
My alpine installation was re-alpine from AUR, so I just removed it with 'yaourt -R re-alpine' and then re-installed it with 'yaourt -S re-alpine' and the re-installation worked.
Not sure if this is even the 'right' way to fix it or even if it will work for kopete, but may be worth a try.
Offline
Thanks, seems like a sensible solution ill try it in about a day or two for now im having fun with pidgin!!!
Offline
I tried reinstalling to no avail, so im not gonna mark this thread solved yet even though I am happy with pidgen.
Offline
Hmm... I would guess that your mirror is not in sync. libldap is at 2.4.18 and should have been upgraded a long while ago. What versions of kopete and libldap do you have installed? Please post the output of
$ pacman -Qi libldap kdenetwork-kopete
Offline
here you go I am pretty sure the mirrors are in sync
Name : libldap
Version : 2.4.18-1
URL : http://www.openldap.org/
Licenses : custom
Groups : None
Provides : None
Depends On : libsasl openssl>=0.9.8f
Optional Deps : None
Required By : apr-util cyrus-sasl cyrus-sasl-plugins gconf gnupg gnupg2
openldap smbclient
Conflicts With : None
Replaces : None
Installed Size : 1848.00 K
Packager : Allan McRae <allan@archlinux.org>
Architecture : i686
Build Date : Mon 14 Sep 2009 01:37:51 AM PDT
Install Date : Tue 06 Oct 2009 09:18:19 PM PDT
Install Reason : Installed as a dependency for another package
Install Script : No
Description : Lightweight Directory Access Protocol (LDAP) client libraries
Name : kdenetwork-kopete
Version : 4.3.1-3
URL : http://www.kde.org
Licenses : GPL LGPL FDL
Groups : kde kdenetwork
Provides : None
Depends On : kdebase-runtime kdepimlibs qca-ossl libotr libmsn>=4.0beta8
libidn qimageblitz libxss libv4l libgadu
Optional Deps : None
Required By : None
Conflicts With : None
Replaces : None
Installed Size : 21792.00 K
Packager : Andrea Scarpino <andrea@archlinux.org>
Architecture : i686
Build Date : Thu 10 Sep 2009 09:34:40 AM PDT
Install Date : Tue 06 Oct 2009 09:17:09 PM PDT
Install Reason : Explicitly installed
Install Script : YesDescription : Instant Messenger
Last edited by jascase901 (2009-10-07 04:31:31)
Offline
Strange. Did you maybe install one of the dependencies of kopete from the AUR and not rebuild them when libldap was updated ca. two weeks ago?
Also, there should a large KDE update to 4.3.2 waiting for you on your mirror (or at least arrive in a few hours). Could you update and report back?
Last edited by mutlu_inek (2009-10-07 04:37:34)
Offline
hmm says my systems up to date. I guess i gotta wait a few hours.
Offline
I figured it out, the last update I installed before my machine started breaking upgraded pacman. this update changed my /etc/pacman.conf, and took the kde mod repos out that i was using. This caused my next update to mix kde stuff with kde mod stuff which is no bueno.
the fix is to type
pacman -Rd kde
pacman -Q grep | kde
to remove all non kde stuff, and to manually check if there is some left repsectivly.
Then readd the kde-mod repos, making sure to add them infront of the standard extra repo.
after just update and all your problems will be solved
Offline
I am glad you were able to fix it.
the last update I installed before my machine started breaking upgraded pacman. this update changed my /etc/pacman.conf, and took the kde mod repos out that i was using.
This, surely, is not the case. pacman upgrades (or any other) never touch /etc/pacman.conf. Otherwise, it would be a major bug.
Offline
Well it was a noob mistake, pacman autogenerated a new pacman.conf file. I then noobishly replaced my pacman .conf with the new pacman.conf.new without taking the time to read the thing.
Offline
Pages: 1