Bug 261733

Summary: crash after adding a folder to favorite folder list
Product: [Applications] kmail2 Reporter: m.wege
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: m.wege, tokoe, Wolfgang_Mader
Priority: NOR Keywords: investigated, triaged
Version: 2.0.89   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi
New crash information added by DrKonqi
Traceback (**) of kmail crash due to favorite folders

Description m.wege 2010-12-31 16:19:18 UTC
Application: kmail (2.0.89)
KDE Platform Version: 4.5.90 (4.6 RC1)
Qt Version: 4.7.0
Operating System: Linux 2.6.37-11-generic-pae i686
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed: I added a folder to the favorite folder list, then the crash happened. The funny thing: I had done this before. This was number 6 or 7, before that, there was no crash. Kmail crashed repeatedly on restart until I removed the configs about favourite folders. The last folder added did not contain any unusual character. When trying to reproduce the bug, just adding the folders did not do any crash. But starting to rename the folders (essentially removing the mailbox name) Kmail started to behave odd: First one of the folders appeared double, then 2 of the folders had the option to rename it greyed out. Deleting the double folder -> crash again

- Unusual behavior I noticed:

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0xb22f3730 (LWP 23649))]

Thread 3 (Thread 0xaf48ab70 (LWP 23778)):
#0  0xb7868424 in __kernel_vsyscall ()
#1  0xb5ab74dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb6041d9d in pthread_cond_wait () from /lib/libc.so.6
#3  0xb3e7a3a5 in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb437d680) at wtf/FastMalloc.cpp:2378
#4  0xb3e7a481 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0xb437d680) at wtf/FastMalloc.cpp:1497
#5  0xb5ab2cc9 in start_thread () from /lib/libpthread.so.0
#6  0xb603469e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xac781b70 (LWP 24968)):
#0  0xb6041fa1 in pthread_mutex_unlock () from /lib/libc.so.6
#1  0xb48dde58 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#2  0xb48de279 in ?? () from /lib/libglib-2.0.so.0
#3  0xb48de848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#4  0xb635b59f in QEventDispatcherGlib::processEvents (this=0xa6b0a38, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#5  0xb632b609 in QEventLoop::processEvents (this=0xac781270, flags=) at kernel/qeventloop.cpp:149
#6  0xb632ba8a in QEventLoop::exec (this=0xac781270, flags=...) at kernel/qeventloop.cpp:201
#7  0xb6227b7e in QThread::exec (this=0xa6f2f00) at thread/qthread.cpp:490
#8  0xb630a35b in QInotifyFileSystemWatcherEngine::run (this=0xa6f2f00) at io/qfilesystemwatcher_inotify.cpp:248
#9  0xb622adf9 in QThreadPrivate::start (arg=0xa6f2f00) at thread/qthread_unix.cpp:266
#10 0xb5ab2cc9 in start_thread () from /lib/libpthread.so.0
#11 0xb603469e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb22f3730 (LWP 23649)):
[KCrash Handler]
#7  Akonadi::CollectionStatisticsDelegate::paint (this=0x99233a0, painter=0xbf9474dc, option=..., index=...) at ../../akonadi/collectionstatisticsdelegate.cpp:222
#8  0xb6b86d66 in QListView::paintEvent (this=0x9913fe8, e=0xbf947d14) at itemviews/qlistview.cpp:1044
#9  0xb65eacc6 in QWidget::event (this=0x9913fe8, event=0xbf947d14) at kernel/qwidget.cpp:8333
#10 0xb6a0c763 in QFrame::event (this=0x9913fe8, e=0xbf947d14) at widgets/qframe.cpp:557
#11 0xb6aa9a82 in QAbstractScrollArea::viewportEvent (this=0x129de058, e=0x12a27000) at widgets/qabstractscrollarea.cpp:1043
#12 0xb6b660f7 in QAbstractItemView::viewportEvent (this=0x9913fe8, event=0xbf947d14) at itemviews/qabstractitemview.cpp:1619
#13 0xb6aac4d5 in viewportEvent (this=0x990a8f0, o=0x99283d0, e=0xbf947d14) at widgets/qabstractscrollarea_p.h:100
#14 QAbstractScrollAreaFilter::eventFilter (this=0x990a8f0, o=0x99283d0, e=0xbf947d14) at widgets/qabstractscrollarea_p.h:116
#15 0xb632c29a in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x91c4f28, receiver=0x99283d0, event=0xbf947d14) at kernel/qcoreapplication.cpp:847
#16 0xb658cfb9 in QApplicationPrivate::notify_helper (this=0x91c4f28, receiver=0x99283d0, e=0xbf947d14) at kernel/qapplication.cpp:4392
#17 0xb65930e9 in QApplication::notify (this=0xbf948aec, receiver=0x99283d0, e=0xbf947d14) at kernel/qapplication.cpp:4361
#18 0xb76582ca in KApplication::notify (this=0xbf948aec, receiver=0x99283d0, event=0xbf947d14) at ../../kdeui/kernel/kapplication.cpp:311
#19 0xb632cb3b in QCoreApplication::notifyInternal (this=0xbf948aec, receiver=0x99283d0, event=0xbf947d14) at kernel/qcoreapplication.cpp:732
#20 0xb65f1ee6 in sendSpontaneousEvent (this=0x99245f8, pdev=0x98d01cc, rgn=..., offset=..., flags=<value optimized out>, sharedPainter=0x0, backingStore=0x98d0178) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#21 QWidgetPrivate::drawWidget (this=0x99245f8, pdev=0x98d01cc, rgn=..., offset=..., flags=<value optimized out>, sharedPainter=0x0, backingStore=0x98d0178) at kernel/qwidget.cpp:5420
#22 0xb67e2bff in QWidgetBackingStore::sync (this=0x98d0178) at painting/qbackingstore.cpp:1320
#23 0xb65e42b3 in QWidgetPrivate::syncBackingStore (this=0x9381ab8) at kernel/qwidget.cpp:1805
#24 0xb65eb466 in QWidget::event (this=0x9381a18, event=0x126ba328) at kernel/qwidget.cpp:8480
#25 0xb6a2b917 in QMainWindow::event (this=0x9381a18, event=0x126ba328) at widgets/qmainwindow.cpp:1417
#26 0xb7744d14 in KMainWindow::event (this=0x9381a18, ev=0x126ba328) at ../../kdeui/widgets/kmainwindow.cpp:1100
#27 0xb77908ff in KXmlGuiWindow::event (this=0x9381a18, ev=0x126ba328) at ../../kdeui/xmlgui/kxmlguiwindow.cpp:126
#28 0xb658cfdc in QApplicationPrivate::notify_helper (this=0x91c4f28, receiver=0x9381a18, e=0x126ba328) at kernel/qapplication.cpp:4396
#29 0xb65930e9 in QApplication::notify (this=0xbf948aec, receiver=0x9381a18, e=0x126ba328) at kernel/qapplication.cpp:4361
#30 0xb76582ca in KApplication::notify (this=0xbf948aec, receiver=0x9381a18, event=0x126ba328) at ../../kdeui/kernel/kapplication.cpp:311
#31 0xb632cb3b in QCoreApplication::notifyInternal (this=0xbf948aec, receiver=0x9381a18, event=0x126ba328) at kernel/qcoreapplication.cpp:732
#32 0xb632fd8b in sendEvent (receiver=0x0, event_type=0, data=0x91903c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#33 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x91903c0) at kernel/qcoreapplication.cpp:1373
#34 0xb632ff4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#35 0xb635ba74 in sendPostedEvents (s=0x91c69a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#36 postEventSourceDispatch (s=0x91c69a0) at kernel/qeventdispatcher_glib.cpp:277
#37 0xb48da855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#38 0xb48de668 in ?? () from /lib/libglib-2.0.so.0
#39 0xb48de848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#40 0xb635b565 in QEventDispatcherGlib::processEvents (this=0x91b7fe8, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#41 0xb664ebe5 in QGuiEventDispatcherGlib::processEvents (this=0x91b7fe8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#42 0xb632b609 in QEventLoop::processEvents (this=0xbf948a04, flags=) at kernel/qeventloop.cpp:149
#43 0xb632ba8a in QEventLoop::exec (this=0xbf948a04, flags=...) at kernel/qeventloop.cpp:201
#44 0xb633000f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#45 0xb658be07 in QApplication::exec () at kernel/qapplication.cpp:3672
#46 0x0804a4e6 in main (argc=3, argv=0xbf948ca4) at ../../kmail/main.cpp:145

