Version: (using KDE KDE 3.5.7) Installed from: Debian testing/unstable Packages OS: Irix I closed kopete using Ctrl-Q and then immediately after kopete closed, kontact crashed with SIGSEGV and this backtrace: Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1243085104 (LWP 5376)] [New Thread -1301107824 (LWP 5396)] [New Thread -1288602736 (LWP 5380)] [New Thread -1280210032 (LWP 5379)] [New Thread -1271817328 (LWP 5378)] [New Thread -1263424624 (LWP 5377)] [KCrash handler] #6 0xb7737135 in ?? () from /lib/i686/cmov/libc.so.6 #7 0xb1cdaa18 in ?? () #8 0xbfd87668 in ?? () #9 0xb773ad0e in malloc () from /lib/i686/cmov/libc.so.6 #10 0xb7738c2f in ?? () from /lib/i686/cmov/libc.so.6 #11 0xb7928ff4 in ?? () from /usr/lib/libstdc++.so.6 #12 0xb01816b8 in ?? () #13 0x00000002 in ?? () #14 0xb77386f1 in ?? () from /lib/i686/cmov/libc.so.6 #15 0xb7928ff4 in ?? () from /usr/lib/libstdc++.so.6 #16 0xb01816b8 in ?? () #17 0xb735a78a in ?? () from /usr/lib/libqt-mt.so.3 #18 0xbfd876e8 in ?? () #19 0x00010208 in ?? () #20 0x00010208 in ?? () #21 0xb77f8f00 in ?? () from /lib/i686/cmov/libc.so.6 #22 0xb77386f1 in ?? () from /lib/i686/cmov/libc.so.6 #23 0x00000010 in ?? () #24 0xb780fff4 in ?? () from /lib/i686/cmov/libc.so.6 #25 0xb1c00010 in ?? () #26 0xafc55928 in ?? () #27 0xbfd87708 in ?? () #28 0xb773ad0e in malloc () from /lib/i686/cmov/libc.so.6 #29 0xb773c530 in free () from /lib/i686/cmov/libc.so.6 #30 0xb6f49fb6 in QImage::freeBits (this=0x8b08168) at kernel/qimage.cpp:1364 #31 0xb6f4a18f in QImage::reset (this=0x8b08168) at kernel/qimage.cpp:958 #32 0xb6f4db7e in ~QImage (this=0x8b08168) at kernel/qimage.cpp:568 #33 0xb6f70565 in QMimeSource::clearCache (this=0x862f560) at kernel/qmime.cpp:96 #34 0xb6f715fc in ~QMimeSource (this=0x862f560) at kernel/qmime.cpp:113 #35 0xb6f288ee in ~QDragObject (this=0x862f538) at kernel/qdragobject.cpp:335 #36 0xb6f28c34 in ~QImageDrag (this=0x862f538) at kernel/qdragobject.cpp:1040 #37 0xb6f70303 in QMimeSourceFactory::setData (this=0x80b89c8, abs_name=@0xbfd8794c, data=0xb01816e0) at kernel/qmime.cpp:537 #38 0xb6f704b3 in QMimeSourceFactory::setPixmap (this=0x80b89c8, abs_name=@0xbfd8794c, pixmap=@0xbfd87914) at kernel/qmime.cpp:523 #39 0xb7ef03da in KPIM::AddresseeView::updateView (this=0x8a8e9d8) at /tmp/buildd/kdepim-3.5.7/./libkdepim/addresseeview.cpp:564 #40 0xb7ef052d in KPIM::AddresseeView::slotPresenceInfoExpired ( this=0x8a8e9d8) at /tmp/buildd/kdepim-3.5.7/./libkdepim/addresseeview.cpp:735 #41 0xb7ef06d9 in KPIM::AddresseeView::qt_invoke (this=0x8a8e9d8, _id=163, _o=0xbfd87a5c) at ./addresseeview.moc:188 #42 0xb6f7ce70 in QObject::activate_signal (this=0x84d1218, clist=0x8595f30, o=0xbfd87a5c) at kernel/qobject.cpp:2380 #43 0xb6f7d7e8 in QObject::activate_signal (this=0x84d1218, signal=3) at kernel/qobject.cpp:2325 #44 0xb60ead1c in KIMProxy::sigPresenceInfoExpired (this=0x84d1218) at ./kimproxy.moc:107 #45 0xb60ec2e6 in KIMProxy::unregisteredFromDCOP (this=0x84d1218, appId=@0xbfd87c6c) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./interfaces/kimproxy/library/kimproxy.cpp:324 #46 0xb60ec716 in KIMProxy::qt_invoke (this=0x84d1218, _id=3, _o=0xbfd87b84) at ./kimproxy.moc:114 #47 0xb6f7cd43 in QObject::activate_signal (this=0x8079820, clist=0x84d0f98, o=0xbfd87b84) at kernel/qobject.cpp:2356 #48 0xb7468921 in DCOPClient::applicationRemoved (this=0x8079820, t0=@0xbfd87c6c) at ./dcopclient.moc:143 #49 0xb746ff69 in DCOPClient::receive (this=0x8079820, objId=@0xbfd87dcc, fun=@0xbfd87dc4, data=@0xbfd87dbc, replyType=@0xbfd87db4, replyData=@0xbfd87dac) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./dcop/dcopclient.cpp:1591 #50 0xb747178b in DCOPProcessInternal (d=0x8079850, opcode=1, key=1, dataReceived=@0xbfd87e88, canPost=true) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./dcop/dcopclient.cpp:518 #51 0xb7471eb5 in DCOPProcessMessage (iceConn=0x807ab70, clientObject=0x8079850, opcode=1, length=73, replyWait=0x0, replyWaitRet=0xbfd87ef4) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./dcop/dcopclient.cpp:430 #52 0xb7481f40 in KDE_IceProcessMessages (iceConn=0x807ab70, replyWait=0x0, replyReadyRet=0x0) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./dcop/KDE-ICE/process.c:326 #53 0xb7468573 in DCOPClient::processSocketData (this=0x8079820, fd=3) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./dcop/dcopclient.cpp:2009 #54 0xb7471ab9 in DCOPClient::qt_invoke (this=0x8079820, _id=2, _o=0xbfd88098) at ./dcopclient.moc:176 #55 0xb6f7cd43 in QObject::activate_signal (this=0x80b5660, clist=0x80b7140, o=0xbfd88098) at kernel/qobject.cpp:2356 #56 0xb6f7d65a in QObject::activate_signal (this=0x80b5660, signal=2, param=3) at kernel/qobject.cpp:2449 #57 0xb730a43f in QSocketNotifier::activated (this=0x80b5660, t0=3) at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85 #58 0xb6f9f9d6 in QSocketNotifier::event (this=0x80b5660, e=0xbfd883f0) at kernel/qsocketnotifier.cpp:258 #59 0xb6f14500 in QApplication::internalNotify (this=0xbfd88678, receiver=0x80b5660, e=0xbfd883f0) at kernel/qapplication.cpp:2635 #60 0xb6f1632f in QApplication::notify (this=0xbfd88678, receiver=0x80b5660, e=0xbfd883f0) at kernel/qapplication.cpp:2358 #61 0xb7631142 in KApplication::notify (this=0xbfd88678, receiver=0x80b5660, event=0xbfd883f0) at /tmp/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kapplication.cpp:550 #62 0xb6ea75b5 in QApplication::sendEvent (receiver=0x80b5660, event=0xbfd883f0) at ../include/qapplication.h:520 #63 0xb6f06839 in QEventLoop::activateSocketNotifiers (this=0x808f770) at kernel/qeventloop_unix.cpp:578 #64 0xb6ebba15 in QEventLoop::processEvents (this=0x808f770, flags=4) at kernel/qeventloop_x11.cpp:383 #65 0xb6f2ec06 in QEventLoop::enterLoop (this=0x808f770) at kernel/qeventloop.cpp:198 #66 0xb6f2ea16 in QEventLoop::exec (this=0x808f770) at kernel/qeventloop.cpp:145 #67 0xb6f160a9 in QApplication::exec (this=0xbfd88678) at kernel/qapplication.cpp:2758 #68 0x08061d69 in main (argc=) at /tmp/buildd/kdepim-3.5.7/./kontact/src/main.cpp:163 #69 0xb76e6ebc in __libc_start_main () from /lib/i686/cmov/libc.so.6 #70 0x08059101 in _start ()
I can not reproduce. Can you try to reproduce that bug and post the steps to reproduce here? What part of Kontact was shown at the time of the crash? The mail part? What kind of mail was shown in the message viewer at the time of the crash? Was the sender also on your Kopete contact list? Did the mail have attached vcards? Were you using drag&drop at the time of the crash? Are you really using IRIX?
Indeed I can't remember most of parameters of the apps when the crash happens. Since I didn't expect a crash I don't realise of the details. However I have the impression that I was on the mail part, but looking at the BT, maybe I was at the addressbook. I don't think I was seeing a mail with a vcard attached, yet I have some mails in the inbox with that. What I'm sure is that the sender is not on my kopete contact list. No drag&drop I were aware of(maybe accidental) but I used Ctrl-Q to quit, so not likely. Where did you got that I'm using IRIX?. I'm using GNU/Linux actually. Maybe I should wait for the crash to be repeatable before I report it, in this case we could mark this as invalid waiting for it not to be reproduced.
>Where did you got that I'm using IRIX?. I'm using GNU/Linux actually. You selected IRIX somewhere. See the top of this page. I've changed it now. >Maybe I should wait for the crash to be repeatable before I report it, in this case we could mark this as invalid waiting for it not to be reproduced. No need to mark this as invalid, it will stay as UNCONFIRMED until some of the developers are able to reproduce this.
that is hapennig to me too!!!! Aplicación: Kopete (kopete), señal SIGABRT (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (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 0xb59626c0 (LWP 6617)] [KCrash handler] #6 0xb80b3430 in __kernel_vsyscall () #7 0xb645d880 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb645f248 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb74e1795 in qt_message_output () from /usr/lib/libQtCore.so.4 #10 0xb74e1872 in qFatal () from /usr/lib/libQtCore.so.4 #11 0xb80047fc in ?? () from /usr/lib/libkopete.so.4 #12 0xb800695b in Kopete::PluginManager::slotPluginDestroyed () from /usr/lib/libkopete.so.4 #13 0xb800a15f in Kopete::PluginManager::qt_metacall () from /usr/lib/libkopete.so.4 #14 0xb75eea60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #15 0xb75eee60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #16 0xb75eeeeb in QObject::destroyed () from /usr/lib/libQtCore.so.4 #17 0xb75f09a9 in QObject::~QObject () from /usr/lib/libQtCore.so.4 #18 0xb8003e2d in Kopete::Plugin::~Plugin () from /usr/lib/libkopete.so.4 #19 0xb800f8a2 in Kopete::Protocol::~Protocol () from /usr/lib/libkopete.so.4 #20 0xb347020a in ?? () from /usr/lib/libkopete_msn_shared.so.4 #21 0xb800b742 in ?? () from /usr/lib/libkopete.so.4 #22 0xb80045aa in ?? () from /usr/lib/libkopete.so.4 #23 0xb7f806bb in ?? () from /usr/lib/libkopete.so.4 #24 0xb6460d69 in exit () from /lib/tls/i686/cmov/libc.so.6 #25 0xb644868d in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #26 0x08063d61 in _start () #0 0xb80b3430 in __kernel_vsyscall ()
@Fremir Hernandez Diaz: Your backtrace is unrelated to the problem discussed here. What you experienced most likely was bug #172011
Someone can confirm this using KDE 4.2 beta2? I'm unable to reproduce it.
It seems not reproducible on KDE4. Someone confirm it?
I haven't seen this bug for quite some time, and I'm unable to reproduce. I'm recently on kde4, not much experience with it yet, but I'd say this isn't applicable on kde4 since dcop it's gone. HTH,
(In reply to comment #8) > I haven't seen this bug for quite some time, and I'm unable to reproduce. I'm > recently on kde4, not much experience with it yet, but I'd say this isn't > applicable on kde4 since dcop it's gone. > > HTH, ok, Closing