Mailinglist Archive: opensuse-kde (180 mails)

[Sabine Konhaeuser <sjmk@xxxxxxx>]

On Friday 20 January 2006 19:45, Curtis Rey wrote:
> On Fri January 20 2006 09:11, Sabine Konhaeuser wrote:
> > On Friday 20 January 2006 02:10, Joshua Raphael Fuentes wrote:
> > > funny.. I never had that problem on my SUSE 10. But if those cases
> > > happen, it's always good to do a refresh on you KDE, or if not, you can
> > > always revert back to it's first run by deleting .kde inside your home.
> > > You will be left with defaults by then, so which means you will be
> > > spending time configuring and making adjustments to meet your desires.
> >
> > Well, deleting .kde is not really an option for me, since I have way to
> > many things configured the way I want it, and bringing it all back is
> > just not something I want to deal with (unless it's absolutely
> > necessary). Deleting single config files is a different thing though. The
> > days when I didn't mind fiddling hours with my computer are gone ;-).
> >
> > Cheers,
> > Sabine
>
> Well, the suggestion by Mr "sargon" is not entirely without merit.  If you
> learn which key files you "really" need (such as mail
> settings/config/filters/etc and other basics like konq settings and
> bookmarks, ad infinim) and move these key files over first one by one (or
> in the case as something like kontact settings verses KMail settings - can
> move most/all the KMail settings) then reboot and see if it fails/bad
> behavior returns.  I have had to any more than one occasion had to rename
> my .kde dir to ~kde and then do just what he's suggested.
>
> Also, sometimes clearing out the /tmp file helps with killing the simlinks
> that are in the ".kde" dir in your $HOME/ dir.  They are those
> "socket-<hostname>" and "tmp-<hostname>" files.  I usually don't mess with
> the "cache-<hostname" and it's often still viable.  If you do rename you
> $HOME/.kde to something like ~kde then I alway delete all the symlinks in
> that directory (e.g. "rm *-<hostname>" removes all three files).
>
> Caveat:  If you do something (as root) link; (w/o the #)
>
> # rm -rf /tmp/*
>
> and then;
>
> # rm -fr /tmp/.* (complains about not being able to rm "." and ".." dirs =
> ok)
>
> This clears out all the files but I recommend if you take out the
> ".X11-unix" and the ".ICE-unix" directorys you need to restart the Xserver,
> either by "ctrl+alt+backspace" in the kdm user login screen or I prefer to
> login root at tty1 and issuing an "init 3" or "telint3" to bring X all the
> way down and any possible things that might be hanging around.  Keep in
> mind you setup, such as allowing remote access for admin, database, etc.
> etc. etc... You may need to reboot.  Some insist that this doesn't need to
> be done, but I've found that in some cases it resolves certain issues. 
> Also check the permissions as well.  I have some fun with that after the
> upgrade.  I logged into kde root, /home/<user> and gave  my user acct all
> the permission recursively, then login to kde as user and repeat this - and
> certian locked files seem to unlock (and I think I renamed a file that
> kmail complained about).
>
> Just my $0.02.  Curtis

Hi,

these are all steps I more or less do when I install a new SUSE or a new 
version of KDE (3.3 to 3.5 for example). Usually I do not have any problems 
when applying some minor updates (knock on wood). If the problem would have 
been a big one, I even might have done it now, but not for such a small thing 
like a background image hickup.

Thanks for all the tips though. It's appreciated, and will come in handy.

Cheers,
-- 
Sabine