View previous topic :: View next topic |
Author |
Message |
ralle Tux's lil' helper
Joined: 25 Mar 2003 Posts: 144 Location: Aachen, Germany
|
Posted: Wed Feb 04, 2004 4:13 pm Post subject: Kopete in kde 3.2 problem |
|
|
When I try to setup the Kopete Instant Messenger I get this strange problem:
I get to the point where you can select the different protocols, then I may pick any item and kopete will always complain: "Das Protokoll `ICQ' kann nicht geladen werden." which means something like "The protocol ICQ could not be loaded" in English.
Anybody experienced the same? Any solutions? |
|
Back to top |
|
|
dr.gonzo n00b
Joined: 12 Nov 2002 Posts: 7 Location: Montreal, QC
|
Posted: Wed Feb 04, 2004 4:45 pm Post subject: |
|
|
it could be that you have an older version of it lying around that it could be trying to load a plugin for.. (i used to get those errors).. either unmerge it if you have it installed (it comes with KDE 3.2 anyways) or manually delete any 'kopete' files in /usr/kde/3.2 and then compile it by hand from source (i use CVS HEAD every day with no problems but your mileage may vary) _________________ .....watch more tv..... |
|
Back to top |
|
|
ZothOmmog Apprentice
Joined: 05 May 2003 Posts: 216 Location: Nashville, TN
|
Posted: Wed Feb 04, 2004 5:06 pm Post subject: |
|
|
According to the KDE buglist, this seems to be a Gentoo specific problem: http://bugs.kde.org/show_bug.cgi?id=67668.
For the record, I did unmerge Kopete prior to emerging KDE 3.2, and I still get this same error with the new version. _________________ -It's gonna take a lot of fireworks to clean this place up. |
|
Back to top |
|
|
ralle Tux's lil' helper
Joined: 25 Mar 2003 Posts: 144 Location: Aachen, Germany
|
Posted: Wed Feb 04, 2004 7:25 pm Post subject: Fix |
|
|
I fixed it myself. Using the information from the link above, I changed the file /etc/env.d/99kde-env from:
Code: |
KDEDIRS=/usr
CONFIG_PROTECT=/usr/share/config
|
to
Code: |
KDEDIRS=/usr/kde/3.2:/usr
CONFIG_PROTECT=/usr/share/config
|
Then and a reboot to make absolutely sure, but no recompile or something...
Now kopete works like a charm! |
|
Back to top |
|
|
MrIch Apprentice
Joined: 25 May 2002 Posts: 204
|
Posted: Thu Feb 05, 2004 9:38 pm Post subject: |
|
|
If I change the KDEDIRs, programs like koffice doest not appear in the k-menu anymore...
Also mldonkey doest not work then...
Any ideas? |
|
Back to top |
|
|
ralle Tux's lil' helper
Joined: 25 Mar 2003 Posts: 144 Location: Aachen, Germany
|
Posted: Thu Feb 05, 2004 9:48 pm Post subject: |
|
|
I don't have any problems with disappearing icons or kmldonkey not working (assuming you really meant kmldonkey, not the mldonkey daemon).
Maybe it's because I completely unmerged my old kde before installing 3.2.
You could take a look at /usr/kde/3.2/share/applnk and /usr/kde/3.1/share/applnk to check out where the koffice icons are installed.
Perhaps unmerging the old version is required in some cases... |
|
Back to top |
|
|
danthe n00b
Joined: 09 Feb 2004 Posts: 1
|
Posted: Mon Feb 09, 2004 5:36 pm Post subject: the quickest solution |
|
|
After a little playing with strace, I found the old files, which were not unmerged when I cleaned kopete from my system before upgrading to kde 3.2.
In /usr/lib/kde3, there were some old .la files. After I removed them (rm /usr/lib/kde3/kopete_*) and restarted kopete, everything worked correctly again.
I only had to restart kopete. There's no need to re-emerge anything, not even reset of restart kde... |
|
Back to top |
|
|
tlaloctlaloc Apprentice
Joined: 11 Feb 2004 Posts: 198 Location: Europe-In the heart of the Alps
|
Posted: Wed Feb 11, 2004 9:57 am Post subject: |
|
|
That worked for me. Thanks. |
|
Back to top |
|
|
RioFL Guru
Joined: 31 Oct 2002 Posts: 407
|
Posted: Sat Feb 14, 2004 7:43 pm Post subject: Re: the quickest solution |
|
|
danthe wrote: | After a little playing with strace, I found the old files, which were not unmerged when I cleaned kopete from my system before upgrading to kde 3.2.
In /usr/lib/kde3, there were some old .la files. After I removed them (rm /usr/lib/kde3/kopete_*) and restarted kopete, everything worked correctly again.
I only had to restart kopete. There's no need to re-emerge anything, not even reset of restart kde... |
I had the same problem, and that is what worked for me too. Someone should add that deletion into the kdenetwork ebuild system! It is going to be a "more often than not" problem otherwise.
Chuck |
|
Back to top |
|
|
cvk Guru
Joined: 06 Jan 2003 Posts: 314 Location: Our house, in the middle of our street
|
Posted: Thu Mar 11, 2004 11:18 am Post subject: |
|
|
Works fine now, thanks a lot.
Chris _________________ Adopt an unanswered post now. |
|
Back to top |
|
|
gondoi Tux's lil' helper
Joined: 27 Mar 2003 Posts: 138 Location: San Angelo, TX
|
Posted: Mon Mar 29, 2004 5:21 pm Post subject: |
|
|
I have a problem with ICQ, but I don't think it has anything to do with the module loading.
I am running KDE 3.2.1 (fresh install, not an upgrade) And I'm running Kopete 0.8.1. I have been able to connect to ICQ for a while but here recently the icon just flashes in the bottom like it's trying to connect, but then after a while it just quits. I can connect from a windows machine on the network fine. So I'm not sure what's going on here. Where are the error logs for kopete? or does anyone know an answer?
Thanks _________________ "I'm only acting retarded, what's your excuse?"
- The Gord |
|
Back to top |
|
|
RioFL Guru
Joined: 31 Oct 2002 Posts: 407
|
Posted: Mon Mar 29, 2004 5:37 pm Post subject: |
|
|
gondoi wrote: | I have a problem with ICQ, but I don't think it has anything to do with the module loading.
I am running KDE 3.2.1 (fresh install, not an upgrade) And I'm running Kopete 0.8.1. I have been able to connect to ICQ for a while but here recently the icon just flashes in the bottom like it's trying to connect, but then after a while it just quits. I can connect from a windows machine on the network fine. So I'm not sure what's going on here. Where are the error logs for kopete? or does anyone know an answer?
Thanks |
unfortunately I don't know where the logs are, but mine also takes quite a while compared to the others to connect, plus i experience random disconnects from icq and aim. never from yahoo. once i reconnect it is fine again for however long. many times when leaving it connected but idle over night i find it disconnected from them in the morning.
Chuck |
|
Back to top |
|
|
gondoi Tux's lil' helper
Joined: 27 Mar 2003 Posts: 138 Location: San Angelo, TX
|
Posted: Mon Mar 29, 2004 7:11 pm Post subject: |
|
|
I see these problems too. Almost all of them get disconnected an stay that way. It doesn't seem to try and reconnect.
But about my post from above, I figured out what the deal was. When I re-compiled kdenetwork applying the kget patch, I still had KDE and kopete running, apparently it screwed up the module or something, not sure.
At any rate, I logged out of KDE and kdm and recompiled kdenetwork and now everything works great... (well except for the staying connected thing that has come up) _________________ "I'm only acting retarded, what's your excuse?"
- The Gord |
|
Back to top |
|
|
RioFL Guru
Joined: 31 Oct 2002 Posts: 407
|
Posted: Mon Mar 29, 2004 7:19 pm Post subject: |
|
|
gondoi wrote: | I see these problems too. Almost all of them get disconnected an stay that way. It doesn't seem to try and reconnect.
But about my post from above, I figured out what the deal was. When I re-compiled kdenetwork applying the kget patch, I still had KDE and kopete running, apparently it screwed up the module or something, not sure.
At any rate, I logged out of KDE and kdm and recompiled kdenetwork and now everything works great... (well except for the staying connected thing that has come up) |
yeah. wish they would find a way to terminate the processes or at least tell you about that and make you quit the programs first. i had odd stuff happen too when i did a kde /kopete upgrade and i was still running it... wound up killing xdm and recompiling everything from tty1. suddenly it all worked right |
|
Back to top |
|
|
|