I'm in too minds about this issue.
OpenSUSE has a reputation of being very stable and reliable. Past history has shown that upgrades are well thought out. Should components such as KDE be lacking in quality, OpenSUSE normally includes ways to mitigate the issue. For example, in the past some OpenSUSE versions included multiple of KDE versions. Given that kmail remains one of the most popular KDE applications, it was surprising and disappointing that users were left to fend for themselves.
On the other hand, it was not to hard to figure out how to re-enable the 11.4 repo and grab the previous kmail from there. See
And then lock the packages in place to prevent any upgrades.
In summary, I don't think a broken Kmail was something that should have shipped without clearly providing an alternative or pointing out some way to mitigate the issue - some release notes could have covered it.
Long term, I hope kmail2 improves or kmail forks.
On Sat, 25 Feb 2012 03:14:09 C wrote:
On Fri, Feb 24, 2012 at 15:02, Stefan Gofferje email@example.com wrote:
On 02/24/2012 12:07 PM, C wrote:
KMail is well known to be problematic in KDE4... You can't really blame openSUSE on something that is an issue with upstream KDE. If you go to any other distro that is shipping the *same* release of KDE4, you will find similar if not identical issues with KMail.
KMail2 ist not the only problem in 12.1, as the list archive and various reviews in the web show. The whole release was composed too fast and not thoroughly checked before releasing. And nobody forced SuSE to go from Kmail to KMail2.
??? Think about what you wrote there... nobody forced you to use KMail2. KMail2 is part of KDE4... if you have problems (most of which are probably very well documented and have bug reports open on them) then you can either help fix it... or use an alternative - of which there are many.
Show me a single release of ANY Linux distro (or ANY other OS by any other commercial OS vendor) that doesn't have list archives and various reviews on the web that point at flaws. You can't. If openSUSE was held back and not released until everything was 100% perfect we'd still be waiting on release 1.0.