Bug 179645 - body part of email not shown
Summary: body part of email not shown
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: SVN trunk (KDE 4)
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 180287 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-04 21:44 UTC by Richard Bos
Modified: 2010-02-03 21:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
The body part behind the red circle is empty (86.83 KB, image/png)
2009-01-04 21:53 UTC, Richard Bos
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Bos 2009-01-04 21:44:56 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

The body part of emails are not shown by kmail.  This is with kde-4.1.87.  It used to work, but without reason known to me,
the body part of emails are not shown.  The attached screenshot, makes it clearer what is meant exactly.

This is for an imap account.  Removing the account and adding it again does not help.
Comment 1 Richard Bos 2009-01-04 21:53:04 UTC
Created attachment 29907 [details]
The body part behind the red circle is empty

When the email subject is double clicked the email body part is shown in
the popped up window, as can be seen in the screenshot.

This is in kontact.  When kontact is quit, the crash handler pops up.
According the crash handler the backtrace is not usefull, but perhaps it still
reveals something....

[Current thread is 1 (Thread 0xb49f6700 (LWP 12700))]

Thread 3 (Thread 0xb068db90 (LWP 12747)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6676f62 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb66d784c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#3  0xb66cc9c6 in ?? () from /usr/lib/libQtCore.so.4
#4  0xb66d685e in ?? () from /usr/lib/libQtCore.so.4
#5  0xb66731b5 in start_thread () from /lib/libpthread.so.0
#6  0xb5a8838e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xaf97ab90 (LWP 12795)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6676f62 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb66d784c in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#3  0xb66cc9c6 in ?? () from /usr/lib/libQtCore.so.4
#4  0xb66d685e in ?? () from /usr/lib/libQtCore.so.4
#5  0xb66731b5 in start_thread () from /lib/libpthread.so.0
#6  0xb5a8838e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb49f6700 (LWP 12700)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb5a50e96 in nanosleep () from /lib/libc.so.6
#2  0xb5a50c7e in sleep () from /lib/libc.so.6
#3  0xb6dce9ba in ?? () from /usr/lib/libkdeui.so.5
#4  0xb6dcf3ec in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb0bea757 in DwEntity::Headers() const () from /usr/lib/libmimelib.so.4
#7  0xb0eaeed5 in ?? () from /usr/lib/libkmailprivate.so.4
#8  0xb110960b in ?? () from /usr/lib/libkmailprivate.so.4
#9  0xb0fa8bf3 in ?? () from /usr/lib/libkmailprivate.so.4
#10 0xb0fb3e0a in ?? () from /usr/lib/libkmailprivate.so.4
#11 0xb0fa5078 in ?? () from /usr/lib/libkmailprivate.so.4
#12 0xb0fa5290 in ?? () from /usr/lib/libkmailprivate.so.4
#13 0xb0fa5abd in ?? () from /usr/lib/libkmailprivate.so.4
#14 0xb0f9d565 in ?? () from /usr/lib/libkmailprivate.so.4
#15 0xb0fb34ea in ?? () from /usr/lib/libkmailprivate.so.4
#16 0xb67db580 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#17 0xb67dc302 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#18 0xb119d163 in ?? () from /usr/lib/libkmailprivate.so.4
#19 0xb11a85c1 in ?? () from /usr/lib/libkmailprivate.so.4
#20 0xb11acec4 in ?? () from /usr/lib/libkmailprivate.so.4
#21 0xb67db580 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#22 0xb67dc302 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#23 0xb69e55d3 in KJob::result(KJob*) () from /usr/lib/libkdecore.so.5
#24 0xb69e5a79 in KJob::emitResult() () from /usr/lib/libkdecore.so.5
#25 0xb7003065 in KIO::SimpleJob::slotFinished() () from /usr/lib/libkio.so.5
#26 0xb7004633 in KIO::TransferJob::slotFinished() () from /usr/lib/libkio.so.5
#27 0xb70056bb in KIO::TransferJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#28 0xb67db580 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#29 0xb67dc302 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#30 0xb70b3107 in KIO::SlaveInterface::finished() () from /usr/lib/libkio.so.5
#31 0xb70b5d5f in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /usr/lib/libkio.so.5
#32 0xb70b3717 in KIO::SlaveInterface::dispatch() () from /usr/lib/libkio.so.5
#33 0xb70a6030 in KIO::Slave::gotInput() () from /usr/lib/libkio.so.5
#34 0xb70a63a3 in KIO::Slave::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#35 0xb67db580 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#36 0xb67dc302 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#37 0xb6fd0887 in KIO::Connection::readyRead() () from /usr/lib/libkio.so.5
#38 0xb6fd22b3 in ?? () from /usr/lib/libkio.so.5
#39 0xb6fd2906 in KIO::Connection::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#40 0xb67d471b in QMetaCallEvent::placeMetaCall(QObject*) () from /usr/lib/libQtCore.so.4
#41 0xb67d6281 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#42 0xb5d5b8fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#43 0xb5d6375e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#44 0xb6d6292d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#45 0xb67c6961 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#46 0xb67c75d5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#47 0xb67c77cd in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#48 0xb67f136f in ?? () from /usr/lib/libQtCore.so.4
#49 0xb51729a8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#50 0xb5176063 in ?? () from /usr/lib/libglib-2.0.so.0
#51 0xb5176221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#52 0xb67f0fb8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#53 0xb5df4785 in ?? () from /usr/lib/libQtGui.so.4
#54 0xb67c501a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#55 0xb67c51da in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#56 0xb67c7895 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#57 0xb5d5b777 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#58 0x0804bf8f in _start ()


When kmail is start from the commandline I get the following output:
# kmail
kmail(12847)/libakonadi Akonadi::Control::Private::exec: Could not start/stop Akonadi!

How to debug, or what to do to get out of this situation (misery)?
Comment 2 Jaime Torres 2009-01-08 10:23:48 UTC
Do you still get empty body emails with a more recent kmail version?

Please, only one bug in one report.. (in any case, the backtrace contains insuficient information)
To get usefull backtraces, you should compile kmail using the build type debugfull
http://wiki.kde.org/tiki-index.php?page=KDE+CMake+Intro
Comment 3 Richard Bos 2009-01-08 10:47:00 UTC
> Do you still get empty body emails with a more recent kmail version?

After an system restart, it works again....
I'm not sure, but it looks like it is related to akonadi (I have been
told, that kmail does not use akonadi yet, but still I see signs that
this is the cause).  When starting kmail, it complains that akonadi
can not be started, after that the email body part is not shown.
After a full system restart, akonadi(console) works again and kmail
shows the email body parts too....
Perhaps this is because my home directory is stored on an nfs server?
(The full system start, is a restart of the desktop system and the
nfs server.  Not sure if this is really the solution, but it happened
twice now, and both times it was solved this way)

