| Summary: | kmail composer crashes when closing (reproducible) | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Gilles Schintgen <gilles> |
| Component: | tdepim | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | acinonyx, bugwatch, darrella, panamajo, vizzy |
| Priority: | P4 | ||
| Version: | 3.5.10 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Gilles Schintgen
2009-11-15 07:29:29 CST
I come to this website to report this exact Kmail bug. At first, I suspected something was corrupted in my Kmail setttings/mail folder after transferring it from Kubuntu 8.04. But after numerous tries I finally went to try Live CD of this Karmic KDE3 distribution and this bug can be re-produces on Live CD as well. Just start Kmail, compose new message and hit window close or send. The crash seem to occur on 'new message' window close. Can someone install the kdepim-dbg package (the debugging symbols) and regenerate the backtrace? Thanks! (In reply to comment #2) > Can someone install the kdepim-dbg package (the debugging symbols) and > regenerate the backtrace? > > Thanks! I can reproduce it both on x86 and AMD64. Here is the backtrace with debug symbols: [Thread debugging using libthread_db enabled] [New Thread 0x7fca20628910 (LWP 25407)] [New Thread 0x7fca20e29910 (LWP 25406)] [New Thread 0x7fca2162a910 (LWP 25405)] [New Thread 0x7fca21e2b910 (LWP 25404)] [KCrash handler] #5 0x00007fca284e32f7 in ~DCOPObject (this=0x2c31fc8, __in_chrg=<value optimised out>) at /build/buildd/kdelibs-kde3-3.5.10/./dcop/dcopobject.cpp:81 #6 0x00007fca2e5ff946 in ~KMComposeWin (this=0x2c31940, __in_chrg=<value optimised out>, __vtt_parm=<value optimised out>) at /build/buildd/kdepim-kde3-3.5.10/./kmail/kmcomposewin.cpp:490 #7 0x00007fca2773513a in QObject::event (this=0x2c31940, e=0x2c971d0) at kernel/qobject.cpp:753 #8 0x00007fca27768d93 in QWidget::event (this=0x2c31fc8, e=0x0) at kernel/qwidget.cpp:4681 #9 0x00007fca276d6785 in QApplication::internalNotify ( this=<value optimised out>, receiver=0x2c31940, e=0x2c971d0) at kernel/qapplication.cpp:2638 #10 0x00007fca276d752e in QApplication::notify (this=0x7fffd594cbe0, receiver=0x2c31940, e=0x2c971d0) at kernel/qapplication.cpp:2526 #11 0x00007fca288d4a64 in KApplication::notify (this=0x7fffd594cbe0, receiver=0x2c31940, event=0x2c971d0) at /build/buildd/kdelibs-kde3-3.5.10/./kdecore/kapplication.cpp:550 #12 0x00007fca276d8483 in QApplication::sendEvent (receiver=0x0, event_type=<value optimised out>) at kernel/qapplication.h:523 #13 QApplication::sendPostedEvents (receiver=0x0, event_type=<value optimised out>) at kernel/qapplication.cpp:3302 #14 0x00007fca27687495 in QEventLoop::processEvents (this=0x1d62ff0, flags=0) at kernel/qeventloop_x11.cpp:205 #15 0x00007fca276ed5c1 in QEventLoop::enterLoop (this=0x1d62ff0) at kernel/qeventloop.cpp:201 #16 0x00007fca276ed472 in QEventLoop::exec (this=0x2c31fc8) at kernel/qeventloop.cpp:148 #17 0x0000000000402f13 in main (argc=<value optimised out>, argv=0x7fffd594cea8) at /build/buildd/kdepim-kde3-3.5.10/./kmail/main.cpp:110 Current language: auto The current source language is "auto; currently c". STATUS UPDATE This bug has been traced at length to a regression in gcc, specifically in the interaction of the Kmail KMCompiserWin class and gcc4.4. Compilation under gcc4.3, with no other changes, results in a working, stable Kmail program. I will simply recompile with gcc4.3 on the PPA, as there is no reason to move to 4.4 in this instance. Hopefully with time gcc4 will stabilize and I will be able to recompile against it for Lucid. Fix uploaded in kdepim-kde3 4:3.5.10-0ubuntu4. Thanks for reporting! |