I've been running Ubuntu 11.04, did a clean install 2 months ago. Today I got a update notification to upgrade to 11.10 Oneiric Ocelot and I was a bit hesitant at th beginning but then I said why not and went for it. All went fine at the start.

After it was done with upgrading and cleaning the packages it restarted and I was pretty amazed with the new light dm log in screen. However, I did a restart right away to complete the install. This resulted in a black screen after the boot screen.

I did get a "waiting for network configuration" at the first start up but didn't think any of it at the beginning and everything went fine. But after the second restart, I get the boot screen with the same message and then instead of a log in screen its just black.

I tried restarting form battery source, unplugging all the usb's I had connected but still I get this black screen.

It a bit annoying cause at the moment I can't get past this, therefore I have no access to anything, so I'm lost in what to do next.

I would appreciate any help.

Kind regards

First, let this be a lesson in not upgrading using Update Mangler. Second, there is no sense in upgrading right on the day a release is put out. Let others deal with the bugs for a month or so.

That said, boot to recovery and when you get to the prompt do the text log in, at the next prompt do:
if this does anything other than give you another prompt run it a gain. If still runs some stuff before another prompt do it again.

When all you get is a clean prompt or you have run the above command 3 times, do;
This will, hopefully, take you to your desktop.

If not boot recovery again and redo the above after checking to see if there are any updates;
and
If this does not work post again with whatever errors you can write down that occurred during the ordeal and about when they happened to show up.

Thanks for taking the time, Im learning my lessons most certainly:

I went to root and did the text login but when I type
I get
Also tried startx but then I get an xauth error in locking authority file.

Not sure if this helps, but I am clueless.

Thank again,

Kind regards

I'm having the same problem. With the same errors. Any assistance would be greatly appreciated. I tried using previous kernel versions install on my computer but to no avail.

I have the same problem on 11.10 too. I feel disappointed on Ubuntu already. This problem is just never fixed, feeling suck that I have to go through all the repair process in 11.04 again.

I hope that you can report that you were asked for your password when you typed the dpkg command. That will at least tell us that some things are operating correctly.

Just for your information, dpkg is pretty much the heart of your package management system. Commands given for apt-get or aptitude are really commands that invoke dpkg. UM also is doing so even if in a rather round about way.

I am afraid I have not seen that error before and will have to investigate it a bit before venturing to give advice on that. Hopefully some other kind soul will jump in here in the mean time.

It will probably not make you feel better but the UFs is pretty swamped with similar, and some much worse, cases of 11.10 failures, I can't say that I am surprised. These are things that should have been brought to light in 11.10 testing. The UFs has run most of the experienced testers off (about 95% of them), including me.

11.10 was not tested as well as releases in the past, nor was 11.04 but not quite so bad. 10.10 was fairly well tested.

Ubuntu has never had a good record of fixing long standing bugs. Those bugs, some going back to 10.04 (or before), plus the lack of testing have combined in a release with a lot of new things in it to be a real wreck.

There is a reason that I am now using Debian.

If you are not real experienced you may find it easier to get an install disk and do a clean install. Save your data and you can put it back in there. I would use the Alt install disk, it is a text based installer but not hard to understand and it is reliable. If anything will install the bugger that will.

I will look into your error but it is 1:00AM here and I am hitting the hay. Will get back tomorrow. Well, later today.

Couldn't leave it be. Ran a short search and this came up;
https://answers.launchpad.net/ubuntu...uestion/124857

You might try that solution, can't hurt. Just change the permissions and then try booting recovery again and running the dpkg command again. Might work.
might shake something loose too.

Now I am going to bed.

Yes it did ask for my password when I run the command.

Tried the sudo install -f and didn't shake much I think as the sudo dpkg --configure -a, resulted in the same error and read only file system.

I need to go to work now, so i ll be back with more feedback about it later.

Thnx for your help.

Hi,
I have same problem. I get it after installing guest additions.
Any help ?

This is what I found although I have never experienced the problem
http://forums.debian.net/viewtopic.php?f=17&t=45159

Hi,
I had same problem. I found following solution:

https://bugs.launchpad.net/ubuntu/+s...us/+bug/811441

# 24 from RawwrBag (sthaber) helps

Hi zackFisch,
Page not found.

sorry!

https://bugs.launchpad.net/ubuntu/+s...us/+bug/811441

I find it astonishing that 'buntu's update manager still offers full distribution upgrades from within X, after years of these kinds of breakages. Forget update manager, a dist-upgrade should never be carried out from within a running x session.

As a general rule dist-upgrade should work ok, but even in Debian where they're much more reliable, you have to take some precautions. It's a good idea to get rid of proprietary video drivers, especially if you downloaded them yourself from AMD/ATI or Nvidia, in which case it's actually necessary to remove them. It's also very wise to exit from your x session and stop your display manager. You should then login as your normal user and run "apt-get dist-upgrade" as root. Once you're done - reboot, as it's likely a newer kernel was installed. Then ensure it's working ok, if so you can install back any proprietary drivers you removed - the modules for these will then be built for the new kernel - which is rather important...

Tried the fstab repair didn't work, therefore wasn't able to remount so as to have read-write access.


Got to the virtual terminal but my Linux knowledge stops at that point of creating and moving files through the terminal. Tried the first commands from there, but still got error message that the file directory exists and then that is not possible to move.

I admit that I didn't put much thought into upgrading through the update manager, but I never expected of such a huge bug out of proper release.

Thank you for your help guys.