cleaned up /tmp now can't get into kde

fobius · 01-05-2005, 01:57 AM

hey guys,

i recently had a problem where I was unable to update my packages using swaret because /tmp had become too full. So looking around, it seemed like a good idea at the time to just remove the stuff in /tmp. But after I did that, I can't seem to startx anymore or use vi among other things. Is there any way to recover from this?

thanks

masand · 01-05-2005, 02:01 AM

what errors u r getting??
please post them....

regards

shilo · 01-05-2005, 01:10 PM

Does this persist across reboots? I wonder because I frequently use the following commands and have no problems.

Code:

cd /tmp
rm -r *
rm -r .*
reboot

Does that work for you?

fobius · 01-05-2005, 11:03 PM

hey guys,

I tried what you suggested shilo, and I still am unable to start kde. If I try to start kde, I get an error message saying that /tmp is too full, although there's nothing in it. If I try and use vi, I get an error message saying "blkopen's read failed." How do I let the system know that /tmp is available?

Also, I installed kde in a separate partition, /opt

Thanks

leonscape · 01-05-2005, 11:38 PM

If vi isn't working you might have done some damage to your system. Have you deleted /tmp itself?

fobius · 01-05-2005, 11:53 PM

Nope...even when I try to start firefox, I get an error about a bad resource request...is it time for a reinstall?

uselpa · 01-06-2005, 01:39 AM

leonscape asks the good question: did you delete /tmp itself, i.e. did you do a "rm -rf /tmp" ?

fobius · 01-06-2005, 01:41 AM

nope..

Cedrik · 01-06-2005, 02:25 AM

Did you try as root :
chmod ugo+rxwt /tmp

fobius · 01-06-2005, 10:35 AM

hmm i haven't tried that yet but I tried listing to permission of /tmp, which was drwxrwxrwxt, still same problem..

Genesee · 01-06-2005, 04:53 PM

what does "df" give you for free space?

EDIT: also, did you try doing "swaret --purge" ?

jimbob1234 · 01-06-2005, 11:55 PM

I did the same thing, starting KDE as root fixed things for me. I hope it does the same for you.

fobius · 01-07-2005, 01:08 AM

Hey guys,

Thanks for all the suggestions. Interestingly enough, when I do

Code:

df

It shows that / is 100% even though I cleared tmp. I can't provide the output since I can't start X pretty much. I tried to start KDE as root and I got a message saying that xauthority couldn't be found. I even deleted /tmp and recreated it, setting on permissions as Cedrik suggested, still no luck, KDE still complains that /tmp is out of space.

I rebooted into Mandrake and ran fsck on /dev/hda1 (where Slack is installed) and that didn't help either

Cedrik · 01-07-2005, 06:18 AM

Try :
mkdir /tmp/.X11-unix
mkdir /tmp/.ICE-unix

chmod -R ugo+rxwt /tmp

Genesee · 01-07-2005, 09:50 AM

Quote:

Originally posted by fobius
Hey guys,
It shows that / is 100% even though I cleared tmp. I can't provide the output since I can't start X pretty much. I tried to start KDE as root and I got a message saying that xauthority couldn't be found. I even deleted /tmp and recreated it, setting on permissions as Cedrik suggested, still no luck, KDE still complains that /tmp is out of space.

Hi fobius -

you will have problems starting X/WM if there's really no space on the device - did you check to make sure swaret wasn't retaining all the d/l'ed packages? run it with the "--purge" option to see if that helps. if not, check that the space isn't being used elsewhere, inside /var would be a good place to start, using "du -h". I'm not sure on this, but kde may be referring to another tmp directory? - there are several possibilities, but that will depend on your system so try looking around....