Version: (using KDE KDE 3.5.5) Installed from: Gentoo Packages Adding ICQ contacts doesn't work any more. This only results in an empty contact (no name, no connection). Adding always worked but today it's broken on to computers running kopete. Here's the relevant part of the log (number blanked out): kopete (oscar/icq): [virtual bool ICQAddContactPage::apply(Kopete::Account*, Kopete::MetaContact*)] called; adding contact... kopete (oscar/icq): [virtual bool ICQAddContactPage::apply(Kopete::Account*, Kopete::MetaContact*)] uin=xxxx kopete (oscar): [virtual bool OscarAccount::createContact(const QString&, Kopete::MetaContact*)] New contact 'xxxx' not in SSI. Creating new contact kopete (oscar): [virtual bool OscarAccount::createContact(const QString&, Kopete::MetaContact*)] Adding xxxx to server side list kopete (oscar): [virtual bool OscarAccount::createContact(const QString&, Kopete::MetaContact*)] Contact with group. No. of groups = 1 Name of first group = Uni kopete (oscar - raw protocol): [void Client::addContact(const QString&, const QString&)] Adding contact xxxx to SSI in group Uni kopete (oscar - raw protocol): [bool SSIModifyTask::addContact(const QString&, const QString&, bool)] creating new SSI item for xxxx in group Uni kopete (oscar - raw protocol): [void SSIModifyTask::sendSSIUpdate()] Adding an item to the SSI list libkopete: [bool Kopete::Account::addContact(const QString&, Kopete::MetaContact*, Kopete::Account::AddMode)] changing KABC libkopete: [void Kopete::KABCPersistence::write(Kopete::MetaContact*)] looking up Addressee for ... kopete (oscar - raw protocol): [void CoreProtocol::addIncomingData(const QByteArray&)] Received 26 bytes. kopete (oscar - raw protocol): [virtual Transfer* SnacProtocol::parse(const QByteArray&, uint&)] family: 19 subtype: 14 flags: 32768 id: 62618 kopete (oscar - raw protocol): Acknowledgement code is 14 kopete (oscar - raw protocol): [void SSIModifyTask::handleSSIAck()] Can't add item because contact requires authorization kopete (oscar - raw protocol): [bool SSIModifyTask::addContact(const QString&, const QString&, bool)] This contact requires auth. adding appropriate tlv kopete (oscar - raw protocol): [bool SSIModifyTask::addContact(const QString&, const QString&, bool)] creating new SSI item for xxxx in group Uni kopete (oscar - raw protocol): [void Oscar::SSI::checkTLVs()] Need auth for contact xxxx kopete (oscar - raw protocol): [void SSIModifyTask::sendSSIUpdate()] Adding an item to the SSI list kopete (oscar - raw protocol): [void CoreProtocol::addIncomingData(const QByteArray&)] Received 26 bytes. kopete (oscar - raw protocol): [virtual Transfer* SnacProtocol::parse(const QByteArray&, uint&)] family: 19 subtype: 14 flags: 32768 id: 62621 kopete (oscar - raw protocol): Acknowledgement code is 1 kopete (oscar - raw protocol): [void SSIModifyTask::handleSSIAck()] Unknown acknowledgement code
Acknowledgement code 1 isn't documented so we don't know why it has failed. Can you add anybody to in/visible list? Can you add contacts with web client go.icq.com? Thanks
Adding with any other client works. Visible- / Invisible-list don't work with kopete, either.
That's odd, what version of Kopete ebuild do you have intalled?
Latest stable build 3.5.5-r2 I got a new router a few weeks ago and since then it was the first time i tried to add someone, I think. But it uses the same settings and I can't imagine anything the router could disturb. Strange think is that both systems have the same problem.
I cannot reproduce it with kde-base/kopete-3.5.5-r2. :( It would be great if you could try svn version, because it can be bug 133950.
*** Bug 143672 has been marked as a duplicate of this bug. ***
Closing as there were many changes to ICQ protocol since KDE 3.5, if you still see this bug in KDE 4.1 or greater please reopen.
Reopening, saw the exact symptoms described by the reporter, today with Kopete shipped with KDE 4.2.1.
Need new debug output. Please provide and reopen.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!