I'm not sure what category I fall into; whether in was a result of a bad update, or a "space" issue. I'm inclined to think it was the result of the update as this is a recent install of Kubuntu Edgy a few months ago. It has run perfectly until an automatic update the other night.

I turned this machine on and attempted to log-in as I normally would. The screen left as if to log in, and returned within 5 seconds to the Login Screen.

Being new to all things Linux, I'm at a loss. I've heard other mention "create another login", or..."clean up some disk space", in the event it was a lack of real estate, but not being able to do much beyond using the "esc" key at the post in an attempt to login from the command line, I'm a complete loss.

Does anyone have a solution or some "how too's" on this issue?

Thanks,

Tim

One option (you'll probably receive more) is to login at a text terminal:

<CTRL><ALT><F1> ( Same way as you'd do <CTRL><ALT><DEL> on that other OS ) will take you to a full-screen terminal. <CTRL><ALT><F7> will take you back to the KDE login screen (Try it now).

Do <CTRL><ALT><F1> to go back to the text login terminal

Now login as yourself

df -h will tell you how much disk space you have free
sudo init 1 will take you to single-user mode and stop the X server.
startx will now try to start the X server (& KDE). You will probably see helpful errors.

To turn your computer OFF safely, you may have to resort to sudo halt

This is a follow up to this thread: http://www.linuxquestions.org/questi...d.php?t=535181

An update was mentioned. If the kernel was part of the update there may still be some missing pieces that will be there in a day or two. You can select the previous kernel from the Grub Menu that comes up at boot time. That should get you working for now. I've seen this before on my system. I have an Nvidia card and the package for restricted modules isn't on the mirror site yet. This caused the Nvidia driver not to work because it was compiled with the prior version. Your situation may be different.

That's a viable suggestion fragos... Strange that it has happened with several of us over a month or so though :S

I didn't try using the older kernel; Next time I'm bored I'll do an update and see if it breaks, then try using the old kernel

Thanks for the help thus far.

I've done the CTRL-ALT-F1 and attempted to log in. This is what I receive: "configuration error - unknown item 'FAIL_DELAY' (notify administrator)"

Although, after which...it does appear to log me in after offering my password.

The machine dies (sits motionless for extended periods) after using the "sudo init 1" and I have to restart.

But, I have received this error message after using the aforementioned "startx" from the command line: "/usr/bin/startx: line 132: cannot create temp file for here document: No space left on device"

****
OH WAIT: (Notice I'm working on the machine while I post this...) I've found a list of needed command line prompts for Linux. I'm attempting to clean out the system, piece by piece,...little by little, removing what I can that might be taking up space. (I've only deleted those files in which I've created, added, or downloaded myself.)

Ok, apparently I'm only making matters worse. Now, after removing some files to eleviate some disk space problems (which apparently there was), I'm now getting a small command line box which takes up about 25% of my screen in the upper-left-hand corner that is empty with no apparent desire to go further. I still receive the "FAIL_DELAY" error as I reported above when to ALT-CTRL-F1 to log in.

So, while I think I know what started this whole mess, I'm now in dire straights to figure out how to climb my way out of the hole I've got myself into.

I did apparently manage to boot into an earlier kernel with 'recovery mode' selected. Although, it's "Ubuntu" instead of "Kubuntu". Wierd!

That is probably because you are in single-user command mode. It will do nothing, until you tell it something to do!

It sounds as though you have indeed run out of disk space. Linux generally allocates some disk space that is reserved just for root in case this happens. This allows root to login (even when no one else can), to clear up the mess. But I am not sure how kubuntu handles this, as kubuntu doesn't come with a root login by default.

You might be more comfortable working from a graphical environment. You'll remember that your original kubuntu install disk let you run it as a "Live CD". So boot from that into KDE, mount your HDD partitions, if they are not automatically mounted for you, and tidy up from there.

Then you'll need to find some extra HDD space, and move your current install to it.

As a matter of interest (it'll help later), what is the output of the following commands:

sudo fdisk -l ( That's a "minus ell" not "minus one" ! )
df -h

Would you like to clue us in?

I was speaking on the fact that I "ran out of diskspace" as the reason for what started it all. I didn't mean to indicate there was something else I didn't want to share. Sorry.

Ok, here's a new development:

After removing some files, it WILL log into Gnome just fine. It's KDE that is broken I'm thinkin'. Not sure of a repair solution. Anyone have anything on this?

By the way, here is what was recieved by using the above mentioned commands:

Disk /dev/hda: 20.4 GB, 20491075584 bytes
255 heads, 63 sectors/track, 2491 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 2385 19157481 83 Linux
/dev/hda2 2386 2491 851445 5 Extended
/dev/hda5 2386 2491 851413+ 82 Linux swap / Solaris
timba@kubuntu-desktop:~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 18G 4.9G 13G 29% /
varrun 237M 156K 236M 1% /var/run
varlock 237M 4.0K 237M 1% /var/lock
procbususb 10M 92K 10M 1% /proc/bus/usb
udev 10M 92K 10M 1% /dev
devshm 237M 0 237M 0% /dev/shm
lrm 237M 18M 219M 8% /lib/modules/2.6.17-11-386/volatile

Just curious...

I'm wondering if "marking for reinstallation" through the Synaptic Package Manager the kde-core K Destop Environment core modules might be worth considering? Or any such reinstallation via Synaptic? Because...I've got access to that via the gnome desktop.

Thanks. -Tim

OK, you have 13G free - plenty!
If you want to have a lot of large files again, I'd suggest you buy another disk, install it as HDB, and put your /home directory there (hope it's not a laptop!).

In what way is KDE "Broken"?

Sometimes "brokenness" is caused by an error somewhere in the /home/timba/.kde tree.
This can safely be renamed as something else, and it will be recreated with defaults next time you login to KDE. Sadly, you'll loose any customisation you have done to KDE, but that's not the end of the world

So try this:

Boot. Do NOT login at the graphical interface. <CTRL><ALT><F1> to get a console login, login as yourself. Then do the following commands:

mv .kde kde_old_config
exit
<CTRL><ALT><F7> to go back to the graphical login.
login to KDE.

Any better?

- Your post #11 : Yes you probably can "fix" KDE that way, but it may be simpler just to re-create the .kde directory.

Note, as this begins with a "." it is "hidden" by both ls and most filemanagers, unless they are configured to "Show Hidden Files" (Under "View" in konqueror).

[QUOTE=tredegar]- Your post #11 : Yes you probably can "fix" KDE that way, but it may be simpler just to re-create the .kde directory.QUOTE]

Tredegar: You Rock! Your solution worked fantasticlly. And, yes...I do need to rebuild my settings, but...I'm back in business once again! Thank you very much. And, to all those who gave me some advice too. I appreciate it! Peace!

I like it when things work out!
And thanks for the feedback!