Announcement

**Snowhog** · Nov 17, 2008, 05:19 PM

Re: not able to log in to KDE

You appear to have a single partition being used for your Linux OS, which is 12G in total size, of which, 11G have been used. Reboot and select the second entry from the Grub menu. This will be a recovery mode kernel, and you will end up at the CLI as root.

Type:

Code:

apt-get autoclean
apt-get autoremove
apt-get clean

Then type:

Code:

df -hTxtmpfs

and check the Used and Use% values. If the Used% shows 10G or less, you should be able to get back into your GUI desktop. To restart, type:

Code:

shutdown -r now

This will reboot your PC.

**ejt** · Nov 17, 2008, 05:31 PM

Re: not able to log in to KDE

I have already done the apt-get autoclean and the rest from the user in CLI. Will doing these commands from root work better?

**Snowhog** · Nov 17, 2008, 05:35 PM

Re: not able to log in to KDE

They have to be done as root - a 'non-root' user (or without sudo privileges) can't run the commands.

So are you saying, that after running these three commands, you still have 11G of used space on your 12G single partition? I'll assume 'yes.'

How many kernels do you have installed? From the CLI:

Code:

ls -l /boot/initrd*

If you have more than one version, you can uninstall one (or more) of the older ones. Note I said uninstall - do not just delete any of them!

**ejt** · Nov 17, 2008, 05:58 PM

Re: not able to log in to KDE

OK so at the CLI it has my user name and when I ls I see just those dir in the home dir. If I "/" I get to where I can ls and see (I think) home, user ,var etc. . Yet I did sudo apt-get and df from the first one and things seemed to work. By the way, I did not have to enter a password to sudo anything? As far as kernels are concerned, I did a total install (no windows) from a friends' gg image then an upgrade to hh when it came out a few weeks or months ago (time flies). I'll try doing as you say tomorrow, that computer is at my office, but to uninstall not delete do you mean something like sudo apt-get remove version*? Hope you can understand what I'm trying to explain.

**Snowhog** · Nov 17, 2008, 08:00 PM

Re: not able to log in to KDE

Yes. (...but to uninstall not delete do you mean something like sudo apt-get remove version*?) Use Adept Manager or Synaptic (I like Synaptic a whole lot better in 8.10 than the current Adept Manger. If you don't have Synaptic installed, I'd recommend doing so. It's available in Adept manager, or you can install it from the CLI:

Code:

sudo apt-get install synaptic

In Synaptic, search on linux-image-x.x.xx-x-generic where x.x.xx-x is the oldest kernel in your /boot directory click on the Status box (green) and click Mark for Complete Removal. WARNING: DO NOT DO THIS IF YOU HAVE ONLY ONE KERNEL VERSION INSTALLED!

For reference, see Rog131's HOWTO: Removing unnecessary entries from the grub menu list

"By the way, I did not have to enter a password to sudo anything?" This is correct when you boot into Recover Mode. In this mode, you are running 'as root' so sudo isn't required to execute commands requiring root privileges.

**ejt** · Nov 17, 2008, 09:12 PM

Re: not able to log in to KDE

OK, I think I saw somewhere that I had 3 or 4 different kernel choices (I can't remember where right now but the list on Rog131 link looked familiar). I have adept and synaptic installed, but how do I use them if the only thing I can use is the CLI? I don't know how to get to either one except from the menu. How much memory do the kernels use? Should I uninstall all but the most current kernel?

Is apt-get remove a CLI way of using adept? If so, what is the synaptic way of doing it? And is remove the same as uninstall or delete? I don't know what I'm doing

**Snowhog** · Nov 17, 2008, 09:22 PM

Re: not able to log in to KDE

You can use apt-get remove linux-image-x.x.xx-x-generic (where x.x.xx-x is the oldest kernel in your /boot directory). I'd start by removing just the oldest one. Then, afterwards, run apt-get autoclean, apt-get autoremove and apt-get clean. Then, df -hTxtmpfs to check on how much space you've recovered. If you get below 11G used, then shutdown/restart with shutdown -r now and boot into the first kernel in the menu, and see if you can login normally and get to the desktop. If you can, use Synaptic to remove the other older kernels. Rule of thumb is to keep the current and first prior kernel versions installed on the system.

**ejt** · Nov 17, 2008, 09:28 PM

Re: not able to log in to KDE

Ok I think I've got it

. 1 more question tho, how do I know if I am booting to the 1st kernel or will that be obviouse when I shutdown -r?
Thanks again, I really appreciate your time and energy.
ejt

**Snowhog** · Nov 17, 2008, 09:29 PM

Re: not able to log in to KDE

It'll be the first entry in the Grub boot menu that you see.

**ejt** · Nov 17, 2008, 09:34 PM

Re: not able to log in to KDE

8) if all this works I'll send you a box of candy, and hopefully I can write "solved" tomorrow

**mahutchinson** · Nov 18, 2008, 03:25 AM

Re: not able to log in to KDE

The amount of space you have in total is very small - about the same as is recommended for the root and swap partitions, without any data.

**Fintan** · Nov 18, 2008, 04:17 AM

Re: not able to log in to KDE

I concur with mahutchinson.

I would definitely have a look here:
http://www.psychocats.net/ubuntu/separatehome

There are other ways but this will give you the general idea. It saves a lot of agro.

Having a separate /home has a lot of advantages and no disadvantages

I fact *ubuntu should offer to set up a separate /home partition but doesn't

**ejt** · Nov 18, 2008, 09:31 AM

Re: not able to log in to KDE

Thanks for the tip, I'll definitely look into it if I can ever get back to a useful OS.
As of now, after uninstalling all but 2 of the most current kernels, the df code is show that I have 12g total 11g used, 1.2g avail, at 90%. I still boot into the CLI.
I spent hours yesterday rm many files from my backup dir, but curiously when I ls that dir I saw a dir named "My Documents" which I know came over from my windows migration. And I know there are many large file that could be deleted to give me more room, but when I cd to get to that dir the message is "dir not found". I've tried "My Documents", "my documents", "My-Documents", "MyDocuments", "my", "My", "documents", basically every combination I can think of. I can cd into all the other dir in the backup dir except that one. Has anyone run into this before?
Also, is there anyway to rm a dir even if there are files and dir still in it? That would save me so much time.
Thanks

ps. sorry snowdog, no candy yet!

**Fintan** · Nov 18, 2008, 09:47 AM

Re: not able to log in to KDE

I don't have a lot of time right now but if you can get yourself a copy of the latest gparted live cd:
http://gparted.sourceforge.net/download.php

there is a lot of usefull partitoning info there as well.

Start it up and see if you have enough space for a new partition lets say 6-10gig (we can make that bigger later as needed)
if you do make a partition and format it as ext3 and label it home.

after that boot up with a live cd of your choice, mount your new partition and move all your DATA files from your present /home to this new partition. Leave the rest in place for the moment.
This should release some space.

If that works, great.
You can then go about making a separate /home for your installation as described in the link above.

If it doesn't get back to us and we will see what should be done.

Announcement

not able to log in to KDE <SOLVED>

not able to log in to KDE <SOLVED>

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment