On Friday 20 August 2010 08:46:29 Per Jessen wrote:
One of my 11.3 test-systems filled up a disk with /tmp/kde-per/kconf_updateNNNNNN.tmp files - they appear to be empty, so I'm just going to delete them, but what's happening?
kconf_updates are scripts that are evaluated on login to see if configuration needs updating due to a new software version. Each app can install scripts that modify its existing config files. $HOME/.kde4/share/config/kconf_updaterc contains the state of the update system (scripts should only run once). /home/per/.kde4/share/apps/kconf_update/log/update.log is the log of activity. (KDE3 has the same mechanism, if you are still using it or its apps, check $HOME/.kde/.... as well). Apparently something is going wrong and the temporary files are spamming your disk. Does the log give any clue to repeated, failed update attempts? Otherwise it could be hard to track down the app that is causing the failures since the filenames themselves don't identify the app and are empty, so we will have to detect it indirectly. Are all the temp files recently dated, or have they accumulated over time? Can you link them to any recent app you installed? Are you using any 3rd party repositories or applications? Can you compare the installed kde app set to another system that doesn't exhibit this behaviour? Will -- Will Stephenson, openSUSE Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org