Judging from the changelog, this fix landed in Gutsy, Marking as Fix
Released.
** Changed in: update-manager (Ubuntu)
Status: Fix Committed = Fix Released
--
Upgrading to Feisty fails with fatal error
https://bugs.launchpad.net/bugs/109548
You received this bug notification because you
Unsubscribing ubuntu-sru. Please fix this in hardy first and then
provide a proper SRU request as per policy
(https://wiki.ubuntu.com/StableReleaseUpdates).
--
Upgrading to Feisty fails with fatal error
https://bugs.launchpad.net/bugs/109548
You received this bug notification because you are a
Thanks for this additional information, I'm happy that your system is
working ok again.
--
Upgrading to Feisty fails with fatal error
https://bugs.launchpad.net/bugs/109548
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Thanks for your bugreport.
From reading the logs it seems that downloading/installing the updated
packages took three days, is that correct (update started 20 and failed
on 23)?
** Changed in: update-manager (Ubuntu)
Status: Unconfirmed = Needs Info
--
Upgrading to Feisty fails with
True, in the sense that I started it Friday afternoon when I left the
office and had to acknowledge an error msg when I came back on Monday.
--
Upgrading to Feisty fails with fatal error
https://bugs.launchpad.net/bugs/109548
You received this bug notification because you are a member of Ubuntu
True, in the sense that I started it Friday afternoon when I left the
office and had to acknowledge an error msg when I came back on Monday.
** Changed in: update-manager (Ubuntu)
Status: Needs Info = Unconfirmed
--
Upgrading to Feisty fails with fatal error
Thanks for this additional information.
It looks like this is caused by a race with the automatic cleanup process, I
commited a fix for this as:
Anyway, after a few rounds of updates in Synaptic the Update Manager now
thinks my system is up to date. Only problem that remained was a bug in
xorg.conf, where my ATI card was listed as ChipId 0x71c5. Changing to
0x71c4 got X working again, so now everything looks fine.
--
Upgrading to Feisty
