| Summary: | Crash after receiving pending message | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Nicolas Girard <nicolas.girard> |
| Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED REMIND | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | 0.9.1 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
> Amarok crashes.
You mean Kopete ?
Anyway i can't reproduce the bug. Can you compile Kopete with debug symbols and send the backtrace again?
Oops, of course I meant Kopete... sorry for the misunderstanding. These days I've noticed the following: once connected, two popup windows inform me about a pending message ; and if I wait a few seconds and click on the bubble-shaped one, instead of clicking immediately, I don't seem to experience crashes. What do you think about it ? On Sunday 28 November 2004 21:57, Nicolas Girard wrote: > These days I've noticed the following: once connected, two popup windows > inform me about a pending message ; and if I wait a few seconds and click > on the bubble-shaped one, instead of clicking immediately, I don't seem to > experience crashes. > > What do you think about it ? That we can't do anything about it unless we can reproduce it or we can get a more useful backtrace. It's probably a race condition somewhere. Please provide more information. Useful things to tell us include which protocol this is happening with, whether it happens every time or only occasionally, and anything peculiar about the contact the message causing the crash is from. If you could recompile kopete and pass --enable-debug=full to the configure script, you'd get better backtraces (and they'd be better still if you recompiled kdelibs with --enable-debug=full too :) ). it's been about 30 days and i can't reproduce it either. since i'm rather impatient, please reopen if you can provide a backtrace after compiling kopete with --enable-debug=full and we'll investigate further. |
Version: 0.9.1 (using KDE 3.3.1 (CVS >= 20041110), Mandrake Linux Cooker i586 - Cooker) Compiler: gcc version 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk) OS: Linux (i686) release 2.6.8.1-10mdk This defects tends to happen quite systematically to me in the following context: My mother and I have a Jabber account on the same server ; she's used to send me a message before I'm available to read it. When I launch Kopete, I get connected to the jabber server ; then a popup informs me that I'm connected ; and finally I get another popup that informs me about my mom's message. But when I click on the popup's "read" button ("Lire" in French), Amarok crashes. Here follows the backtrace: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1106774656 (LWP 13716)] [New Thread 1128962992 (LWP 14002)] [Thread debugging using libthread_db enabled] [New Thread 1106774656 (LWP 13716)] [New Thread 1128962992 (LWP 14002)] [Thread debugging using libthread_db enabled] [New Thread 1106774656 (LWP 13716)] [New Thread 1128962992 (LWP 14002)] [New Thread 1120570288 (LWP 13998)] [KCrash handler] #7 0x400b4ecb in KopeteMessage::KopeteMessage () from /usr/lib/libkopete.so.1 #8 0x40122ccc in KopeteEvent::message () from /usr/lib/libkopete.so.1 #9 0x422245f7 in KopeteViewManager::slotViewActivated () from /usr/lib/kde3/kopete_chatwindow.so #10 0x42234ec8 in KopeteViewManager::qt_invoke () from /usr/lib/kde3/kopete_chatwindow.so #11 0x414795ad in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #12 0x08449f50 in ?? () #13 0x083d5250 in ?? () #14 0x00000000 in ?? () #15 0x083056d0 in ?? () #16 0x083d5438 in ?? () #17 0x083d5508 in ?? () #18 0xbfffeb38 in ?? () #19 0x42218217 in KopeteChatWindow::setStatus () from /usr/lib/kde3/kopete_chatwindow.so