--===============0794884415== Content-Type: multipart/alternative; boundary="-----------------------------1090010583" -------------------------------1090010583 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Thanks for your reply. It was partially helpful. What is the "RMB context menu?" I tried copying the IconPositions file to a new location, then deleting it. KDE builds a new one, but with the same problems. The icons still won't stay where I put them after a reboot (after logout and log on , yes). Just for fun, I tried to make the IconPositions file read only -- so that KDE wouldn't overwrite them after rebooting. It seems to work. But is it dangerous, do you think? I suppose it just means that any folders created on the desktop won't be there after a reboot? I don't really know. I'm going to test it now. Andy Liebman tyrerj@acm.org writes: Do you have the icons aligned to a grid. If so, doing it again with the RMB context menu might help. This information is stored in the file: $HOME/.kde/share/apps/kdesktop/IconPositions Make sure that the permissions for this file are: 600, and that the permissions of the directory: .kde/share/apps/kdesktop are: 700 If that is OK, then try renaming the file. Using the date as an extension is a good idea (e.g. IconPositions.20040716). I keep one of these in case of problems. Then after you rename the file and see if you get a new file: "IconPositions" when you log out and log back in. If so, that should fix it. If not, then you have some serious problem. :-( -------------------------------1090010583 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
Thanks for your reply. It was partially helpful. What is the "RMB conte= xt menu?"
 
I tried copying the IconPositions file to a new location, then deleting= it. KDE builds a new one, but with the same problems. The icons still won't= stay where I put them after a reboot (after logout and log on , yes).
 
Just for fun, I tried to make the IconPositions file read only -- so th= at KDE wouldn't overwrite them after rebooting. It seems to work. But is it=20= dangerous, do you think? I suppose it just means that any folders created on= the desktop won't be there after a reboot? I don't really know. I'm going t= o test it now.
 
Andy Liebman
 
tyrerj@acm.org writes:
Do you have the icons aligned to a grid. = If so, doing it again with the RMB
context menu might help.

This=20= information is stored in the file:

    $HOME/.kde/share/app= s/kdesktop/IconPositions

Make sure that the permissions for this file= are: 600, and that the permissions
of the directory:

   = ; .kde/share/apps/kdesktop

are: 700

If that is OK, then try re= naming the file.  Using the date as an extension is a
good idea (e.g= . IconPositions.20040716).  I keep one of these in case of
problems.=   Then after you rename the file and see if you get a new
file: "Ico= nPositions" when you log out and log back in.

If so, that should fix=20= it.

If not, then you have some serious problem. :-(
-------------------------------1090010583-- --===============0794884415== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________ This message is from the kde-linux mailing list. Account management: https://mail.kde.org/mailman/listinfo/kde-linux. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html. --===============0794884415==--