> Please, only one bug in one report.. (in any case, the backtrace
> contains insuficient information) To get usefull backtraces,
> you should compile kmail using the build type debugfull
> http://wiki.kde.org/tiki-index.php?page=KDE+CMake+Intro

I use rpms provided by openSUSE.  I wonder for which functions the
symbols are missing, can you see that?  Are they missing for QT, or
is it kmail (kdepim)?  I probably still need to install the related
debuginfo packages....
Comment 4 Jaime Torres 2009-01-08 11:24:44 UTC
* kmail in 4.2 does not requires akonadi. But if it is there, it is used, and once the mail database has been converted, it is used.
  in 4.3 it will be required.

* the akonadi database is stored somewhere in the home directory, so this could be the cause.

* you're missing the kdepim debug symbols.

Comment 5 Richard Bos 2009-01-09 16:38:21 UTC
It happened again; I powered down my desktop computer to leave, and left the
nfs server running.   After I cam back I switched on, the desktop system.
After logging, kmail did not show the email body part reported that it could
not start akonadi.  After stopping the desktop system and rebooting the nfs
server all is working again...
Comment 6 giuseppe 2009-01-11 09:11:36 UTC
*** Bug 180287 has been marked as a duplicate of this bug. ***
Comment 7 giuseppe 2009-01-11 09:12:39 UTC
Still unfixed on kde 4.2 rc1 from
websvn tag
Comment 8 Jaime Torres 2009-01-11 12:04:53 UTC
This could be due to a mysql bug with nfs..

"Just doing a cp -a on the file to a different filename and moving that new file to replace the locked file did the trick. This needs to be done to all innodb data files and the innodb log files. Whew!"


Could you paste the akonadi log when this happens again?
Comment 9 Dario Andres 2009-05-17 01:28:39 UTC
Any news on this ? Thanks
Comment 10 Richard Bos 2009-05-17 21:29:11 UTC
@Dario: why do you ask?  I Returned to just resources, without akonadi as middeleware, and since I haven't seen the problem.  Perhaps it is due to the fact that I have my /home mounted on an nfs3 filesystem.  I read somewhere, some time ago that I believe akonadi has problem with this.  NFS4 should be better in that respect.
Comment 11 Dario Andres 2009-05-31 01:25:05 UTC
I asked because I wanted to know if there was activity in this bug report, to close it :P
Now that you are not using Akonadi you will not be able to provide a log for comment 8, anyways the bug may still be there. Let's wait a bit.
Regards
Comment 12 Thomas McGuire 2009-12-01 11:19:38 UTC
This bug is unrelated to Akonadi, KMail only uses Akonadi for address stuff.
Looks more like an corrupted index file to me, or some other IMAP problem.
Comment 13 Björn Ruberg 2010-02-03 21:15:32 UTC
Have never experienced this. I'm closing - when you experience this in KDE 4.3+ again, please report.