This bug may be a duplicate of or related to bug 261225.

Possible duplicates by query: bug 261225.

Reported using DrKonqi
Comment 1 m.wege 2010-12-31 16:22:37 UTC
Created attachment 55420 [details]
New crash information added by DrKonqi

kmail (2.0.89) on KDE Platform 4.5.90 (4.6 RC1) using Qt 4.7.0

- What I was doing when the application crashed:
The second crash I mentioned, seems to be the same.

-- Backtrace (Reduced):
#7  Akonadi::CollectionStatisticsDelegate::paint (this=0x9fbf530, painter=0xbfcbe1ec, option=..., index=...) at ../../akonadi/collectionstatisticsdelegate.cpp:222
#8  0xb6a32d66 in QListView::paintEvent (this=0x9efdce8, e=0xbfcbea24) at itemviews/qlistview.cpp:1044
#9  0xb6496cc6 in QWidget::event (this=0x9efdce8, event=0xbfcbea24) at kernel/qwidget.cpp:8333
#10 0xb68b8763 in QFrame::event (this=0x9efdce8, e=0xbfcbea24) at widgets/qframe.cpp:557
#11 0xb6955a82 in QAbstractScrollArea::viewportEvent (this=0xc4aba78, e=0xc4ac0e0) at widgets/qabstractscrollarea.cpp:1043
Comment 2 m.wege 2010-12-31 20:43:08 UTC
I believe I may have an idea what could be related to that crash. In my favourite folder list there are two folders which are there, but I can not find them in the kmail2rc where the other folders are stored. Then there is another one, which appears double. The extra folder can not be renamed in the context menu. They also appear a little later even though they are from the same IMAP-account. My theory: May be there is a double function for favourite folders which then interfer with each other.
Comment 3 Tobias Koenig 2011-01-02 17:13:25 UTC
Hej,

