/tmp
 

I am in a bit of a pickle.

Running Slack 10.2 with KDE and have 5 users set up.
A couple of days ago I attempted to log my kids into their profile with no success. An error appeared explaining a problem with KDE and how it could not start. At the time I did not think of it, and was not bothered to attempt to troubleshoot.
Today (4 days later) I tried to sign into my user with a similar error from KDE say that the temp (/tmp) directory was full and could not load.
My first instinct told me to log into /root (which I did) and delete any files within /tmp. But it would seem that did not work.
I am still getting told that the /tmp directory is full and can not log into any user other than root.

Two questions:
1) what can I do to rectify my login issues
2) and is there a way to enlarge the /tmp directory without reinstalling?

One, did you delete HIDDEN files within /tmp

Two, what does "df -h" show, i.e. how much free space HAVE you got?

The chances are there's something taking up an awful lot of space and you just literally haven't got enough room in /tmp for everything that wants to use it - this is really strange as it rarely needs more than a few hundred megs. That probably means your hard disk is full up completely. Try deleting those MP3's and ISO's. :-)

Did you upgrade your x11 to version 6.9.0 before this happened for first time? If so then it's due to a fault in the new x11 package. You can run:
to see if that solves your problem.

If you have enough RAM, you could use tmpfs. It will expand as neccessary as long as there is enough virtual memory, and clear out when you shut down as recommended by the FHS. Since it is in memory, it will be much faster than a disk based /tmp.

bathory:

For my own info, what does running
do and how will this sort out the original problem?

Cheers

There was a prob with the first x11-6.9.0 slack pagkage, that when you try to run X as normal user it could not create the necessary temp files to run. So perhaps that's the case here, since the thread starter can run X as root but not as normal user. With this command you turn the setuid bit on so you can run X as you were root.

Regards