[Bug 207210] KMail crashes when accessing the folders of an email account

[Maria Niku]

https://bugs.kde.org/show_bug.cgi?id=207210





--- Comment #2 from Maria Niku <mr wisty gmail com>  2009-09-12 22:22:09 ---
Apologies. Here the error messages directly:

1. Error message:

Unable to Enter Folder
This means that an attempt to enter (in other words, to open) the requested
folder imaps://(address):993/;TYPE=LIST was rejected.
Details of the request:
URL: (unknown)
Date and time: Saturday 12 September 2009 22:44
Additional information: imaps://(address):993/;TYPE=LIST
Possible causes:
Your access permissions may be inadequate to perform the requested operation on
this resource.
The file may be in use (and thus locked) by another user or application.
Possible solutions:
Check your access permissions on this resource.
Check to make sure that no other application or user is using the file or has
locked the file.
Contact your appropriate computer support system, whether the system
administrator, or technical support group for further assistance.

2. Crash report:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f467f1e6820 (LWP 3154))]

Thread 2 (Thread 0x7f4669642910 (LWP 3187)):
#0  0x0000003e3520b57d in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x0000003bb4a5ace2 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQtCore.so.4
#2  0x0000003bb4a50e22 in ?? () from /usr/lib64/libQtCore.so.4
#3  0x0000003bb4a59cd5 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x0000003e3520686a in start_thread () from /lib64/libpthread.so.0
#5  0x0000003e346de3bd in clone () from /lib64/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f467f1e6820 (LWP 3154)):
[KCrash Handler]
#5  0x000000380f59ee08 in KIO::Slave::deref() () from /usr/lib64/libkio.so.5
#6  0x000000380f59f7f9 in KIO::Slave::gotInput() () from /usr/lib64/libkio.so.5
#7  0x000000380f5a18fc in KIO::Slave::qt_metacall(QMetaObject::Call, int,
void**) () from /usr/lib64/libkio.so.5
#8  0x0000003bb4b54fdc in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib64/libQtCore.so.4
#9  0x000000380f4baf57 in ?? () from /usr/lib64/libkio.so.5
#10 0x000000380f4bb06d in KIO::Connection::qt_metacall(QMetaObject::Call, int,
void**) () from /usr/lib64/libkio.so.5
#11 0x0000003bb4b4f309 in QObject::event(QEvent*) () from
/usr/lib64/libQtCore.so.4
#12 0x0000003cf5d8ee2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQtGui.so.4
#13 0x0000003cf5d95e5e in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQtGui.so.4
#14 0x000000380ea11b56 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libkdeui.so.5
#15 0x0000003bb4b3fcbc in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQtCore.so.4
#16 0x0000003bb4b408c8 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#17 0x0000003bb4b68743 in ?? () from /usr/lib64/libQtCore.so.4
#18 0x0000003bb3e3790e in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#19 0x0000003bb3e3b0e8 in ?? () from /lib64/libglib-2.0.so.0
#20 0x0000003bb3e3b20a in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#21 0x0000003bb4b683b6 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /usr/lib64/libQtCore.so.4
#22 0x0000003cf5e21b8e in ?? () from /usr/lib64/libQtGui.so.4
#23 0x0000003bb4b3e5f2 in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQtCore.so.4
#24 0x0000003bb4b3e9c4 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib64/libQtCore.so.4
#25 0x0000003bb4b40b79 in QCoreApplication::exec() () from
/usr/lib64/libQtCore.so.4
#26 0x0000000000403d17 in _start ()

3. Relevant parts of .xsession-errors

QThreadStorage: Thread 0x20556f0 exited after QThreadStorage 2147483638
destroyed
kdeinit4: preparing to launch /usr/bin/kontact
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
Calling appendChild() on a null node does nothing.
kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib64/kde4/kio_imap4.so
<unknown program name>(3132)/ kdemain: IMAP4::kdemain
kdeinit4: preparing to launch /usr/lib64/kde4/kio_imap4.so
<unknown program name>(3133)/ kdemain: IMAP4::kdemain
kdeinit4: preparing to launch /usr/lib64/kde4/kio_imap4.so
<unknown program name>(3134)/ kdemain: IMAP4::kdemain
kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so
kdeinit4: preparing to launch /usr/lib64/kde4/kio_file.so
*** KMail got signal 11 (Crashing)
KCrash: Application 'kontact' crashing...
kdeinit4: preparing to launch /usr/libexec/kde4/drkonqi
kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kwrite.so

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.