can you attach the '[FavoriteCollections]' section of your kmail2rc, please?
Do all the collections (with the given ids) really exists in your Akonadi setup? (You can check with akonadiconsole).

Ciao,
Tobias
Comment 4 m.wege 2011-01-03 00:26:09 UTC
Here:
[FavoriteCollections]
FavoriteCollectionIds=16,40,35,38,54,29,33
FavoriteCollectionLabels=Posteingang,cshcmails,foren,tauschring,pfda,facebook

facebook appears double and there also appear two extra folders in Favorite folders (which can not be renamed). 
Sometimes instead of the extra facebook folder and the two extra folders only the account-name appears in the favorite folders.
I have started akonadiconsole, but I have no idea, how to get the information you requested.
Comment 5 m.wege 2011-01-17 07:31:42 UTC
Created attachment 56114 [details]
New crash information added by DrKonqi

kmail (2.0.89) on KDE Platform 4.5.95 (4.6 RC2) using Qt 4.7.0

- What I was doing when the application crashed: doing the same as described in the report above

-- Backtrace (Reduced):
#7  Akonadi::CollectionStatisticsDelegate::paint (this=0x9f80ec0, painter=0xbfa86e7c, option=..., index=...) at ../../akonadi/collectionstatisticsdelegate.cpp:222
#8  0xb6a33d66 in QListView::paintEvent (this=0x9f79c00, e=0xbfa876b4) at itemviews/qlistview.cpp:1044
#9  0xb6497cc6 in QWidget::event (this=0x9f79c00, event=0xbfa876b4) at kernel/qwidget.cpp:8333
#10 0xb68b9763 in QFrame::event (this=0x9f79c00, e=0xbfa876b4) at widgets/qframe.cpp:557
#11 0xb6956a82 in QAbstractScrollArea::viewportEvent (this=0xc73b710, e=0xc594f00) at widgets/qabstractscrollarea.cpp:1043
Comment 6 Torgny Nyblom 2011-01-17 08:31:34 UTC
If you reduce the backtraces please leave at least some frames belonging to KDE.
Comment 7 m.wege 2011-01-17 08:49:00 UTC
I did not do this. This report and the attachments were made with Dr.Konqi. Seems to be a bug then?  Or is the full thing that which is in the attachments? Seems at least that it contains more.
Comment 8 Wolfgang Mader 2011-11-19 04:44:56 UTC
Created attachment 65834 [details]
Traceback (**) of kmail crash due to favorite folders
Comment 9 Wolfgang Mader 2011-11-19 04:46:48 UTC
Hi,

I had the same issue. Last time kmail was running not all of my folders which I
have selected to be favorite ones were shown. Therefore, I added the folder in
question again, but it was not shown anyways. The next time I wanted to start
kmail it crashed with the traceback wich you can find in my last post. Not
the most usefull one, sorry.

To fix the problem I removed the two lines from the favorite folder section in
kmail2rc.
Comment 10 Andrew Crouthamel 2018-09-22 02:08:52 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Andrew Crouthamel 2018-10-27 03:50:30 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!