Bug 180430 - Error when close Kmail with established connection (recive mail in progress)
Summary: Error when close Kmail with established connection (recive mail in progress)
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.10.3
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 184106 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-12 09:51 UTC by Yan Sereda
Modified: 2009-10-23 10:12 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kmail.kcrash (4.72 KB, text/plain)
2009-01-12 09:53 UTC, Yan Sereda
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yan Sereda 2009-01-12 09:51:24 UTC
Version:           1.10.3 (using KDE 4.1.3)
OS:                Linux
Installed from:    Mandriva RPMs

[KCrash handler]
#6  0xb67714fe in QWidget::effectiveWinId () from /usr/lib/libQtGui.so.4
#7  0xb74b37ac in KMessageBox::error () from /usr/lib/libkdeui.so.5
#8  0xb7ad819e in ?? () from /usr/lib/libkmailprivate.so.4
#9  0xb7ae5975 in ?? () from /usr/lib/libkmailprivate.so.4
#10 0xb7082c8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7083a95 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb561b545 in KIO::Scheduler::slaveError () from /usr/lib/libkio.so.5
#13 0xb561b7a4 in ?? () from /usr/lib/libkio.so.5
#14 0xb5621796 in KIO::Scheduler::qt_metacall () from /usr/lib/libkio.so.5
#15 0xb7082c8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb7083a95 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb5633b2d in KIO::SlaveInterface::error () from /usr/lib/libkio.so.5
#18 0xb5636865 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#19 0xb56343aa in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.5
#20 0xb56266a5 in KIO::Slave::gotInput () from /usr/lib/libkio.so.5
#21 0xb5626a30 in KIO::Slave::qt_metacall () from /usr/lib/libkio.so.5
#22 0xb7082c8d in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb7083a95 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb554bce5 in KIO::Connection::readyRead () from /usr/lib/libkio.so.5
#25 0xb554d81b in ?? () from /usr/lib/libkio.so.5
#26 0xb554de7b in KIO::Connection::qt_metacall () from /usr/lib/libkio.so.5
#27 0xb707bb8a in QMetaCallEvent::placeMetaCall ()
   from /usr/lib/libQtCore.so.4
#28 0xb707d782 in QObject::event () from /usr/lib/libQtCore.so.4
#29 0xb6720fac in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#30 0xb6729205 in QApplication::notify () from /usr/lib/libQtGui.so.4
#31 0xb7534b91 in KApplication::notify () from /usr/lib/libkdeui.so.5
#32 0xb706d853 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#33 0xb706e535 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#34 0xb706e71c in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#35 0xb709972d in ?? () from /usr/lib/libQtCore.so.4
#36 0xb4ab57ca in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#37 0xb4ab8ee8 in ?? () from /usr/lib/libglib-2.0.so.0
#38 0xb4ab90a8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#39 0xb709934a in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#40 0xb67bd95a in ?? () from /usr/lib/libQtGui.so.4
#41 0xb706bec3 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#42 0xb706c081 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#43 0xb706e7f2 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#44 0xb6720e14 in QApplication::exec () from /usr/lib/libQtGui.so.4
#45 0x0804a42f in _start ()
Comment 1 Yan Sereda 2009-01-12 09:53:16 UTC
Created attachment 30173 [details]
kmail.kcrash
Comment 2 Dario Andres 2009-01-12 22:37:22 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 3 Christophe Marin 2009-02-14 19:43:08 UTC
*** Bug 184106 has been marked as a duplicate of this bug. ***
Comment 4 Christophe Marin 2009-02-14 19:44:29 UTC
Markus: Can you please read the comment #2 and try to get a better backtrace for this crash ?

