| Summary: | KMail/Kontact Crash By Spell Checker | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Dirk Förster <dfoerster> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 1.6.2 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Dirk Förster
2004-11-02 10:22:55 UTC
Apparently a version mismatch. After having updated to KDE 3.3.2 Level "a", the same problem exists. Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 3274)] [KCrash handler] #5 0x40d6490a in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #6 0x410b3183 in QComboBox::activated () from /usr/lib/qt3/lib/libqt-mt.so.3 #7 0x40e03d01 in QComboBox::internalActivate () from /usr/lib/qt3/lib/libqt-mt.so.3 #8 0x410b2ff5 in QComboBox::qt_invoke () from /usr/lib/qt3/lib/libqt-mt.so.3 #9 0x40d6467e in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #10 0x40d64cad in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #11 0x410bbfb1 in QListBox::selected () from /usr/lib/qt3/lib/libqt-mt.so.3 #12 0x40e3daf3 in QListBox::mouseDoubleClickEvent () from /usr/lib/qt3/lib/libqt-mt.so.3 #13 0x40d9a104 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #14 0x40d0293f in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #15 0x40d04ca8 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0x409cc0ce in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #17 0x40e0163f in QComboBox::eventFilter () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0x08693f50 in ?? () #19 0xbfffe600 in ?? () #20 0x00000001 in ?? () #21 0x00000001 in ?? () #22 0x086948c8 in ?? () #23 0xbfffe608 in ?? () #24 0x40d9a072 in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #25 0x080737e0 in ?? () #26 0x080e2888 in ?? () #27 0x00000000 in ?? () #28 0x080e2618 in ?? () #29 0x081041b8 in ?? () #30 0x08103bf8 in ?? () #31 0x08129130 in ?? () #32 0x00000000 in ?? () #33 0x00000000 in ?? () #34 0x00000001 in ?? () #35 0xbffff354 in ?? () #36 0x416a0a00 in __libc_tsd_MALLOC_data () from /lib/libc.so.6 #37 0x00000000 in ?? () #38 0x08118318 in ?? () #39 0x080f7148 in ?? () #40 0x080f1eb0 in ?? () #41 0x08067300 in vtable for QDragMoveEvent () #42 0x08064b2c in vtable for KontactApp () #43 0x080fb938 in ?? () #44 0x080eb3b0 in ?? () #45 0x0810e768 in ?? () #46 0x411aefa8 in vtable for QCString () from /usr/lib/qt3/lib/libqt-mt.so.3 #47 0x08074a58 in ?? () #48 0xbffff2b0 in ?? () #49 0x080f7948 in ?? () #50 0x08076778 in ?? () #51 0x00000133 in ?? () #52 0x000000ff in ?? () #53 0x08067322 in vtable for QDragMoveEvent () #54 0x00000000 in ?? () #55 0x0806c108 in ?? () #56 0x00000001 in ?? () #57 0x411a0a08 in vtable for QPixmap () from /usr/lib/qt3/lib/libqt-mt.so.3 #58 0x03600014 in ?? () #59 0x0810bf48 in ?? () #60 0x00000002 in ?? () #61 0x00000000 in ?? () #62 0x08129610 in ?? () #63 0x411a0a08 in vtable for QPixmap () from /usr/lib/qt3/lib/libqt-mt.so.3 #64 0x03600019 in ?? () #65 0x0812c108 in ?? () #66 0x00000002 in ?? () #67 0x00000000 in ?? () #68 0x080eb238 in ?? () #69 0x0806c108 in ?? () #70 0x0806c108 in ?? () #71 0x41428d01 in __pthread_unlock () from /lib/libpthread.so.0 Am Sonntag, 2. Januar 2005 12:21 schrieb Till Adam: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=92562 > adam kde org changed: > > What |Removed |Added > --------------------------------------------------------------------------- >- Status|UNCONFIRMED |RESOLVED > Resolution| |INVALID > > > > ------- Additional Comments From adam kde org 2005-01-02 12:21 ------- > Apparently a version mismatch. Do you have the dictionary header active in the composer (view->Dictionary)? Reporter reports by private mail:
>No, I did not. Now I have. There are no more crashes. Thank you!
But it does not actually solve the bug. I'll close it as a dup to the other one anyhow.
|