Version: 1.9.10 (using KDE 3.5.10) OS: Linux Installed from: SuSE RPMs Using the system tray icon to reopen kmail (as part of kontact), and if the trash folder was previously selected before close, the trash folder looks empty except for the threading tree lines are still present on the very left (each row is blank except for the 'tree' thread lines). If an email row item is selected while in this odd state then kmail (and kontact) crash. If another folder is selected as soon as this odd state is observed, then all continues as normal, and coming back to the trash folder is then in a normal state (ie all rows showing). Have not observed this with any other folder. Here is the last backtrace from Crash handler: System configuration startup check disabled. [?1034h(no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [... previous repeated many times ...] [Thread debugging using libthread_db enabled] [New Thread 0xb5fe66d0 (LWP 22941)] [New Thread 0xb35c0b90 (LWP 22945)] [New Thread 0xb3dc1b90 (LWP 22944)] [New Thread 0xb45c2b90 (LWP 22943)] [New Thread 0xb4dc3b90 (LWP 22942)] (no debugging symbols found) [... previous repeated many times ...] [KCrash handler] #6 0xb50914a4 in KMHeaders::selectedSernums () from /opt/kde3/lib/libkmailprivate.so #7 0xb5265727 in KMMainWidget::updateMessageActions () from /opt/kde3/lib/libkmailprivate.so #8 0xb52750fe in KMMainWidget::qt_invoke () from /opt/kde3/lib/libkmailprivate.so #9 0xb6c77b4d in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #10 0xb6c786ed in QObject::activate_signal () from /usr/lib/qt3/lib/libqt-mt.so.3 #11 0xb6fadea9 in QTimer::timeout () from /usr/lib/qt3/lib/libqt-mt.so.3 #12 0xb6c9abaf in QTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3 #13 0xb6c1933c in QApplication::internalNotify () from /usr/lib/qt3/lib/libqt-mt.so.3 #14 0xb6c1a126 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 #15 0xb72c45e2 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 #16 0xb6c0e614 in QEventLoop::activateTimers () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0xb6bc8573 in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0xb6c2fec0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #19 0xb6c2fd56 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0xb6c18eaf in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0x0805bf33 in QWidget::setUpdatesEnabled () #22 0xbfeb2fac in ?? () #23 0x00000001 in ?? () #24 0x00000001 in ?? () #25 0x00000000 in ?? () Thank you for your effort and time in making kmail an excellent program (barring the odd crash) =)
To clarify further, this does not happen everytime I reopen kmail from the system tray and the trash was previous selected. It is intermittent. Was just able to reproduce the odd state. With kmail open (in kontact), emptied the trash via toolbar icon, with trash folder selected, closed kmail (and kontact), then used the system tray icon to 'check mail' (I don't check mail that way normally). Some email was retrieved (and since I use filters to weed out spam, some went straight to trash) and then reopening kmail from the system tray icon, the trash showed itself in the odd state again (only thread lines showing).
The version you are using is almost unmantained. You my try to use kmail from kde4. Hint: It is possible to use kmail from kde4 and still use the old kde3 desktop. just install kde4-kmail (or kde4-pim) from yast2 (or zypper) and you'll have it. Probably you will need to setup again you mail accounts as the account information is store in another directory (.kde in 3.5 and .kde4 in 4.x).
This seems to be related to bug 171491
*** This bug has been marked as a duplicate of bug 171491 ***