Bug 178459

Summary:	All mail message columns being displayed
Product:	[Unmaintained] kmail	Reporter:	Blackpaw <lindsay.mathieson>
Component:	new message list	Assignee:	Szymon Stefanek <pragma>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	frank78ac, kde-bugs, simon, yallaone
Priority:	NOR
Version:	1.10.92
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Blackpaw 2008-12-22 13:06:22 UTC

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

On a regular basis - about every 1 in 3 startups *all* the message list columns will be enabled and displayed, scrunched up in the list window. I then have to manually uncheck them or use "Show Default Columns".

I have only seen this behaviour since the 4.2. beta 2. Unfortunately I have figured out what triggers it. I am getting occasional black screens on shutdown, which is also new to the 4.2 Beta 2 - maybe its related?

Comment 1 Thomas McGuire 2008-12-22 14:29:23 UTC

I've seen this as well, but only when KMail was used inside of Kontact.

Comment 2 Blackpaw 2008-12-22 15:22:11 UTC

(In reply to comment #1)
> I've seen this as well, but only when KMail was used inside of Kontact.
> 

Yes, it is kmail within kontact.

Comment 3 Thomas McGuire 2009-01-04 14:19:48 UTC

*** Bug 179349 has been marked as a duplicate of this bug. ***

Comment 4 Fred van Zwieten 2009-01-15 15:30:15 UTC

This still exists in KDE 4.2 RC1, Kontact 1.3. It seems like a Kontact problem, because aKregator inside Kontact has the same issue (see bug 180726)

Comment 5 Thomas McGuire 2009-01-25 22:50:41 UTC

*** Bug 181681 has been marked as a duplicate of this bug. ***

Comment 6 markuss 2009-01-26 09:20:34 UTC

This is a duplicate of Bug 178154 and it also affects the other Kontact apps. I can at least confirm this for Akregator.

Comment 7 Frank Reininghaus 2009-02-15 16:04:14 UTC

(In reply to comment #6)
> This is a duplicate of Bug 178154

you're right, marking as duplicate.

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