Bug 301709

Summary:	KMail2 - Message list geometry not remembered
Product:	[Applications] kmail2	Reporter:	leo_rockway <leo>
Component:	message list	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED FIXED
Severity:	minor	CC:	montel
Priority:	NOR
Version First Reported In:	4.9 pre
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	4.9
Sentry Crash Report:
Attachments:	KMail2 Message List

Description leo_rockway 2012-06-12 08:06:35 UTC

The geometry of the message list is not remembered between invocations of KMail2. The staring height of the message list is too small (in my case) and I always have to make it larger. The size should be remembered.

Reproducible: Always

Steps to Reproduce:
1. Open KMail2
2. Resize message list
3. Close KMail2
4. Open KMail2
5. Find that the message list size that we set on step 2 is not remembered
Actual Results:  
The message list geometry is not remembered

Expected Results:  
The message list should appear the same after reopening KMail2

I have seen this behaviour on previous versions. This is not something new in KDE SC 4.9 beta 1.

Comment 1 Laurent Montel 2012-06-13 10:23:01 UTC

It works fine here.
I resize and I close and it's restore.
Can't reproduce it

Comment 2 leo_rockway 2012-06-14 03:44:29 UTC

I deleted my ~/.kde4/share/config/kmail2rc thinking that maybe I got something in there that causes this behaviour, but the same thing happens with a fresh config file. Anywhere else I could look to see what's going on? The only things I change from the default configuration is having short folder list and to never show favourite folders view.

Comment 3 Laurent Montel 2012-06-15 06:44:47 UTC

Screenshot to show what it bad. Perhaps I don't understand your bug

Comment 4 leo_rockway 2012-06-16 03:32:30 UTC

Created attachment 71864 [details]
KMail2 Message List

The message list geometry is not remembered.

Comment 5 Laurent Montel 2012-07-24 08:20:48 UTC

OK I just fixed same bug yesterday.
Sorry I forgot to read it.
But it's fixed now.
(in 4.9)

Thanks for reports