| View previous topic :: View next topic |
| Author |
Message |
wbecker Tux's lil' helper

Joined: 16 May 2005 Posts: 95 Location: Melbourne, Australia
|
Posted: Thu Aug 16, 2007 2:05 am Post subject: Kopete can't find libraries |
|
|
After upgrading to 3.5.7 it doesn't find my old accounts and all the configure windows say: The specified library x could not be found, where x is kopete_accountconfig, kopete_behaviorconfig, etc.
It may have had issues compilling: I got some messages at the end saying:
>>> Regenerating /etc/ld.so.cache...
/sbin/ldconfig: /lib/libattr.so.1 is not a symbolic link
But looking at the output of the compile it seems to have created all the right things:
eg:
>>> /usr/kde/3.5/lib64/kde3/kcm_kopete_behaviorconfig.so
>>> /usr/kde/3.5/lib64/kde3/kcm_kopete_behaviorconfig.la
both of which exist.
I might just try rebooting and see if that helps, but I am not sure it will!
Update: no help |
|
| Back to top |
|
 |
didymos Advocate


Joined: 10 Oct 2005 Posts: 4798 Location: California
|
Posted: Thu Aug 16, 2007 3:15 am Post subject: |
|
|
Try running revdep-rebuild. I'd also look into that libattr thing. You might fix it by doing this:
| Code: |
emerge --oneshot attr
|
_________________ Thomas S. Howard |
|
| Back to top |
|
 |
wbecker Tux's lil' helper

Joined: 16 May 2005 Posts: 95 Location: Melbourne, Australia
|
Posted: Thu Aug 16, 2007 7:56 am Post subject: |
|
|
Did the revdep, and remade it. Didn't help, so I recompiled it again. Still broken, though no such warnings now!
Is there anything I can do? Is it worth unmerging it and merging it again? |
|
| Back to top |
|
 |
didymos Advocate


Joined: 10 Oct 2005 Posts: 4798 Location: California
|
Posted: Thu Aug 16, 2007 8:13 am Post subject: |
|
|
Ok, wait a sec: what version did you upgrade from? _________________ Thomas S. Howard |
|
| Back to top |
|
 |
wbecker Tux's lil' helper

Joined: 16 May 2005 Posts: 95 Location: Melbourne, Australia
|
Posted: Thu Aug 16, 2007 8:15 am Post subject: |
|
|
3.5.5 to 3.5.7
Just been keeping up with stable. |
|
| Back to top |
|
 |
didymos Advocate


Joined: 10 Oct 2005 Posts: 4798 Location: California
|
Posted: Thu Aug 16, 2007 8:31 am Post subject: |
|
|
Well, so much for that idea. If you'd been using 3.5.2, I thought it might be a slotting thing. I don't suppose you have one of the old net-im/kopete versions installed, do you? Here, I'll answer for you:
You: No.
Me: So much for that idea. _________________ Thomas S. Howard |
|
| Back to top |
|
 |
wbecker Tux's lil' helper

Joined: 16 May 2005 Posts: 95 Location: Melbourne, Australia
|
Posted: Thu Aug 16, 2007 8:56 am Post subject: |
|
|
Yeah, that can't kind of went out months ago.
Oh well. I'll give the -C a go. |
|
| Back to top |
|
 |
wbecker Tux's lil' helper

Joined: 16 May 2005 Posts: 95 Location: Melbourne, Australia
|
Posted: Thu Aug 16, 2007 10:34 am Post subject: |
|
|
| That didn't help either. Is anyone else having this problem or have I done something funny? |
|
| Back to top |
|
 |
didymos Advocate


Joined: 10 Oct 2005 Posts: 4798 Location: California
|
Posted: Thu Aug 16, 2007 10:51 am Post subject: |
|
|
I've never heard of it, but that's true about a lot of things. I couldn't find anything on Bugzilla that seemed even remotely relevant. I haven't tried checking the KDE bug site though. Maybe something is lurking in /tmp/kde-<whatever> or /var/tmp/kdecache-<whatever>. The current config data could be corrupted as well, which you could test by moving/renaming the ~/.kde/share/apps/kopete directory. _________________ Thomas S. Howard |
|
| Back to top |
|
 |
