Bug 169843 - kmail crashed while loading mail by imap
Summary: kmail crashed while loading mail by imap
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-26 10:56 UTC by Wilhelm Schillilng
Modified: 2009-01-18 00:33 UTC (History)
2 users (show)

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 Wilhelm Schillilng 2008-08-26 10:56:18 UTC
Version:            (using KDE 4.1.0)
OS:                Linux
Installed from:    Ubuntu Packages

This is my first try to use bugzilla and I am "just" user of Kubuntu and Kontact. I hope the following information will help anyway:

While checking / loading mail in an imap-account kmail crashes several times. I am not shure but in my opinion kmail has problems every now and than with (larger) attachments. Maybe this is connected somehow to this - here is the backtrace:

Anwendung: Kontact (kontact), Signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb4e34940 (LWP 12035)]
[New Thread 0xb0dcab90 (LWP 12305)]
[KCrash handler]
#6  0xb72de59a in QProgressBar::minimum () from /usr/lib/libQtGui.so.4
#7  0xb783cc9a in QObject::event () from /usr/lib/libQtCore.so.4
#8  0xb6efcc0c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#9  0xb6f017a9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#10 0xb7cc1f53 in KApplication::notify (this=0xbfbd94c8, receiver=0x80a6a08, 
    event=0xbfbd9258)
    at /build/buildd/kde4libs-4.1.0/kdeui/kernel/kapplication.cpp:311
#11 0xb782c6a9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#12 0xb785a1a1 in ?? () from /usr/lib/libQtCore.so.4
#13 0xb7857a40 in ?? () from /usr/lib/libQtCore.so.4
#14 0xb56e5dd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#15 0xb56e9193 in ?? () from /usr/lib/libglib-2.0.so.0
#16 0xb56e974e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#17 0xb7857f98 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#18 0xb6f901b5 in ?? () from /usr/lib/libQtGui.so.4
#19 0xb782b92d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#20 0xb782babd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#21 0xb782dd3d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#22 0xb6efc567 in QApplication::exec () from /usr/lib/libQtGui.so.4
#23 0x0804b326 in _start ()
#0  0xb7f76410 in __kernel_vsyscall ()

Thank you for help!
Comment 1 Dario Andres 2008-12-07 23:22:32 UTC
Have you experienced this bug again with a recent KDE version? (4.1.3 / 4.2beta1 / 4.2svn) ? Thanks :)
Comment 2 Dario Andres 2009-01-18 00:33:36 UTC
No news from the bug reporter, closing. Please reopen this bug report if you experience the same bug again with a recent KDE (4.1.4 / 4.2beta2 / 4.2rc1 / 4.2svn / 4.3svn) . Thanks :)
The backtrace looks similar to the one in bug 178885, however the situation is completely different so I suppose it's a Qt bug