Bug 256983 - kmail crashes after sending an email
Summary: kmail crashes after sending an email
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.5
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-15 15:55 UTC by Christian Herzberg
Modified: 2012-08-19 10:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Herzberg 2010-11-15 15:55:17 UTC
Application: kmail (1.13.5)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.36-0.slh.3-aptosid-686 i686
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
Hi, 

I wrote a Mail but was away before finishing it for several hours. I saved it to the draft-folder (kmail moved the mail to the correct IMAP-Folder) and I reopen it afterwards, finished the mail and send it. After a few minutes away from the  desktop I realized the crash dialog.

Restarting kmail with the button in crash-dialog didn't reopen anything visible. Starting kmail again leads to a message: KMail seems still running on another Desktop. Multiple runs could lead to lost E-Mails. You should only start kmail, if you are sure it isn't running yet. (translated from german massage.)


There are some strange kdm/xserver crashes in the past few day. The memory is allright, but maybe this is related ???

--- Bugtrace for kdm-crash: ---
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80adffb]
1: /usr/bin/X (0x8048000+0x5aca5) [0x80a2ca5]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb777b40c]
Segmentation fault at address (nil)

Fatal server error:
Caught signal 11 (Segmentation fault). Server aborting
--- ENd Bugtrace for kdm-crash ---

Thanks for all efforts
Chrisch






 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[KCrash Handler]
