Version: (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages I have the following problems with the new message list/classic theme (was working in kde 4.1): (my columns are: sender, receiver, subject, date, size) - column sizes are reset when kmail is restarted - the subject column is always moved to the first position after a restart - the subject column includes a 'tree line' even though I have selected 'flat date view' - the custom font settings are ignored (e.g. I have selected a bold font for new messages)
I am having some similar problems on Kubuntu Intrepid (32-bit) using KDE 4.2.00 and KMail 1.11.0, as follows: (1.) "column sizes are reset when kmail is restarted" - this happens to me too, but not every time. Perhaps once in every five KMail restarts. I haven't found a pattern to it (yet). (2.) "the subject column is always moved to the first position after a restart"- yes, I get see this behaviour too when I get problem (1.) (3.) "the subject column includes a 'tree line' even though I have selected 'flat date view'" - I DON'T see this behaviour on my setup (4.) "the custom font settings are ignored (e.g. I have selected a bold font for new messages) - I have this problem too - I think its already reported as bug 178402 (?)
Edit: Re: point (3.) in my previous comment - sorry, I didn't understand what was meant by a "tree line" - yes, I DO see this behaviour. It also has the unwanted side effect of making the line spacing in the message list larger than the line spacing in the folders list, which makes the interface look inconsistent. (Everything looks and works OK though in KMail v1.10.4 on GNOME 2.24, Ubuntu 8.10 Intrepid)
Please only report one bug per report. Most of the problems have already been reported: (1) column sizes, bug 142609 (2) moving columns doesn't work at all currently, bug 187217 (3) tree lines in flat view, bug 181794 (4) custom fonts are ignored, bug 178402 I'm marking this bug a duplicate of the first one mentioned. Please CC yourselves to the other bugs if you want to follow them. *** This bug has been marked as a duplicate of bug 142609 ***