I would say: don't do anything for now. The problem may have been solved by the updates or by the file system check.

No. And frankly, hoping that an alpha release will solve your problems is always a risky bet. If you need a stable system you should look back rather than forward (unless you have brand new hardware that is poorly supported by a newer release). I'm not saying you should revert to 9.10 or check out the 10.4.1 revision (yet). Just wait and see whether the problem reappears.

Ya know what? I tried the recovery mode (before you posted the above) and there was an option to "repair broken packages"- so I chose that, and it downloaded and installed all the updates that the Update Manager wasn't able to.

After that it returned to a command prompt- and trying "esc", e and q would not get me out of terminal mode- so I had to shut off the computer via the power button. Then it didn't boot up properly- so I shut it down again...and tried yet again, and now it's up and running.

Will my problem be solved? I doubt it- but I'm sure hoping.

So 10.04 LTS is different from 10.04.1?

Maybe reverting to 9.10 would be a good idea- my 'puter is about 3 years old, with no new hardware.....

You should have used "exit" or "reboot now". Watch out with simply cutting the power; it can lead to file system corruption.

Gee...I wonder what THAT would be like

I THINK it may be fixed! I tried to run the update manager yet again- and got the same error as before ("File system broken"). It said to run

But when I tried that, I got another error message and it said that I had to run something else (forget exactly what) to fix THAT.......[sigh]

So I ran the something else

But instead of it generating another error message as described in post #16

it actually worked this time!

Then I did the

And IT worked!

I then ran the update manager again, half expecting it to crash the system again....

But it came up and said "Your system is up to date"!!!!!! Woo-hoo!

I'm keeping my fingers crossed- I do think that what was causing my update manager problem was also causing the other problem (initial subject of this thread) - or visa-versa...

So we shall see- but I am more confident now- as it seems like something significant was actually accomplished- finally.

I'll keep you all posted-

Thanks again, and good night!!

UPDATE: Here it is, after noon, and so far, so good!

I noticed upon booting up this morning, I now (since the update) have more options in the Grub menu.

The default option is now Ubuntu(generic) 2.6.32. 24
instead of the 2.6.32. 21

Can I now go into the disk utility and delete the 2.6.32. 21 ?

Anywhay...I'll give it another day, and I think I can mark this thread "SOLVED"!

Ironically, my new monitor and ps/2 optical mouse arrived today, and I just installed them without a hitch!

I'm back to loving Ubuntu! (Good thing, because returning to Win-D'ohs is not an option, and I had no intentions of buying a Mac!) - Ubuntu or bust!

Unless you are running out of space, there is no real need to remove older kernels. You can, though (use synaptic or aptitude, not disk utility). Once you have verified that the newer kernel isn't causing any issues, that should be perfectly fine.

Thanks. I'll let it go for a few days and then if no problems arise, I'll give it a try.

Thanks for all your help.

Hi,

I generally do not remove older kernels. It is always good to something to fall back to, just in case there *might* occur some problem with the latest kernel. One never knows.

Hello!

The way that old kernel weas [not]working......I don't know how good it would be to fall back on. Maybe I'll try booting it up and seeing if it has the previous problems. If it does, I'll delete it...if it doesn't, I'll keep it around.