Bug 168863 - Kopete Reloads Previously Removed Contacts!
Summary: Kopete Reloads Previously Removed Contacts!
Status: RESOLVED FIXED
Alias: None
Product: kopete
Classification: Unmaintained
Component: Yahoo Plugin (show other bugs)
Version: 0.50.80
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 174551 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-08-10 20:31 UTC by Terry
Modified: 2010-01-17 04:57 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Terry 2008-08-10 20:31:02 UTC
Version:           0.50.80 (using 4.1.00 (KDE 4.1.0), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.26-5-generic

When launching Kopete, it immediately loads up contacts not currently in my contact list for Yahoo instant messenger.  These are contacts that I previously removed because I received one and only one message from them and it was SPAM in nature.  When Kopete loses connection with Yahoo, it also reloads these unwanted contacts.  Each time I have to delete/remove these contacts.  Granted, I'm running this version of Kopete on Kubuntu 8.10 Alpha 3 but I've never experienced this even in Kubuntu 8.04.  Please look into this carefully.
Comment 1 Ritesh Raj Sarraf 2008-11-17 11:23:09 UTC
And when I tried to collectively delete all thos spam contacts, I got a crash.

Application: Kopete (kopete), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb586e6c0 (LWP 7234)]
[New Thread 0xaf0ffb90 (LWP 7306)]
[New Thread 0xb1231b90 (LWP 7302)]
[KCrash handler]
#6  0xb6392cac in memcpy () from /lib/i686/cmov/libc.so.6
#7  0xb75d0c10 in KNetwork::Internal::KSocketBuffer::sendTo (this=0x8d3e8e8, 
    dev=0x8b83ac8, len=-1)
    at /tmp/buildd/kde4libs-4.1.3/kdecore/network/k3socketbuffer.cpp:256
#8  0xb75babf0 in KNetwork::KBufferedSocket::slotWriteActivity (
    this=0x8d3eb98)
    at /tmp/buildd/kde4libs-4.1.3/kdecore/network/k3bufferedsocket.cpp:349
#9  0xb75baa20 in KNetwork::KBufferedSocket::qt_metacall (this=0x8d3eb98, 
    _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbff87bcc)
    at /tmp/buildd/kde4libs-4.1.3/obj-i486-linux-gnu/kdecore/k3bufferedsocket.moc:68
#10 0xb66bebd0 in QMetaObject::activate (sender=0x8c21958, 
    from_signal_index=4, to_signal_index=4, argv=0xbff87bcc)
    at kernel/qobject.cpp:3031
#11 0xb66bf952 in QMetaObject::activate (sender=0x8c21958, m=0xb678d050, 
    local_signal_index=0, argv=0xbff87bcc) at kernel/qobject.cpp:3101
#12 0xb66f96e3 in QSocketNotifier::activated (this=0x8c21958, _t1=34)
    at .moc/release-shared/moc_qsocketnotifier.cpp:81
#13 0xb66c47a7 in QSocketNotifier::event (this=0x8c21958, e=0xbff87fa0)
    at kernel/qsocketnotifier.cpp:320
#14 0xb693879c in QApplicationPrivate::notify_helper (this=0x81db448, 
    receiver=0x8c21958, e=0xbff87fa0) at kernel/qapplication.cpp:3803
#15 0xb694061e in QApplication::notify (this=0xbff8843c, receiver=0x8c21958, 
    e=0xbff87fa0) at kernel/qapplication.cpp:3393
#16 0xb785107d in KApplication::notify (this=0xbff8843c, receiver=0x8c21958, 
    event=0xbff87fa0)
    at /tmp/buildd/kde4libs-4.1.3/kdeui/kernel/kapplication.cpp:311
#17 0xb66aa0d1 in QCoreApplication::notifyInternal (this=0xbff8843c, 
    receiver=0x8c21958, event=0xbff87fa0) at kernel/qcoreapplication.cpp:587
#18 0xb66d68ba in QEventDispatcherUNIX::activateSocketNotifiers (
    this=0x81db500)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:209
#19 0xb66d6db3 in QEventDispatcherUNIXPrivate::doSelect (this=0x81dba68, 
    flags={i = -1074233080}, timeout=0xbff88100)
    at kernel/qeventdispatcher_unix.cpp:246
#20 0xb66d8261 in QEventDispatcherUNIX::processEvents (this=0x81db500, flags=
      {i = -1074232548}) at kernel/qeventdispatcher_unix.cpp:889
