Summary: | migration from KDE 3 to KDE 4 kmail identities and so on | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Frank Andreas <knarf12> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | jezuch, krammer |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Frank Andreas
2009-01-14 15:54:46 UTC
Please check if KDE4 is properly configured to use the same local prefix, e.g. by running % kde4-config --localprefix That should be the same as running % kde-config --localprefix If it is not, e.g. the KDE4 one being $HOME/.kde4 and the one for KDE3 being $HOME/.kde then the distributions upgrade tool/script did not properly copy/link the files to the location they chose. In which case it might be better to file a buf report on their bug tracker. I don't know if it changed in KDE 4.2, but copying kmail files from ~/.kde to ~/.kde4 does not work (or at least did not work last I tried). So I'm gonna have to vote for this bug and hope for a less painful migration :) Can you check if it works if you remove/move .kde4 and copy the whole tree before starting KDE4? KDE uses .kde in both versions and therefore all upgrade facilitied assume they have access to the older version's files. If a distributor decides to use different prefixes, it is up to them to provide migration tools. *** This bug has been marked as a duplicate of bug 169827 *** Amazing! It worked! :D Honestly, I don't know what to say ;) |