Bug 81083 - Message View Component does not appear : my messages are not readable !
Summary: Message View Component does not appear : my messages are not readable !
Status: RESOLVED DUPLICATE of bug 81798
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.6.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-07 11:50 UTC by Michel Nolard
Modified: 2007-09-14 12:17 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Nolard 2004-05-07 11:50:22 UTC
Version:           1.6.2 (using KDE 3.2.2,  (testing/unstable))
Compiler:          gcc version 3.3.3 (Debian 20040401)
OS:          Linux (i686) release 2.4.24-meg-12.1

KMail went right until a day, last week, when the message preview zone of the display disappeared without any reason. Until then, the only way to read my mails is to click on "reply"... which is not what we can call "a good solution".

I tried to change KMail's main window layout (with/without restarting kmail), I tried to double click on the mail (the box opened containing only the toolbar and a gread empty zone), I tried to disactivate the mime structure, to drag the splitter, ... nothing did the trick.

If I find what made the things bad like this, I promise to fill in a bug report explaining how to reproduce, but I can't even find how to have the preview back on the screen !

I am totally desesperate, can you help me quickly !

Chucky
Comment 1 Mirko Klemm 2004-08-16 22:43:04 UTC
I have the same problem, but in kmail 1.6.82
Comment 2 Jean-Marie Lambert 2004-11-16 15:37:37 UTC
I'm just having the same problem with KMail 1.7.1
Comment 3 Philip Rodrigues 2006-10-29 19:40:29 UTC
Does the same problem occur in the latest KMail?
Comment 4 Philip Rodrigues 2006-10-29 21:05:55 UTC
I think what's happening here is what's described in bug 81798, so I'll close this as dupe of that (since the description of the problem there is clearer).

*** This bug has been marked as a duplicate of 81798 ***