174633 – Crashes when opening maildir folders

Bug 174633 - Crashes when opening maildir folders

Summary: Crashes when opening maildir folders

Status:	RESOLVED NOT A BUG

Alias:	None

Product:	kmail
Classification:	Applications
Component:	general (show other bugs)
Version:	unspecified
Platform:	openSUSE Linux

Importance:	NOR crash
Target Milestone:	---
Assignee:	kdepim bugs

URL:
Keywords:

Depends on:
Blocks:

Reported:	2008-11-08 16:31 UTC by workingwriter
Modified:	2009-03-19 00:34 UTC (History)
CC List:	2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description workingwriter 2008-11-08 16:31:26 UTC

Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    SuSE RPMs

I am using KMail/Kontact 4.1.3.

KMail displays the main local folder with no issues. If I click any other folder inside Local Folders, Kontact crashes (Signal 6) with the following Backtrace:

Application: Kontact (kontact), signal SIGABRT
[?1034h(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)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f59a83ea700 (LWP 3083)]
(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]
#5  0x00007f599d2755c5 in raise () from /lib64/libc.so.6
#6  0x00007f599d276bb3 in abort () from /lib64/libc.so.6
#7  0x00007f599d2b33a8 in ?? () from /lib64/libc.so.6
#8  0x00007f599d2b8af8 in ?? () from /lib64/libc.so.6
#9  0x00007f599d2b8d8a in ?? () from /lib64/libc.so.6
#10 0x00007f599d2bb626 in ?? () from /lib64/libc.so.6
#11 0x00007f599d2bd111 in malloc () from /lib64/libc.so.6
#12 0x00007f599dacfafd in operator new () from /usr/lib64/libstdc++.so.6
#13 0x00007f599dacfc39 in operator new[] () from /usr/lib64/libstdc++.so.6
#14 0x00007f5991681291 in ?? () from /usr/lib64/libkmailprivate.so.4
#15 0x00007f599167e6fb in ?? () from /usr/lib64/libkmailprivate.so.4
#16 0x00007f59915be636 in ?? () from /usr/lib64/libkmailprivate.so.4
#17 0x00007f59915fe354 in ?? () from /usr/lib64/libkmailprivate.so.4
#18 0x00007f59915bbc0c in ?? () from /usr/lib64/libkmailprivate.so.4
#19 0x00007f5991779aa4 in ?? () from /usr/lib64/libkmailprivate.so.4
#20 0x00007f599177a655 in ?? () from /usr/lib64/libkmailprivate.so.4
#21 0x00007f59a2aed274 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#22 0x00007f59915de8c0 in ?? () from /usr/lib64/libkmailprivate.so.4
#23 0x00007f59915e138d in ?? () from /usr/lib64/libkmailprivate.so.4
#24 0x00007f59a2aed274 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#25 0x00007f5991598dc0 in ?? () from /usr/lib64/libkmailprivate.so.4
#26 0x00007f5991599372 in ?? () from /usr/lib64/libkmailprivate.so.4
#27 0x00007f59a2aed274 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#28 0x00007f59915bb7f0 in ?? () from /usr/lib64/libkmailprivate.so.4
#29 0x00007f599161bd66 in ?? () from /usr/lib64/libkmailprivate.so.4
#30 0x00007f59915bcf6a in ?? () from /usr/lib64/libkmailprivate.so.4
#31 0x00007f5991554d61 in ?? () from /usr/lib64/libkmailprivate.so.4
#32 0x00007f599176e95d in KMMainWidget::folderSelected ()
   from /usr/lib64/libkmailprivate.so.4
#33 0x00007f5991770906 in KMMainWidget::qt_metacall ()
   from /usr/lib64/libkmailprivate.so.4
#34 0x00007f59a2aed274 in QMetaObject::activate ()
   from /usr/lib64/libQtCore.so.4
#35 0x00007f5991524fef in ?? () from /usr/lib64/libkmailprivate.so.4
#36 0x00007f599152a263 in ?? () from /usr/lib64/libkmailprivate.so.4
#37 0x00007f599152baab in ?? () from /usr/lib64/libkmailprivate.so.4
#38 0x00007f59a589e019 in Q3ScrollView::viewportMouseReleaseEvent ()
   from /usr/lib64/libQt3Support.so.4
#39 0x00007f59a589f7e6 in Q3ScrollView::eventFilter ()
   from /usr/lib64/libQt3Support.so.4
#40 0x00007f59a58430fe in Q3ListView::eventFilter ()
   from /usr/lib64/libQt3Support.so.4
#41 0x00007f59a2ad8138 in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib64/libQtCore.so.4
#42 0x00007f599ef0614c in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#43 0x00007f599ef0e79a in QApplication::notify () from /usr/lib64/libQtGui.so.4
#44 0x00007f59a4833d6b in KApplication::notify () from /usr/lib64/libkdeui.so.5
#45 0x00007f59a2ad8e71 in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#46 0x00007f599ef0db38 in QApplicationPrivate::sendMouseEvent ()
   from /usr/lib64/libQtGui.so.4
#47 0x00007f599ef72259 in ?? () from /usr/lib64/libQtGui.so.4
#48 0x00007f599ef70c77 in QApplication::x11ProcessEvent ()
   from /usr/lib64/libQtGui.so.4
#49 0x00007f599ef9755c in ?? () from /usr/lib64/libQtGui.so.4
#50 0x00007f599bdc893a in g_main_context_dispatch ()
   from /usr/lib64/libglib-2.0.so.0
#51 0x00007f599bdcc040 in g_main_context_iterate ()
   from /usr/lib64/libglib-2.0.so.0
#52 0x00007f599bdcc1dc in g_main_context_iteration ()
   from /usr/lib64/libglib-2.0.so.0
#53 0x00007f59a2b0139f in QEventDispatcherGlib::processEvents ()
   from /usr/lib64/libQtCore.so.4
#54 0x00007f599ef96ccf in ?? () from /usr/lib64/libQtGui.so.4
#55 0x00007f59a2ad7772 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#56 0x00007f59a2ad78fd in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#57 0x00007f59a2ad9ded in QCoreApplication::exec ()
   from /usr/lib64/libQtCore.so.4
#58 0x0000000000404a7b in _start ()
#0  0x00007f599d2e5230 in nanosleep () from /lib64/libc.so.6

Comment 1 Pino Toscano 2008-11-10 09:16:03 UTC

Hi,

unfortunately, the backtrace you posted is not so useful. You can read in:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
further instructions on how to get a more detailed one.
Thank you.

Comment 2 workingwriter 2008-11-10 14:00:56 UTC

(In reply to comment #1)
> Hi,
> 
> unfortunately, the backtrace you posted is not so useful. You can read in:
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
> further instructions on how to get a more detailed one.
> Thank you.
> 

Pino,

Thanks for the pointer. The good news is the crash has gone away. Apologies for the premature report.

Comment 3 mario tuling 2008-11-12 05:04:26 UTC

so i guess we can close with invalid?

Comment 4 Jaime Torres 2008-11-12 10:27:22 UTC

The crash has gone away.