wbecker Tux's lil' helper

Joined: 16 May 2005 Posts: 95 Location: Melbourne, Australia
|
Posted: Thu Aug 16, 2007 10:58 am Post subject: |
|
|
couldn't find anything in those dirs and moving the .kde/~/kopete dir didn't help either.
It looks like theres a -r1 in portage, so I'll give that a go.
Otherwise I'll be on pidgin.
Thanks for your help! |
|
| Back to top |
|
 |
wbecker Tux's lil' helper

Joined: 16 May 2005 Posts: 95 Location: Melbourne, Australia
|
Posted: Thu Aug 16, 2007 11:57 am Post subject: |
|
|
Actually, now that I look at it again, I see it says:
/usr/lib64/kde3/kcm_kopete_avdeviceconfig.so
which is true: it doesn't exist. Only the /usr/lib64/kde3/kcm_kopete_avdeviceconfig.la does.
This is the same with all the kopete libraries. What is going on? |
|
| Back to top |
|
 |
didymos Advocate


Joined: 10 Oct 2005 Posts: 4798 Location: California
|
Posted: Thu Aug 16, 2007 12:02 pm Post subject: |
|
|
What version of libtool are you using? _________________ Thomas S. Howard |
|
| Back to top |
|
 |
wbecker Tux's lil' helper

Joined: 16 May 2005 Posts: 95 Location: Melbourne, Australia
|
Posted: Thu Aug 16, 2007 12:05 pm Post subject: |
|
|
>libtool --version
ltmain.sh (GNU libtool) 1.5.23b (1.1220.2.437 2007/02/17 09:08:45) |
|
| Back to top |
|
 |
wbecker Tux's lil' helper

Joined: 16 May 2005 Posts: 95 Location: Melbourne, Australia
|
Posted: Fri Aug 17, 2007 1:53 pm Post subject: |
|
|
Something is broken!!
I managed to fix the problem by going:
cp /usr/kde/3.5/lib64/kde3/kcm_kopete_* /usr/lib64/kde3/
cp /usr/kde/3.5/lib64/kde3/kopete_* /usr/lib64/kde3/
Why were they in that directory instead of the one kopete was looking for? |
|
| Back to top |
|
 |
didymos Advocate


Joined: 10 Oct 2005 Posts: 4798 Location: California
|
Posted: Fri Aug 17, 2007 2:06 pm Post subject: |
|
|
Some libs are installed to /usr/lib64/kde3/ and others are installed to /usr/kde/3.5/lib64/kde3/, the distinction seeming to be that kde packages that aren't officially part of KDE go into the former, while official KDE stuff goes into the latter. So, as kopete is part of KDE, /usr/kde/3.5/lib64/kde3 was the right place for the files. I have no idea why kopete doesn't know where it's own files are installed though. _________________ Thomas S. Howard |
|
| Back to top |
|
 |
robin_elvin n00b


Joined: 25 Nov 2004 Posts: 16 Location: Dereham, Norfolk, England
|
Posted: Tue Oct 16, 2007 7:28 pm Post subject: |
|
|
I have the same problem.
After my latest update to KDE 3.5.7 lots of libs now cannot be found. They are in:
/usr/kde/3.5/lib/kde3/
But not in:
/usr/lib/kde3/
Do you think this is worth raising a bug for? Seems to affect lots of packages though (Kopete can't config accounts, Konqueror cannot manage cookies etc.) |
|
| Back to top |
|
 |
bobber205 Guru


Joined: 23 Aug 2006 Posts: 561 Location: Oregon
|
Posted: Tue Oct 16, 2007 8:18 pm Post subject: |
|
|
I would say its definitely worth raising a bug for. It never hurts.  _________________ Never Forget The Expat 2.0! |
|
| Back to top |
|
 |
robin_elvin n00b


Joined: 25 Nov 2004 Posts: 16 Location: Dereham, Norfolk, England
|
|
| Back to top |
|
 |
|