Version: 0.8.0 (using KDE 3.2.0 RC1, Gentoo) Compiler: gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice) OS: Linux (i686) release 2.4.20-gentoo-r8 I just came back home and Kopete was crashed. It was running idle (in away mode) for some hours, ICQ, Jabber, AIM and Yahoo! accounts logged in. The backtrace: (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)...[New Thread 16384 (LWP 16577)] [New Thread 32769 (LWP 11925)] 0x419bf40b in waitpid () from /lib/libpthread.so.0 #0 0x419bf40b in waitpid () from /lib/libpthread.so.0 #1 0x41109c8c in __JCR_LIST__ () from /usr/kde/cvs/lib/libkdecore.so.4 #2 0x419be1b3 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called> #4 0x08066bd9 in QGArray::data() const () #5 0x40ff8d62 in operator<(KEntryKey const&, KEntryKey const&) () from /usr/kde/cvs/lib/libkdecore.so.4 #6 0x40ff7b81 in QMapPrivate<KEntryKey, KEntry>::find(KEntryKey const&) const () from /usr/kde/cvs/lib/libkdecore.so.4 #7 0x40ff7432 in QMap<KEntryKey, KEntry>::find(KEntryKey const&) const () from /usr/kde/cvs/lib/libkdecore.so.4 #8 0x40ff65a9 in KConfig::lookupData(KEntryKey const&) const () from /usr/kde/cvs/lib/libkdecore.so.4 #9 0x40febfd3 in KConfigBase::readEntry(char const*, QString const&) const () from /usr/kde/cvs/lib/libkdecore.so.4 #10 0x40febed4 in KConfigBase::readEntry(QString const&, QString const&) const () from /usr/kde/cvs/lib/libkdecore.so.4 #11 0x4101d42b in KIconEffect::init() () from /usr/kde/cvs/lib/libkdecore.so.4 #12 0x4101cce3 in KIconEffect::KIconEffect() () from /usr/kde/cvs/lib/libkdecore.so.4 #13 0x40096d2c in KopeteOnlineStatus::renderIcon(QString const&, int, QColor, bool) const () from /usr/kde/cvs/lib/libkopete.so.1 #14 0x40096aff in KopeteOnlineStatus::cacheLookup(QString const&, int, QColor, bool) const () from /usr/kde/cvs/lib/libkopete.so.1 #15 0x40096797 in KopeteOnlineStatus::iconFor(KopeteContact const*, int) const () from /usr/kde/cvs/lib/libkopete.so.1 #16 0x0808af5a in KopeteMetaContactLVI::paintCell(QPainter*, QColorGroup const&, int, int, int) () #17 0x414f5e6b in QListView::drawContentsOffset(QPainter*, int, int, int, int, int, int) () from /usr/qt/3/lib/libqt-mt.so.3 #18 0x41529cfa in QScrollView::viewportPaintEvent(QPaintEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #19 0x40da1196 in KListView::viewportPaintEvent(QPaintEvent*) () from /usr/kde/cvs/lib/libkdeui.so.4 #20 0x41529733 in QScrollView::eventFilter(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #21 0x414f8698 in QListView::eventFilter(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #22 0x4141876e in QObject::activate_filters(QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #23 0x41418691 in QObject::event(QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #24 0x4144fabf in QWidget::event(QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #25 0x413c0075 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #26 0x413bf465 in QApplication::notify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #27 0x40fcbdd5 in KApplication::notify(QObject*, QEvent*) () from /usr/kde/cvs/lib/libkdecore.so.4 #28 0x4138b4a4 in QWidget::repaint(int, int, int, int, bool) () from /usr/qt/3/lib/libqt-mt.so.3 #29 0x41450d8b in QWidget::repaint(bool) () from /usr/qt/3/lib/libqt-mt.so.3 #30 0x414f77b4 in QListView::updateContents() () from /usr/qt/3/lib/libqt-mt.so.3 #31 0x41758747 in QListView::qt_invoke(int, QUObject*) () from /usr/qt/3/lib/libqt-mt.so.3 #32 0x40da4773 in KListView::qt_invoke(int, QUObject*) () from /usr/kde/cvs/lib/libkdeui.so.4 #33 0x08082843 in KopeteContactListView::staticMetaObject() () #34 0x4141ae40 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/qt/3/lib/libqt-mt.so.3 #35 0x4141ac74 in QObject::activate_signal(int) () from /usr/qt/3/lib/libqt-mt.so.3 #36 0x41747e3b in QTimer::timeout() () from /usr/qt/3/lib/libqt-mt.so.3 #37 0x4143c212 in QTimer::event(QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #38 0x413c0075 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #39 0x413bf465 in QApplication::notify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #40 0x40fcbdd5 in KApplication::notify(QObject*, QEvent*) () from /usr/kde/cvs/lib/libkdecore.so.4 #41 0x413af73d in QEventLoop::activateTimers() () from /usr/qt/3/lib/libqt-mt.so.3 #42 0x4136be9a in QEventLoop::processEvents(unsigned) () from /usr/qt/3/lib/libqt-mt.so.3 #43 0x413d1e76 in QEventLoop::enterLoop() () from /usr/qt/3/lib/libqt-mt.so.3 #44 0x413d1d18 in QEventLoop::exec() () from /usr/qt/3/lib/libqt-mt.so.3 #45 0x413c02c1 in QApplication::exec() () from /usr/qt/3/lib/libqt-mt.so.3 #46 0x0806516b in KIconLoader::unknown() () #47 0x41b2fdcc in __libc_start_main () from /lib/libc.so.6
Kopete just did it again, no backtrace this time. It just went away while I sat in front of my screen. I think some ICQ users of whom I still had chat windows open went online.
Sorry but that still does not give us any hint. Try running it in valgrind and make sure you compiled at least kopete with --enable-debug=full and no hyperspeed optimizations.
And btw, if you look into your backtrace you can clearly see that the last few calls (#12 up to #1) are all the way kdelibs and not Kopete code. Maybe try changing your iconset, disable icon effects and/or compile kdelibs with debug as well. Needless to say I have never seen such a crash. Also my Kopete is now running for about 8 hours without a hitch.
My whole KDE is compile with full debug and just -O2 optimizations. My Inconset is Crystal SVG. So nothing weird here. And I don't even know what an IconEffect is ;-) I'm not even sure that the crash a few minutes ago was the same as Dr. Konqi stayed quiet. Kopete just closed itself. Nor that this is related to ICQ in any way -- ICQ is the only protocol I was chatting on, but I'm also logged in to two Jabber accounts and AIM. As this crash or whatever it is happens just once in a blue moon, I don't really want to keep Kopete running under valgrind all the time...
Subject: Re: [Kopete-devel] Crash while running idle On Monday 02 February 2004 21:47, Malte S.Stretz wrote: > As this crash or whatever it is happens just once in a blue moon, I don't > really want to keep Kopete running under valgrind all the time... What *might* help is running Kopete in gdb, which doesn't slow down, but occasionally produces better backtraces than DrKonqi. Your odds are small, but it's the best I can think of.
Ok, it just happened again. A different backtrace this time, but you know what? I had a chat window open to a friend, ICQ contact. And he went offline. I'll keep Kopete running under valgrind now :) (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)...[New Thread 16384 (LWP 7402)] [New Thread 32769 (LWP 9988)] 0x419bf40b in waitpid () from /lib/libpthread.so.0 #0 0x419bf40b in waitpid () from /lib/libpthread.so.0 #1 0x41109c8c in __JCR_LIST__ () from /usr/kde/cvs/lib/libkdecore.so.4 #2 0x419be1b3 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called> #4 0x4141ae0e in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/qt/3/lib/libqt-mt.so.3 #5 0x4141ac74 in QObject::activate_signal(int) () from /usr/qt/3/lib/libqt-mt.so.3 #6 0x41747e3b in QTimer::timeout() () from /usr/qt/3/lib/libqt-mt.so.3 #7 0x4143c212 in QTimer::event(QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #8 0x413c0075 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #9 0x413bf465 in QApplication::notify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #10 0x40fcbdd5 in KApplication::notify(QObject*, QEvent*) () from /usr/kde/cvs/lib/libkdecore.so.4 #11 0x413af73d in QEventLoop::activateTimers() () from /usr/qt/3/lib/libqt-mt.so.3 #12 0x4136be9a in QEventLoop::processEvents(unsigned) () from /usr/qt/3/lib/libqt-mt.so.3 #13 0x413d1e76 in QEventLoop::enterLoop() () from /usr/qt/3/lib/libqt-mt.so.3 #14 0x413d1d18 in QEventLoop::exec() () from /usr/qt/3/lib/libqt-mt.so.3 #15 0x413c02c1 in QApplication::exec() () from /usr/qt/3/lib/libqt-mt.so.3 #16 0x0806516b in KIconLoader::unknown() () #17 0x41b2fdcc in __libc_start_main () from /lib/libc.so.6
And that backtrace is completely useless because all it says is "qt is idling in its event loop".
Stefan, I *know* that backtrace isn't very useful, but it's at least a data point, isn't it? I hope that I'll find out why Kopete does this to me, until then I can just report "hey, it did it again" and try to find any pattern in the behaviour.
> but it's at least a data point, isn't it? Unfortunately no, the qt event loop is executed that often, you cannot say "it happens between function XYZ and signal ABC being emitted". Also the last backtrace contains no reference to kopete so there's not even a hint where things started to go wrong inside of kopete. So far all we have is two backtraces and both of them don't show a crash in kopete but rather outside of kopete code.
Should we reassign this bug to kconfig? At least that's the last kde part the backtrace ends in.
For what it's worth, I just tested the theory of ICQ contact chat window open and ICQ contact goes offline. No crash in 0.8.0.
I haven't encountered this one again for some time now, maybe it got fixed in between. Feel free to close it to get the bug count down...
okie dokie. Thanks Malte. :) Be sure to reopen if you can reliably reproduce.
*** Bug 75805 has been marked as a duplicate of this bug. ***