Version: 0.11.91 (using KDE 3.5.1, Gentoo) Compiler: gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8) OS: Linux (i686) release 2.6.14-gentoo-r5 Hello, My dev-12 kopete crashes now for some time. I thought someone knew about the crash, but it seems not. I have quite a few transports, and some of them are not usual (sms, television program). From the time when jabber plugin added the fake accounts for transport, kopete crashes on every login. I suspect it crashes when some of the non-standard transports send an available presence. I will add a backtrace and the end of console output. Thank you.
Created attachment 14768 [details] The backstrace The backtrace
Created attachment 14769 [details] The console output This is the console output. I removed the jid's from roster and replaced them by "removed", so the people won't get angry with me.
Can you try disabling some of the transports until you find out which one causes the crash?
Well, I can't, since many of them ask for user reauthorization on every adding of the transport and I won't listen again to hundred ICQ people shouting why on earth I ask them for authirization again. But I tried to add transports, one by one, to another testing account and it crashed when I added yahoo@netlab.cz (well, after I added and restarted Kopete). It was second transport, may it be that threre are more than one transport?
I'm having problems with the jabber transports as well. I ran kopete in gdb a couple of times. Sometimes it crashes right at startup, sometimes when I right-click on the transport icon (in the status bar), and sometimes it just crashes without me doing anything at all (status change?). So far, all crashes have been in the ICQ transport, and always in Contact::account() or Account::myself() (always called from Contact::onlineStatus(), as suggested by the backtraces). The problem is always the this pointer, which sometimes is NULL, and sometimes contains some random value. So for some reason the myself() pointer in the transport account is invalid. Version: 0.12-svn (2006-02-25) Compiler: gcc-4.0.2 OS: Linux (x86_64) 2.6.15
Created attachment 14864 [details] crash backtrace
Created attachment 14865 [details] another crash backtrace Don't know if more backtraces will help, but here is another one.
SVN commit 517255 by ogoffart: Add debug output that may help me to fix the bug 122269 Please update, and try to reproduce the bug again, and paste me the debug output. CCBUG: 122269 M +2 -0 jabberaccount.cpp M +3 -1 jabbercontact.cpp M +1 -1 jabbercontactpool.cpp M +2 -0 jabbertransport.cpp --- branches/kopete/0.12/kopete/protocols/jabber/jabberaccount.cpp #517254:517255 @@ -1321,6 +1321,8 @@ Kopete::MetaContact *metaContact=c->metaContact(); if(metaContact->isTemporary()) return; + kdDebug (JABBER_DEBUG_GLOBAL) << k_funcinfo << c->contactId() << + " is on the contactlist while it shouldn't. we are removing it. - " << c << endl; delete c; if(metaContact->contacts().isEmpty()) Kopete::ContactList::self()->removeMetaContact( metaContact ); --- branches/kopete/0.12/kopete/protocols/jabber/jabbercontact.cpp #517254:517255 @@ -1184,7 +1184,7 @@ if ( dontSync () || !account()->isConnected () || metaContact()->isTemporary () || metaContact() == Kopete::ContactList::self()->myself() ) return; -// kdDebug ( JABBER_DEBUG_GLOBAL ) << k_funcinfo << contactId () << " - " <<kdBacktrace() << endl; + kdDebug ( JABBER_DEBUG_GLOBAL ) << k_funcinfo << contactId () /*<< " - " <<kdBacktrace()*/ << endl; if(!m_syncTimer); { @@ -1540,6 +1540,8 @@ JabberAccount *parentAccount=account(); Kopete::OnlineStatus status=onlineStatus(); + kdDebug() << k_funcinfo << jid << " is not a contact but a gateway - " << this << endl; + delete this; //we are not a contact i said ! if(mc->contacts().count() == 0) --- branches/kopete/0.12/kopete/protocols/jabber/jabbercontactpool.cpp #517254:517255 @@ -68,7 +68,7 @@ JabberContactPoolItem *mContactItem = findPoolItem ( contact ); if ( mContactItem) { - kdDebug(JABBER_DEBUG_GLOBAL) << k_funcinfo << "Updating existing contact " << contact.jid().full() << endl; + kdDebug(JABBER_DEBUG_GLOBAL) << k_funcinfo << "Updating existing contact " << contact.jid().full() << " - " << mContactItem->contact() << endl; // It exists, update it. mContactItem->contact()->updateContact ( contact ); --- branches/kopete/0.12/kopete/protocols/jabber/jabbertransport.cpp #517254:517255 @@ -291,6 +291,7 @@ * - a new contact will born, with the same characteristics, but owned by the transport * - Olivier 2006-01-17 - */ + kdDebug() << k_funcinfo << endl; QDict<Kopete::Contact> cts=account()->contacts(); QDictIterator<Kopete::Contact> it( cts ); for( ; it.current(); ++it ) @@ -301,6 +302,7 @@ XMPP::RosterItem item=contact->rosterItem(); Kopete::MetaContact *mc=contact->metaContact(); Kopete::OnlineStatus status = contact->onlineStatus(); + kdDebug() << k_funcinfo << item.jid().full() << " will be soon eat - " << contact << endl; delete contact; Kopete::Contact *c2=account()->contactPool()->addContact( item , mc , false ); //not sure this is false; if(c2)
Created attachment 15049 [details] debug output before crash Here is the log-output after updating to r517492. I'm getting more convinced that it is related to the ICQ-transport, at least in my case. Some observations I have made: 1. Before the crash, the ICQ-transport instance is freed. Some time later, a response is coming from the ICQ-transport on the jabber server. I don't know how these things are handled in kopete, but I never see the MSN-transport being freed (and I've never seen any crashes in it either). 2. At one occasion I actually managed to start kopete and login without getting a crash. However, the ICQ-transport was offline. When I tried to set availability to online, it complained and said I have to be connected (which I was, all my jabber- and MSN-contacts were functioning). What's even more strange is that kopete seemed to think I had a second jabber-account. This account was named jabber.dk/registered. I assume the ICQ-transport was somehow connected to this account. Naturally, I could not log in on this second jabber-account. 3. Often the account-icons on the status-bar is completely messed up; the ICQ-transport icon can be invisible while the ICQ popup menu is accessible via the jabber-account icon; the jabber popup menu is then accessible from where the ICQ-transport icon should have been (where it's just an empty space instead). I realize this may not have anything at all to do with this bug, but then again, maybe it has. Since you haven't been able to reproduce this, let me know if you want me to look for something particular.
Do you have updated your kopete ? i don't see new added debug line in it. Also, I need both the backtrace and the debug ouput. (since i added the address of contact in the debug output to know which one is causing the crash) And yes, it's certenly related to transport code, but i'm not able to reproduce on my side.
Created attachment 15050 [details] another log Sorry about that. I will attach a new log+backtrace. Yes, kopete is up-to-date. Before I created this backtrace I updated it again, and checked that I had no local modifications. I am now on r517518. What debug-line are you thinking of? The "contact will soon be eat" one? It does enter that function, but never the if-statement containing the debug-line.
Created attachment 15051 [details] backtrace to go with log-output
SVN commit 517530 by ogoffart: Add even more debug in order to track bug 122269 CCBUG: 122269 Thanks to still provide me the same info with this new debug. M +9 -2 jabbercontact.cpp M +2 -0 jabbercontact.h M +4 -2 jabbertransport.cpp M +2 -0 libiris/iris/xmpp-im/types.cpp --- branches/kopete/0.12/kopete/protocols/jabber/jabbercontact.cpp #517529:517530 @@ -66,7 +66,7 @@ JabberContact::JabberContact (const XMPP::RosterItem &rosterItem, Kopete::Account *_account, Kopete::MetaContact * mc, const QString &legacyId) : JabberBaseContact ( rosterItem, _account, mc, legacyId) , m_syncTimer(0L) { - + kdDebug(JABBER_DEBUG_GLOBAL) << k_funcinfo << contactId() << " is created - " << this << endl; // this contact is able to transfer files setFileCapable ( true ); @@ -120,6 +120,13 @@ mDiscoDone = false; } + + +JabberContact::~JabberContact() +{ + kdDebug(JABBER_DEBUG_GLOBAL) << k_funcinfo << contactId() << " is destroyed - " << this << endl; +} + QPtrList<KAction> *JabberContact::customContextMenuActions () { @@ -1539,7 +1546,7 @@ JabberAccount *parentAccount=account(); Kopete::OnlineStatus status=onlineStatus(); - kdDebug() << k_funcinfo << jid << " is not a contact but a gateway - " << this << endl; + kdDebug(JABBER_DEBUG_GLOBAL) << k_funcinfo << jid << " is not a contact but a gateway - " << this << endl; delete this; //we are not a contact i said ! --- branches/kopete/0.12/kopete/protocols/jabber/jabbercontact.h #517529:517530 @@ -39,6 +39,8 @@ JabberContact (const XMPP::RosterItem &rosterItem, Kopete::Account *account, Kopete::MetaContact * mc, const QString &legacyId = QString()); + + ~JabberContact(); /** * Create custom context menu items for the contact --- branches/kopete/0.12/kopete/protocols/jabber/jabbertransport.cpp #517529:517530 @@ -48,6 +48,8 @@ JabberContact *myContact = m_account->contactPool()->addContact ( XMPP::RosterItem ( myselfContactId ), Kopete::ContactList::self()->myself(), false ); setMyself( myContact ); + kdDebug(JABBER_DEBUG_GLOBAL) << k_funcinfo << " transport created: myself: " << myContact << endl; + //we have to know if the account get loaded from the config, or newly created bool exist=configGroup()->readBoolEntry("exist",false); @@ -291,7 +293,7 @@ * - a new contact will born, with the same characteristics, but owned by the transport * - Olivier 2006-01-17 - */ - kdDebug() << k_funcinfo << endl; + kdDebug(JABBER_DEBUG_GLOBAL) << k_funcinfo << endl; QDict<Kopete::Contact> cts=account()->contacts(); QDictIterator<Kopete::Contact> it( cts ); for( ; it.current(); ++it ) @@ -302,7 +304,7 @@ XMPP::RosterItem item=contact->rosterItem(); Kopete::MetaContact *mc=contact->metaContact(); Kopete::OnlineStatus status = contact->onlineStatus(); - kdDebug() << k_funcinfo << item.jid().full() << " will be soon eat - " << contact << endl; + kdDebug(JABBER_DEBUG_GLOBAL) << k_funcinfo << item.jid().full() << " will be soon eat - " << contact << endl; delete contact; Kopete::Contact *c2=account()->contactPool()->addContact( item , mc , false ); //not sure this is false; if(c2) --- branches/kopete/0.12/kopete/protocols/jabber/libiris/iris/xmpp-im/types.cpp #517529:517530 @@ -615,8 +615,10 @@ } else if(e.tagName() == "thread") d->thread = e.text(); +#if 0 } else if (e.namespaceURI() == s.xhtmlImNS()) { +#endif if (e.tagName() == "html") { QDomNodeList htmlNL= e.childNodes(); for (unsigned int x = 0; x < htmlNL.count(); x++) {
Created attachment 15052 [details] debug-log Here's the log.
Created attachment 15053 [details] backtrace Here's the backtrace.
The problem is maybe because your icq transport is on your roster with a ressource, while kopete only expect bare Jid on the roster. I've made Kopete more tollerent, and ignore the ressource. I've also made it double check to don't add a transport twice (which is what may hapenned, Kopete has not detected the account existed because the contact has not the correct terminaison) The ressounrce'd contact may have been added with an old version of kopete. I remember having fixed that because i had the problem with the icq gateway, preciselly. Can you upgrade svn, and check if it still crash ? if yes, please paste me the output since the kopete start
I finally managed to compile the new version and yes, it seems fixed. It did not crash and the icons are loaded OK. Thank you. (Should I mark it as resolved, or I should wait for others?)
good. so the bug may be closed, and i'll remove lot of useless now debug output.
Hi, could you please investigate if this crash after the attempted login in to my jabber account is the same? Kopete version 3.5.7 under Debian unstable is used. I had the impression that it may result from an undefined interaction with the kde wallet which popped up in parallel to the crash but did no longer so after I assigned empty passwords to it. I did not ask to have the passwort stored there at any time - which may be another issue. Cheers, Steffen Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47396625505952 (LWP 8699)] [KCrash handler] #5 0x00002b1b6221781d in __dynamic_cast () from /usr/lib/libstdc++.so.6 #6 0x00002b1b65375fe0 in JabberEditAccountWidget::apply (this=0xac0680) at /build/buildd/kdenetwork-3.5.7/./kopete/protocols/jabber/ui/jabbereditaccountwidget.cpp:141 #7 0x0000000000446880 in AddAccountWizard::accept (this=0x9247c0) at /build/buildd/kdenetwork-3.5.7/./kopete/kopete/addaccountwizard/addaccountwizard.cpp:180 #8 0x00002b1b5ffed818 in QDialog::qt_invoke (this=0x9247c0, _id=48, _o=0x7fff4f6fee20) at .moc/debug-shared-mt/moc_qdialog.cpp:108 #9 0x00002b1b5fff15db in QWizard::qt_invoke (this=0x9247c0, _id=48, _o=0x7fff4f6fee20) at .moc/debug-shared-mt/moc_qwizard.cpp:152 #10 0x00002b1b5dd95eb9 in KWizard::qt_invoke (this=0xac0680, _id=0, _o=0x6) at ./kwizard.moc:77 #11 0x00000000004465ed in AddAccountWizard::qt_invoke (this=0x9247c0, _id=48, _o=0x7fff4f6fee20) at ./addaccountwizard.moc:105 #12 0x00002b1b5fc54c2e in QObject::activate_signal (this=0x8fdc50, clist=0x9ba580, o=0x7fff4f6fee20) at kernel/qobject.cpp:2356 #13 0x00002b1b5fc557be in QObject::activate_signal (this=0x8fdc50, signal=4) at kernel/qobject.cpp:2325 #14 0x00002b1b5ffca447 in QButton::clicked (this=0x8fdc50) at .moc/debug-shared-mt/moc_qbutton.cpp:152 #15 0x00002b1b5fceebdf in QButton::mouseReleaseEvent (this=0x8fdc50, e=0x7fff4f6ff460) at widgets/qbutton.cpp:836 #16 0x00002b1b5fc891d2 in QWidget::event (this=0x8fdc50, e=0x7fff4f6ff460) at kernel/qwidget.cpp:4702 #17 0x00002b1b5fbf026a in QApplication::internalNotify (this=0x7fff4f7007c0, receiver=0x8fdc50, e=0x7fff4f6ff460) at kernel/qapplication.cpp:2635 #18 0x00002b1b5fbf23e9 in QApplication::notify (this=0x7fff4f7007c0, receiver=0x8fdc50, e=0x7fff4f6ff460) at kernel/qapplication.cpp:2421 #19 0x00002b1b5eab7438 in KApplication::notify (this=0x7fff4f7007c0, receiver=0x8fdc50, event=0x7fff4f6ff460) at /build/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kapplication.cpp:550 #20 0x00002b1b5fb83874 in QApplication::sendSpontaneousEvent ( receiver=0x8fdc50, event=0x7fff4f6ff460) at kernel/qapplication.h:523 #21 0x00002b1b5fb8249f in QETWidget::translateMouseEvent (this=0x8fdc50, event=0x7fff4f6ffa00) at kernel/qapplication_x11.cpp:4301 #22 0x00002b1b5fb808ff in QApplication::x11ProcessEvent (this=0x7fff4f7007c0, event=0x7fff4f6ffa00) at kernel/qapplication_x11.cpp:3478 #23 0x00002b1b5fb968ba in QEventLoop::processEvents (this=0x744a60, flags=4) at kernel/qeventloop_x11.cpp:192 #24 0x00002b1b5fc097f6 in QEventLoop::enterLoop (this=0x744a60) at kernel/qeventloop.cpp:198 #25 0x00002b1b5fbf1ce6 in QApplication::enter_loop (this=0x7fff4f7007c0) at kernel/qapplication.cpp:2793 #26 0x00002b1b5fdfa83b in QDialog::exec (this=0x9247c0) at dialogs/qdialog.cpp:432 #27 0x00000000004367c3 in KopeteApplication::slotLoadPlugins ( this=0x7fff4f7007c0) at /build/buildd/kdenetwork-3.5.7/./kopete/kopete/kopeteapplication.cpp:204 #28 0x0000000000436ea0 in KopeteApplication::qt_invoke (this=0x7fff4f7007c0, _id=23, _o=0x7fff4f6ffef0) at ./kopeteapplication.moc:93 #29 0x00002b1b5fc54c2e in QObject::activate_signal (this=0x920830, clist=0x920750, o=0x7fff4f6ffef0) at kernel/qobject.cpp:2356 #30 0x00002b1b5ffc2110 in QSignal::signal (this=0x920830, t0=@0x920880) at .moc/debug-shared-mt/moc_qsignal.cpp:100 #31 0x00002b1b5fc73cff in QSignal::activate (this=0x920830) at kernel/qsignal.cpp:212 #32 0x00002b1b5fc7acbe in QSingleShotTimer::event (this=0x9207e0) at kernel/qtimer.cpp:286 #33 0x00002b1b5fbf026a in QApplication::internalNotify (this=0x7fff4f7007c0, receiver=0x9207e0, e=0x7fff4f7003e0) at kernel/qapplication.cpp:2635 #34 0x00002b1b5fbf2014 in QApplication::notify (this=0x7fff4f7007c0, receiver=0x9207e0, e=0x7fff4f7003e0) at kernel/qapplication.cpp:2358 #35 0x00002b1b5eab7438 in KApplication::notify (this=0x7fff4f7007c0, receiver=0x9207e0, event=0x7fff4f7003e0) at /build/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kapplication.cpp:550 #36 0x00002b1b5fb83802 in QApplication::sendEvent (receiver=0x9207e0, event=0x7fff4f7003e0) at ../include/qapplication.h:520 #37 0x00002b1b5fbe357c in QEventLoop::activateTimers (this=0x744a60) at kernel/qeventloop_unix.cpp:556 #38 0x00002b1b5fb97584 in QEventLoop::processEvents (this=0x744a60, flags=4) at kernel/qeventloop_x11.cpp:389 #39 0x00002b1b5fc097f6 in QEventLoop::enterLoop (this=0x744a60) at kernel/qeventloop.cpp:198 #40 0x00002b1b5fc095ff in QEventLoop::exec (this=0x744a60) at kernel/qeventloop.cpp:145 #41 0x00002b1b5fbf1d48 in QApplication::exec (this=0x7fff4f7007c0) at kernel/qapplication.cpp:2758 #42 0x0000000000440ec5 in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kdenetwork-3.5.7/./kopete/kopete/main.cpp:107 #43 0x00002b1b629078e4 in __libc_start_main () from /lib/libc.so.6 #44 0x0000000000431859 in _start ()
hello i've got always the same problem. if i want to connect with my jabber-account, it crashes. i see how it make's the tree, then it's away. my backtrace: Anwendung: Kopete (kopete), Signal SIGSEGV (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x7fb862223780 (LWP 7236)] [New Thread 0x419e5950 (LWP 7243)] [KCrash handler] #5 0x00007fb85dedc008 in memcpy () from /lib/libc.so.6 #6 0x00007fb860999b51 in KNetwork::Internal::KSocketBuffer::sendTo ( this=0xbf5490, dev=0xbf74e0, len=-1) at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3socketbuffer.cpp:256 #7 0x00007fb860989408 in KNetwork::KBufferedSocket::slotWriteActivity ( this=0xad9500) at /build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3bufferedsocket.cpp:349 #8 0x00007fb860989292 in KNetwork::KBufferedSocket::qt_metacall ( this=0xad9500, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=<value optimized out>) at /build/buildd/kde4libs-4.1.1+really4.1.1/obj-x86_64-linux-gnu/kdecore/k3bufferedsocket.moc:68 #9 0x00007fb8602f58b6 in QMetaObject::activate (sender=0xb79310, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x752) at kernel/qobject.cpp:3016 #10 0x00007fb86032efae in QSocketNotifier::activated (this=0xeaffda, _t1=30) at .moc/release-shared/moc_qsocketnotifier.cpp:81 #11 0x00007fb8602fbb5f in QSocketNotifier::event (this=0xb79310, e=0x7fff6a257e90) at kernel/qsocketnotifier.cpp:326 #12 0x00007fb85ebbfacf in QApplicationPrivate::notify_helper (this=0x6a7af0, receiver=0xb79310, e=0x7fff6a257e90) at kernel/qapplication.cpp:3800 #13 0x00007fb85ebc1c85 in QApplication::notify (this=0x7fff6a259c50, receiver=0xb79310, e=0x7fff6a257e90) at kernel/qapplication.cpp:3765 #14 0x00007fb860e77ea1 in KApplication::notify (this=0x7fff6a259c50, receiver=0xb79310, event=0x7fff6a257e90) at /build/buildd/kde4libs-4.1.1+really4.1.1/kdeui/kernel/kapplication.cpp:311 #15 0x00007fb8602e16b9 in QCoreApplication::notifyInternal ( this=0x7fff6a259c50, receiver=0xb79310, event=0x7fff6a257e90) at kernel/qcoreapplication.cpp:591 #16 0x00007fb86030a85a in socketNotifierSourceDispatch (source=0x6aad60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #17 0x00007fb85af553d4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #18 0x00007fb85af586e5 in ?? () from /usr/lib/libglib-2.0.so.0 #19 0x00007fb85af58bcb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #20 0x00007fb86030a9df in QEventDispatcherGlib::processEvents (this=0x696670, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:325 #21 0x00007fb85ec4920f in QGuiEventDispatcherGlib::processEvents ( this=0xeaffda, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #22 0x00007fb8602e0b35 in QEventLoop::processEvents ( this=<value optimized out>, flags=@0x7fff6a2580a0) at kernel/qeventloop.cpp:149 #23 0x00007fb8602e0c8b in QEventLoop::exec (this=0x7fff6a2580e0, flags=@0x7fff6a2580f0) at kernel/qeventloop.cpp:200 #24 0x00007fb8613a0df4 in KIO::NetAccess::enter_loop ( this=<value optimized out>) at /build/buildd/kde4libs-4.1.1+really4.1.1/kio/kio/netaccess.cpp:494 #25 0x00007fb8613a1136 in KIO::NetAccess::mkdirInternal (this=0x7fff6a258140, url=<value optimized out>, permissions=<value optimized out>, window=0x0) at /build/buildd/kde4libs-4.1.1+really4.1.1/kio/kio/netaccess.cpp:370 #26 0x00007fb8613a178a in KIO::NetAccess::mkdir (url=@0xdf6cb0, window=0x0, permissions=-1) at /build/buildd/kde4libs-4.1.1+really4.1.1/kio/kio/netaccess.cpp:260 #27 0x00007fb861777438 in Kopete::AvatarManager::Private::createDirectory () from /usr/lib/kde4/lib/libkopete.so.4 #28 0x00007fb86177816d in Kopete::AvatarManager::AvatarManager () from /usr/lib/kde4/lib/libkopete.so.4 #29 0x00007fb8617781d7 in Kopete::AvatarManager::self () from /usr/lib/kde4/lib/libkopete.so.4 #30 0x00007fb851c12b63 in ?? () from /usr/lib/kde4/lib/kde4/kopete_jabber.so #31 0x00007fb851c1942f in ?? () from /usr/lib/kde4/lib/kde4/kopete_jabber.so #32 0x00007fb851c19e4d in ?? () from /usr/lib/kde4/lib/kde4/kopete_jabber.so #33 0x00007fb8602f58b6 in QMetaObject::activate (sender=0xd7a580, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x752) at kernel/qobject.cpp:3016 #34 0x00007fb85195d2a0 in XMPP::Task::done () from /usr/lib/kde4/lib/libiris_kopete.so.1 #35 0x00007fb851945ee1 in XMPP::JT_VCard::take () from /usr/lib/kde4/lib/libiris_kopete.so.1 #36 0x00007fb85195d4c0 in XMPP::Task::take () from /usr/lib/kde4/lib/libiris_kopete.so.1 #37 0x00007fb85192b9a4 in XMPP::Client::distribute () from /usr/lib/kde4/lib/libiris_kopete.so.1 #38 0x00007fb85192c3be in XMPP::Client::streamReadyRead () from /usr/lib/kde4/lib/libiris_kopete.so.1 #39 0x00007fb8518ebb18 in XMPP::Client::qt_metacall () from /usr/lib/kde4/lib/libiris_kopete.so.1 #40 0x00007fb8602f58b6 in QMetaObject::activate (sender=0xc47fd0, from_signal_index=<value optimized out>, to_signal_index=6, argv=0x752) at kernel/qobject.cpp:3016 #41 0x00007fb8518ec12f in XMPP::ClientStream::qt_metacall () from /usr/lib/kde4/lib/libiris_kopete.so.1 #42 0x00007fb8602f58b6 in QMetaObject::activate (sender=0xd7bf90, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x752) at kernel/qobject.cpp:3016 #43 0x00007fb8602fbfff in QSingleShotTimer::timerEvent (this=0xd7bf90) at kernel/qtimer.cpp:300 #44 0x00007fb8602f01d5 in QObject::event (this=0xd7bf90, e=0xe83bf8) at kernel/qobject.cpp:1105 #45 0x00007fb85ebbfacf in QApplicationPrivate::notify_helper (this=0x6a7af0, receiver=0xd7bf90, e=0x7fff6a259930) at kernel/qapplication.cpp:3800 #46 0x00007fb85ebc1c85 in QApplication::notify (this=0x7fff6a259c50, receiver=0xd7bf90, e=0x7fff6a259930) at kernel/qapplication.cpp:3765 #47 0x00007fb860e77ea1 in KApplication::notify (this=0x7fff6a259c50, receiver=0xd7bf90, event=0x7fff6a259930) at /build/buildd/kde4libs-4.1.1+really4.1.1/kdeui/kernel/kapplication.cpp:311 #48 0x00007fb8602e16b9 in QCoreApplication::notifyInternal ( this=0x7fff6a259c50, receiver=0xd7bf90, event=0x7fff6a259930) at kernel/qcoreapplication.cpp:591 #49 0x00007fb86030ca0c in QTimerInfoList::activateTimers (this=0x6aae30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #50 0x00007fb86030a57d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:166 #51 0x00007fb85af553d4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #52 0x00007fb85af586e5 in ?? () from /usr/lib/libglib-2.0.so.0 #53 0x00007fb85af58bcb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #54 0x00007fb86030a9df in QEventDispatcherGlib::processEvents (this=0x696670, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:325 #55 0x00007fb85ec4920f in QGuiEventDispatcherGlib::processEvents ( this=0xeaffda, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #56 0x00007fb8602e0b35 in QEventLoop::processEvents ( this=<value optimized out>, flags=@0x7fff6a259b80) at kernel/qeventloop.cpp:149 #57 0x00007fb8602e0c8b in QEventLoop::exec (this=0x7fff6a259bc0, flags=@0x7fff6a259bd0) at kernel/qeventloop.cpp:200 #58 0x00007fb8602e2cd9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:849 #59 0x00000000004441f1 in ?? () #60 0x00007fb85de7d1c4 in __libc_start_main () from /lib/libc.so.6 #61 0x0000000000423be9 in _start () #0 0x00007fb85defcb81 in nanosleep () from /lib/libc.so.6 i use kubuntu 8.04.1 (amd64-version) with the ppa.launchpad.net-sources. i saw never a dbg-package in the adept-manager, so i hope, the backtrace is ok. all the settings shout be default. i tested also with my msn-account, this works without some problems. hope, it helps you.