#21 0xb69d2ed6 in QEventDispatcherX11::processEvents (this=0x81db500, flags=
      {i = -1074232488}) at kernel/qeventdispatcher_x11.cpp:148
#22 0xb66a879a in QEventLoop::processEvents (this=0xbff883d0, flags=
      {i = -1074232424}) at kernel/qeventloop.cpp:143
#23 0xb66a895a in QEventLoop::exec (this=0xbff883d0, flags={i = -1074232360})
    at kernel/qeventloop.cpp:194
#24 0xb66ab015 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#25 0xb6938617 in QApplication::exec () at kernel/qapplication.cpp:3331
#26 0x0808aa4f in main (argc=3, argv=0xbff88824)
    at /tmp/buildd/kdenetwork-4.1.3/kopete/kopete/main.cpp:102
#0  0xb7f6c424 in __kernel_vsyscall ()
Comment 2 Dario Andres 2008-12-04 19:45:32 UTC
Comment 1 is a different backtrace (probably related to bug 170376 , similar backtrace)
Comment 3 doctordruidphd@yahoo.com 2009-03-08 17:20:31 UTC
I am having the same problem. This is kubuntu-8.10 and kubuntu-9.04, running kopete-0.70.0. I have so far been unable to find the location where this information is stored to delete it. The previously removed contacts are immediately reloaded, even if I do not log in, and even if I delete the account and re-create it. Where is this information being stored? It appears to be local and not on the server, because this list does not show up in pidgin. These are all spam contacts, so are very annoying.
Comment 4 Matt Rogers 2009-03-27 04:32:19 UTC
*** Bug 174551 has been marked as a duplicate of this bug. ***
Comment 5 Loki2010 2009-05-21 21:50:40 UTC
This is by no means a fix but it's a temporary patch so to speak. I logged in on a windows system with actual yahoo and removed all ignored contacts and set to only allow users in my contact list. then in kde4 open /home/yourhome/.kde4/share/apps/kopete and deleted the contactlist.xml before starting kopete. That doesn't fix the bug but it does remove the unwanted contacts until it can be resolved. Hope this helps.
Comment 6 doctordruidphd@yahoo.com 2009-05-21 23:44:33 UTC
I can confirm that this workaround is successful, but it does require access to a windows pc. Apparently neither kopete nor pidgin are capable of deleting contacts from the yahoo server itself; pidgin does hide them, but does not delete them.
Comment 7 Dmitriy Volk 2009-05-22 09:21:28 UTC
Bump! I'm having the exact same problem, and it makes using Kopete painful.

Loki2010 and doctordruidphd@yahoo.com : is there a way to run Y!Messenger via wine? The official "linux" version of the Y!M plainly doesn't work on my machine (Kubuntu Jaunty).
Comment 8 Dmitriy Volk 2009-05-22 09:25:56 UTC
Sorry, please disregard my previous comment about wine and official Linux version. There's no linux version, I was running the Windows one from under wine. My apologies.
Comment 9 Dmitriy Volk 2009-05-22 10:02:38 UTC
I apologize for spamming this bugreport, but I wanted to add a couple things to the workaround suggested above:

1. in Jaunty/KDE4.2 Kopete settings including the contactlist.xml are stored in ~/.kde/share/apps/kopete (not ~/kde4).

2. If you're like me and have no access to a Windows machine, you can always start a virtual Windows instance at Amazon EC2.
Comment 10 doctordruidphd@yahoo.com 2009-05-22 18:34:30 UTC
Hello,
I hadn't thought to try running Yahoo Messenger with wine, but yes, that does work. Download the setup file with a browser, then run the setup with wine. It doesn't work perfectly (menu bar doesn't work) but it does allow deleting contacts from the server. Thanks for the tip.
Comment 11 Loki2010 2009-05-24 00:46:32 UTC
Actually there is a linux version of yahoo but it looks like it predates win98 and is not fully functional as in it has no audio or video applications. And on my last attempt to install the actual yahoo with wine it loaded but was lacking as doctordruidphd@yahoo.com mentioned. Until the developers of kopete and or pidgin get full access to the yahoo protocols we are kind of in a holding pattern. If anyone else has any idea's I'm always open.
Comment 12 Matt Rogers 2010-01-17 04:57:23 UTC
we don't add blacklisted or other unauthorized users to the contact list anymore. (as of revision 1075437) so I'm marking this fixed.