| Summary: | crash at startup when syncing IMAP inbox | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Marco <marco.mandl> |
| Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | andresbajotierra, christophe |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Marco
2008-08-18 18:55:50 UTC
Please read the following page and provide a useful backtrace for this crash : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports There is not debug package for kde4-kmail, at least not in the Factory repository. I am not able to compile kde myself. Sorry Install the kdepim4-debuginfo and kdepimlibs4-debuginfo packages. Done thiswhich aalsoupgrdde the kdepim4 and kdepimlibs4 packages to version. 4.1.0-51.1.
Now I get the following a few seconds after starting kmail:
The process for the imap://foo.bar.com protoocl died unexpectedly.
And after a few minutes of leaving the program unused I get the following SIGSEGV. Maybe it comes from the regular mail check every 5 minutes.
Application: KMail (kmail), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0x7f1ae9e2f700 (LWP 12789)]
[KCrash handler]
#5 0x0000000001026d60 in ?? ()
#6 0x00007f1ae95ec1ab in ?? () from /usr/lib64/libkmailprivate.so.4
#7 0x00007f1ae95ec370 in ?? () from /usr/lib64/libkmailprivate.so.4
#8 0x00007f1ae9610f46 in ?? () from /usr/lib64/libkmailprivate.so.4
#9 0x00007f1ae9617aab in ?? () from /usr/lib64/libkmailprivate.so.4
#10 0x00007f1ae32964e0 in QMetaObject::activate ()
from /usr/lib64/libQtCore.so.4
#11 0x00007f1ae566f324 in KIO::TransferJob::data ()
from /usr/lib64/libkio.so.5
#12 0x00007f1ae5676999 in KIO::TransferJob::qt_metacall ()
from /usr/lib64/libkio.so.5
#13 0x00007f1ae32964e0 in QMetaObject::activate ()
from /usr/lib64/libQtCore.so.4
#14 0x00007f1ae5715a92 in KIO::SlaveInterface::data ()
from /usr/lib64/libkio.so.5
#15 0x00007f1ae57181f8 in KIO::SlaveInterface::dispatch ()
from /usr/lib64/libkio.so.5
#16 0x00007f1ae5716082 in KIO::SlaveInterface::dispatch ()
from /usr/lib64/libkio.so.5
#17 0x00007f1ae57098de in KIO::Slave::gotInput () from /usr/lib64/libkio.so.5
#18 0x00007f1ae5709be8 in KIO::Slave::qt_metacall ()
from /usr/lib64/libkio.so.5
#19 0x00007f1ae32964e0 in QMetaObject::activate ()
from /usr/lib64/libQtCore.so.4
#20 0x00007f1ae5649a91 in ?? () from /usr/lib64/libkio.so.5
#21 0x00007f1ae564a13a in KIO::Connection::qt_metacall ()
from /usr/lib64/libkio.so.5
#22 0x00007f1ae32929ce in QObject::event () from /usr/lib64/libQtCore.so.4
#23 0x00007f1adf54592d in QApplicationPrivate::notify_helper ()
from /usr/lib64/libQtGui.so.4
#24 0x00007f1adf54bcfa in QApplication::notify ()
from /usr/lib64/libQtGui.so.4
#25 0x00007f1ae4d830eb in KApplication::notify ()
from /usr/lib64/libkdeui.so.5
#26 0x00007f1ae3284e9c in QCoreApplication::notifyInternal ()
from /usr/lib64/libQtCore.so.4
#27 0x00007f1ae32857cb in QCoreApplicationPrivate::sendPostedEvents ()
from /usr/lib64/libQtCore.so.4
#28 0x00007f1adf5c6277 in ?? () from /usr/lib64/libQtGui.so.4
#29 0x00007f1ae32837f2 in QEventLoop::processEvents ()
from /usr/lib64/libQtCore.so.4
#30 0x00007f1ae3283985 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#31 0x00007f1ae3285a25 in QCoreApplication::exec ()
from /usr/lib64/libQtCore.so.4
#32 0x000000000040309b in main (argc=<value optimized out>,
argv=<value optimized out>)
at /usr/src/debug/kdepim-4.1.0/kmail/main.cpp:146
#0 0x00007f1adda54230 in nanosleep () from /lib64/libc.so.6
Can you still reproduce this bug with a recent KDE (4.1.4 / 4.2beta2 / 4.2rc1 / 4.2svn / 4.3svn) ? Thanks :) Due to lack of feedback, we will now change this bug status. (see comment #5) Closing as there was no feedback. Please feel free to reopen this report if you can reproduce it with Kmail 4.8.5 or later and provide a new backtrace. |