You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Saturday, March 6th 2004, 11:29pm

Yahoo Not Working

I'm a newbie and using Kopete under SuSE 9. I've updated Kopete to the latest release, yet it doesn't connect to Yahoo. Checked the Yahoo site and they show 'CSA' and port 5050 instead of 'SCA" and port 5050, however still nothing. Wondering if my installing Mozilla and Firefox in my file/home/usrname dir is part of the problem? Konqueror is still intact, though. Any help would be appreciated.

2

Sunday, March 7th 2004, 12:37am

Ahem...nebber mind...found that I hadn't updated to latest Kopete version after all. Once I did, everything now works (newbie...*sigh*...)

3

Thursday, March 11th 2004, 12:29pm

Kopete Problem - XML Not Parsed (Yahoo)

Very strange, but after using Kopete for one day without problems, every time I try to use it now I can send messages in Yahoo, but the return messages are shown as "An Internal Kopete error has ocurred while parsing a message - XML document could not be parsed". Stranger still is that many times the FIRST response or two will be fine, but the error will happen on subsequent responses. I have un-installed from /home/usr and re-installed under /opt/kde3 but no difference. Anyone have any suggestions?

4

Thursday, March 11th 2004, 4:35pm

i am having the same issue.. it worked sometimes but not all the time when i was on 8rc1 but when i downloaded the last update it over-wrote it with an older one, and i got the kopete8 suse rpm. and after much deleting of all the old stuff it worked, yay! i can now offically log into yahoo except no one can talk to me. i get the same xml error these guys are talking about...

5

Saturday, March 13th 2004, 9:35pm

same prob hear looks like bug issue