| Summary: | kmail won't open without a .kde folder | ||
|---|---|---|---|
| Product: | TDE | Reporter: | paulatgm |
| Component: | tdenetwork | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED INVALID | ||
| Severity: | enhancement | CC: | bugwatch, darrella |
| Priority: | P5 | ||
| Version: | 3.5.10 | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
paulatgm
2009-01-02 13:43:07 CST
Confirmed. It looks like all of the KDE PIM applications are ignoring the KDEHOME environment variable. After much debugging, I found the answer. 1. You are running an upgraded system (not a clean installation of KDE3 from scratch) 2. kmail, knotes, and a few other applications leave full paths (!) in their configuration files 3. kmail (or other app) has been run at least once under the old ~/.kde based installation The fix is easy: just open ~/.kde3/share/config/kmailrc and change the path that contains .kde to contain .kde3 instead. If you like, you can do a search in the ~/.kde3/share/config directory for all text files containing .kde/ and it will show all the configuration files that have this problem. Sorry I had to file a bug on this, but maybe someone else will learn from it. You're correct. Here's the offending line from .kde/share/config/kmailrc: folders[$e]=$HOME/.kde/share/apps/kmail/mail But, actually, I did not upgrade. Instead, I copied my hardy kde3 ~/.kde to the intrepid ~/.kde3. I don't actually use kmail, but it must have set up a config some time ago in hardy. FWIW, They can be found with: $ grep -ir '\.kde/' .kde3/ and fixed with: $ perl -i -p -e 's/\.kde\//\.kde3\//g;' .kde3/share/config/kmailrc regards, |