Upgrade fails

[Åsmund Hjulstad]

I have had two similar problems on upgrade to latest karmic: One dist-upgrade from 9.04, the other an upgrade on an existing karmic installation, sometime during the last few days. In both cases I was left without a working X. As I couldn't find any information elsewhere, I file this bug report, with simple fix, in case it is useful for someone else.

On my Dell XPS M1330 (upgrade from 9.04 amd64), after upgrade, the computer loops endlessly, trying to start X, with ddxSigGiveUp in the X log. To fix it, I started in safe mode (with networking enabled), downloaded envyng-core (with aptitude) and ran envyng -t, installed latest nvidia binary drivers, and reboot.

On my desktop (with GeForce 6800 GS, already running karmic), X did not start, leaving me at a console login. Same solution though.

[Matthew Woerly (nattgew)]

Thanks for taking the time to report this.
Could you provide any logs from the update or upgrade?

[Åsmund Hjulstad (asmund)]

Please find attached contents of /var/log/dist-upgrade from my XPS M1330 (that I upgraded from 9.04). Please advise if I should attach additional logs. (Apologies if double-posting.)

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[Åsmund Hjulstad (asmund)]

All my computers are now running Natty, and I do not have any problem. If I recall correctly, the issue was with an upgrade to karmic, quite a while ago.

I cannot say whether this is still a karmic issue, but I do not see it as a natty issue.

As it does not appear relevant to tag as 'Fix Released', can someone else please advise to what is proper status of this report?

[Bryce Harrington (bryce)]

I think in this case we can treat natty as the "solution" to the problem. I think we're unlikely to backport binary drivers to lrm 2.6.24