#6  QWidget::window (this=0xa64df38) at kernel/qwidget.cpp:4056
#7  0xb5dbe040 in QWidgetPrivate::paintOnScreen (this=0xa64e168) at kernel/qwidget.cpp:2032
#8  0xb5dcd728 in QWidgetPrivate::drawWidget (this=0xa64e168, pdev=0xa55eecc, rgn=..., offset=..., flags=<value optimized out>, sharedPainter=0x0, backingStore=0xa568538) at kernel/qwidget.cpp:5316
#9  0xb5dce7b5 in QWidgetPrivate::paintSiblingsRecursive (this=0xa592270, pdev=0xa55eecc, siblings=..., index=3, rgn=..., offset=..., flags=4, sharedPainter=0x0, backingStore=0xa568538) at kernel/qwidget.cpp:5476
#10 0xb5dcd6c5 in QWidgetPrivate::drawWidget (this=0xa592270, pdev=0xa55eecc, rgn=..., offset=..., flags=<value optimized out>, sharedPainter=0x0, backingStore=0xa568538) at kernel/qwidget.cpp:5412
#11 0xb5dce7b5 in QWidgetPrivate::paintSiblingsRecursive (this=0xa1a6170, pdev=0xa55eecc, siblings=..., index=27, rgn=..., offset=..., flags=4, sharedPainter=0x0, backingStore=0xa568538) at kernel/qwidget.cpp:5476
#12 0xb5dcd6c5 in QWidgetPrivate::drawWidget (this=0xa1a6170, pdev=0xa55eecc, rgn=..., offset=..., flags=<value optimized out>, sharedPainter=0x0, backingStore=0xa568538) at kernel/qwidget.cpp:5412
#13 0xb5fa35d4 in QWidgetBackingStore::sync (this=0xa568538) at painting/qbackingstore.cpp:1300
#14 0xb5dbe173 in QWidgetPrivate::syncBackingStore (this=0xa1a6170) at kernel/qwidget.cpp:1688
#15 0xb5dc4e46 in QWidget::event (this=0xa3714b0, event=0xbfcafdc4) at kernel/qwidget.cpp:8337
#16 0xb61dd707 in QMainWindow::event (this=0xa3714b0, event=0xbfcafdc4) at widgets/qmainwindow.cpp:1414
#17 0xb7784d64 in KMainWindow::event (this=0xa3714b0, ev=0xbfcafdc4) at ../../kdeui/widgets/kmainwindow.cpp:1103
#18 0xb77ccb2f in KXmlGuiWindow::event (this=0xa3714b0, ev=0xbfcafdc4) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:131
#19 0xb5d665cc in QApplicationPrivate::notify_helper (this=0x9fd1290, receiver=0xa3714b0, e=0xbfcafdc4) at kernel/qapplication.cpp:4302
#20 0xb5d6d1f9 in QApplication::notify (this=0xbfcb08c0, receiver=0xa3714b0, e=0xbfcafdc4) at kernel/qapplication.cpp:4267
#21 0xb7693c5a in KApplication::notify (this=0xbfcb08c0, receiver=0xa3714b0, event=0xbfcafdc4) at ../../kdeui/kernel/kapplication.cpp:302
#22 0xb681d4cb in QCoreApplication::notifyInternal (this=0xbfcb08c0, receiver=0xa3714b0, event=0xbfcafdc4) at kernel/qcoreapplication.cpp:726
#23 0xb5fa0607 in sendEvent (widget=0xa3714b0, updateImmediately=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#24 sendUpdateRequest (widget=0xa3714b0, updateImmediately=<value optimized out>) at painting/qbackingstore.cpp:507
#25 0xb5fa3ec1 in QWidgetBackingStore::markDirty (this=0xa568538, rect=..., widget=0xa6a8d48, updateImmediately=168, invalidateBuffer=false) at painting/qbackingstore.cpp:659
#26 0xb5dc0689 in QWidget::repaint (this=0xa6a8d48, rect=...) at kernel/qwidget.cpp:10080
#27 0xb5dc079c in QWidget::repaint (this=0xa6a8d48) at kernel/qwidget.cpp:10036
#28 0xb62170f0 in QProgressBar::setValue (this=0xa6a8d48, value=1225) at widgets/qprogressbar.cpp:321
#29 0xb23b8477 in Oxygen::ProgressBarEngine::timerEvent (this=0xa07d470, event=0xbfcb04b0) at ../../../kstyles/oxygen/animations/oxygenprogressbarengine.cpp:100
#30 0xb682dc54 in QObject::event (this=0xa07d470, e=0xa00faa8) at kernel/qobject.cpp:1212
#31 0xb5d665cc in QApplicationPrivate::notify_helper (this=0x9fd1290, receiver=0xa07d470, e=0xbfcb04b0) at kernel/qapplication.cpp:4302
#32 0xb5d6d15e in QApplication::notify (this=0xbfcb08c0, receiver=0xa07d470, e=0xbfcb04b0) at kernel/qapplication.cpp:3706
#33 0xb7693c5a in KApplication::notify (this=0xbfcb08c0, receiver=0xa07d470, event=0xbfcb04b0) at ../../kdeui/kernel/kapplication.cpp:302
#34 0xb681d4cb in QCoreApplication::notifyInternal (this=0xbfcb08c0, receiver=0xa07d470, event=0xbfcb04b0) at kernel/qcoreapplication.cpp:726
#35 0xb684c796 in sendEvent (this=0x9fd4174) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#36 QTimerInfoList::activateTimers (this=0x9fd4174) at kernel/qeventdispatcher_unix.cpp:603
#37 0xb68493b7 in timerSourceDispatch (source=0x9fd41a8) at kernel/qeventdispatcher_glib.cpp:184
#38 idleTimerSourceDispatch (source=0x9fd41a8) at kernel/qeventdispatcher_glib.cpp:231
#39 0xb3f87305 in g_main_dispatch (context=0x9fd3490) at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c:1960
#40 IA__g_main_context_dispatch (context=0x9fd3490) at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c:2513
#41 0xb3f8afe8 in g_main_context_iterate (context=0x9fd3490, block=<value optimized out>, dispatch=1, self=0xa038658) at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c:2591
#42 0xb3f8b1c8 in IA__g_main_context_iteration (context=0x9fd3490, may_block=1) at /build/buildd-glib2.0_2.24.2-1-i386-AScyie/glib2.0-2.24.2/glib/gmain.c:2654
#43 0xb6849075 in QEventDispatcherGlib::processEvents (this=0x9f9fa80, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#44 0xb5e24ed5 in QGuiEventDispatcherGlib::processEvents (this=0x9f9fa80, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#45 0xb681bae9 in QEventLoop::processEvents (this=0xbfcb0774, flags=) at kernel/qeventloop.cpp:149
#46 0xb681bf3a in QEventLoop::exec (this=0xbfcb0774, flags=...) at kernel/qeventloop.cpp:201
#47 0xb682116f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#48 0xb5d66667 in QApplication::exec () at kernel/qapplication.cpp:3581
#49 0x0804aafe in _start ()

Reported using DrKonqi
Comment 1 Christian Herzberg 2010-11-15 16:03:19 UTC
Reopening kmail reveals, that the mail was send, but stuck in local "send" folder. Normally the mail should be moved the imap-"send"-folder (online).

Hope this helps understanding the crash. Good luck.
Comment 2 Myriam Schweingruber 2012-08-19 10:51:19 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding