Ben Jones kirjoitti (l�hetysaika lauantai, 7. helmikuuta 2004 05:32): > I just upgraded to kde 3.2.0, and I just know I've missed something > crucial. My kicker etc was still the 3.1 version, so I mv'd by ~/.kde to > ~/.kde-BAK.
~/.kde is just a symlink to ~/.kde3.* I don't exactly know what moving the symlink would cause, but in any case it's not a smart move. > Then restarted X... and kicker didn't start. It was still > looking for libs in /usr/kde/3.1/*. For now I just just "mv /usr/kde/3.1 > /usr/kde/2.1-foo ; ln -s /usr/kde/3.2 /usr/kde/3.1" but I dimly remember > the last major release I had to edit a config file somewhere or something - > does this ring any bells for anyone? It's possible I did something really > hacky I'm paying for now I guess... Ok, now your system's really screwed up. First, log out of KDE and into a console with root. Then remove the symlink from /usr/kde/3.2 to /usr/kde/3.1 and restore KDE-3.1 to it's original directory. Then move ~/.kde3.1, ~/.kde3.2 and ~/.kderc somewhere else. Next login to KDE (and be sure to select kde-3.2.0) and start meddling around with the GUI settings. I'm not sure to what extent you can use the old config files. Bookmarks, calendar and such should be fine, but others might screw up the system. -- Jani-Matti H�tinen "Mumbo? Perhaps. Jumbo? Perhaps not." -- [EMAIL PROTECTED] mailing list