Thank you.
Comment 5 Christophe Marin 2009-03-09 10:15:03 UTC
No useful backtrace was provided for this bug report (see comment #1). Changing its status.
Comment 6 Pastor JW 2009-03-10 19:33:18 UTC
Application: KMail (kmail), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb43998d0 (LWP 7442)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb7eec410 in __kernel_vsyscall ()
#7  0xb657b085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb657ca01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb711d367 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb711d458 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb711d505 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb7afa0c9 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4
#13 0xb7b98ba6 in KMKernel::mainWin ()
   from /usr/lib/kde4/lib/libkmailprivate.so.4
#14 0xb7b8b4f7 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4
#15 0xb7b90bf6 in ?? () from /usr/lib/kde4/lib/libkmailprivate.so.4
#16 0xb7225f79 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb7226642 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb5793f6f in KIO::Scheduler::slaveError ()
   from /usr/lib/kde4/lib/libkio.so.5
#19 0xb5794b0d in ?? () from /usr/lib/kde4/lib/libkio.so.5
#20 0xb5797e58 in KIO::Scheduler::qt_metacall ()
   from /usr/lib/kde4/lib/libkio.so.5
#21 0xb7225f79 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#22 0xb7226642 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb57a7b59 in KIO::SlaveInterface::error ()
   from /usr/lib/kde4/lib/libkio.so.5
#24 0xb57a9dcb in KIO::SlaveInterface::dispatch ()
   from /usr/lib/kde4/lib/libkio.so.5
#25 0xb57aa0ed in KIO::SlaveInterface::dispatch ()
   from /usr/lib/kde4/lib/libkio.so.5
#26 0xb579cc67 in KIO::Slave::gotInput () from /usr/lib/kde4/lib/libkio.so.5
#27 0xb579e03d in KIO::Slave::qt_metacall ()
   from /usr/lib/kde4/lib/libkio.so.5
#28 0xb7225f79 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#29 0xb7226642 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#30 0xb56d7917 in KIO::Connection::readyRead ()
   from /usr/lib/kde4/lib/libkio.so.5
#31 0xb56d8788 in ?? () from /usr/lib/kde4/lib/libkio.so.5
#32 0xb56d95ce in KIO::Connection::qt_metacall ()
   from /usr/lib/kde4/lib/libkio.so.5
#33 0xb721f8ab in QMetaCallEvent::placeMetaCall ()
   from /usr/lib/libQtCore.so.4
#34 0xb7220c31 in QObject::event () from /usr/lib/libQtCore.so.4
#35 0xb68d7f9c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#36 0xb68dcbf9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#37 0xb76a4483 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#38 0xb72110b9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#39 0xb7212469 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#40 0xb721268d in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#41 0xb723c62f in ?? () from /usr/lib/libQtCore.so.4
#42 0xb4ce2cc6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#43 0xb4ce6083 in ?? () from /usr/lib/libglib-2.0.so.0
#44 0xb4ce663e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#45 0xb723c9f8 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#46 0xb696ba25 in ?? () from /usr/lib/libQtGui.so.4
#47 0xb721033d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#48 0xb72104cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#49 0xb721274d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#50 0xb68d7897 in QApplication::exec () from /usr/lib/libQtGui.so.4
#51 0x0804a85f in _start ()
#0  0xb7eec410 in __kernel_vsyscall ()
Comment 7 Dario Andres 2009-03-10 19:55:29 UTC
@Pastor: your crash seems to be a different one: If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace in a NEW report? Thanks :)
Comment 8 Markus Walther 2009-03-20 02:31:47 UTC
Sorry, I can't reproduce the crash anymore. It happened when KMail was trying to poll a pop server with settings which were not appropriate for the server at the time it happened. KMail crashed shortly after closing KMail. 

If I could, I'd have attached a full debug backtrace according to the mentioned description. 

Since polling from my provider worked well, KMail didn't crash anymore on my system. 

By the way, I've had some minor problems with KMail since using KDE 4. 

- Importing mails received from KMail by the former Linux (and KDE) version (copying the content of .../.kde/share/apps/kmail/mail) sometimes results in a display of the year 2106 instead of the real one. 

- There seems to be a bit of loose chain to the KDE Wallet Manager, which is obviously the preferred store of passwords to KMail. I often saw something like "kwalletmanager is unavailable, please enter your password for ... " when closing KMail. Workaround: forcing KMail to check for new mails when starting.
Comment 9 Christophe Marin 2009-10-23 10:12:17 UTC
Closing the old crash reports which don't have a useful backtrace. Thanks.