[Bug 365485] Re: Aborted upgrade process left laptop in totally fucked state
It's really frustrating to see Debian users come here and display a complete lack of basic English reading skills by reporting a bug against the entirely wrong package (upgrade-system), despite mentioning in their bug report that they really mean to complain about another package (update-manager). ** Package changed: upgrade-system (Ubuntu) = update-manager (Ubuntu) -- Aborted upgrade process left laptop in totally fucked state https://bugs.launchpad.net/bugs/365485 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365485] Re: Aborted upgrade process left laptop in totally fucked state
Some particularly amusing leftovers from the upgrade script were: * existence of a mysterious '/usr/shareFeisty' directory; * the permissions of /dev/null were reset such that only root may write to it * screwed up ttf-uralic package that complained it could not be removed because its fonts had already been de-registered * failure to configure ubuntu-standard package because atd package would not configure; this was because /etc/init.d/atd start failed; but it did not print out why. Strace revealed that it was trying to connect to /dev/log, but the connection was refused. After I manually started sysklogd, I could read the real error message in syslog: apparantly atd did not have permission to access /var/sppol/cron/atjobs. This directory is now owned by user/group bin(!), as was /var/spool/cron... what the hell? ** Attachment added: dmesg output http://launchpadlibrarian.net/25884938/oops -- Aborted upgrade process left laptop in totally fucked state https://bugs.launchpad.net/bugs/365485 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365485] Re: Aborted upgrade process left laptop in totally fucked state
Jesus, I'm sorry I don't have a magical built-in knowledge of which package to file bugs such as this against. I'm sorry for naively typing in 'upgrade' into the unhelpful package search box and picking a package that sounded relevant to the problem at hand! -- Aborted upgrade process left laptop in totally fucked state https://bugs.launchpad.net/bugs/365485 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365485] Re: Aborted upgrade process left laptop in totally fucked state
Martin-Éric: your comment is completely out of order. It's a mistake very easy to make. I'm sure I don't need to remind you of http://www.ubuntu.com/community/conduct -- Aborted upgrade process left laptop in totally fucked state https://bugs.launchpad.net/bugs/365485 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365485] Re: Aborted upgrade process left laptop in totally fucked state
I understand your frustration, another observation: * existence of a mysterious '/usr/shareFeisty' directory; That looks like file system corruption (a result of the oops?) more than anything else. Could you please run a filesystem check please? -- Aborted upgrade process left laptop in totally fucked state https://bugs.launchpad.net/bugs/365485 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365485] Re: Aborted upgrade process left laptop in totally fucked state
Hello Sam, sorry for the trouble you experienced during the upgrade. I agree with you that the lack of documentation is a problem. However I would like to point out that we use the same underlaying technology /apt/dpkg) as debian to perform the upgrade. A kernel oops in the middle of the upgrade (when udev/X/dbus are in not well definied states) is something that a debian system would not take lightly as well. There is a option in the Recovery boot menu called dpkg - Repair broken packages that should be able to help. Please let me know if that helps with the problem. -- Aborted upgrade process left laptop in totally fucked state https://bugs.launchpad.net/bugs/365485 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365485] Re: Aborted upgrade process left laptop in totally fucked state
The difference is that on Debian, I can always resume an upgrade done with apt-get (or aptitude) dist-upgrade. Even though the dpkg process had gotten wedged in state D, the (first) reboot was a normal one; after I rebooted, I fully expected 'dpkg --configure -a' to resume where it left off, as it did. Now although it turns out that I can do that on Ubuntu too, I had no way of knowing that; all I had to go on was that the upgrade was started from a mysterious icon in the notification area that no longer appears; after some research I found out that this was update-manager, but since that requires pygtk and X, I was not able to run it. For all I knew, this upgrade script did important things in addition to a dist-upgrade, things that wouldn't be done if the script was not used... The problem here is basically the fragility of the upgrade process caused by relying on the update-manager script. From the PoV of an experienced Debian user, it seems like a pretty, but fragile front-end to running 'aptitude dist-upgrade'. And since it does not present any upgrade documentation to the user, the user is powerless to fix their system when an upgrade is aborted for whatever reaso. I have now got the system to a working state by doing the old 'dpkg --configure --pending' followed by a few invocations of 'aptitude dist-upgrade' punctuated by fixing the issues I listed above. Working enough to download an install CD, anyway, and do a fresh install. :) As for /usr/shareFeisty, I assumed that was an artifact of buggy maintainer scripts, rather than filesystem corruption; although, since I didn't run fsck before re-installing, I can't rule that out. -- Aborted upgrade process left laptop in totally fucked state https://bugs.launchpad.net/bugs/365485 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365485] Re: Aborted upgrade process left laptop in totally fucked state
The difference is that on Debian, I can always resume an upgrade done with apt-get (or aptitude) dist-upgrade. Even though the dpkg process had gotten wedged in state D, the (first) reboot was a normal one; after I rebooted, I fully expected 'dpkg --configure -a' to resume where it left off, as it did. Now although it turns out that I can do that on Ubuntu too, I had no way of knowing that; all I had to go on was that the upgrade was started from a mysterious icon in the notification area that no longer appears; after some research I found out that this was update-manager, but since that requires pygtk and X, I was not able to run it. For all I knew, this upgrade script did important things in addition to a dist-upgrade, things that wouldn't be done if the script was not used... The problem here is basically the fragility of the upgrade process caused by relying on the update-manager script. From the PoV of an experienced Debian user, it seems like a pretty, but fragile front-end to running 'aptitude dist-upgrade'. And since it does not present any upgrade documentation to the user, the user is powerless to fix their system when an upgrade is aborted for whatever reaso. I have now got the system to a working state by doing the old 'dpkg --configure --pending' followed by a few invocations of 'aptitude dist-upgrade' punctuated by fixing the issues I listed above. Working enough to download an install CD, anyway, and do a fresh install. :) As for /usr/shareFeisty, I assumed that was an artifact of buggy maintainer scripts, rather than filesystem corruption; although, since I didn't run fsck before re-installing, I can't rule that out. -- Aborted upgrade process left laptop in totally fucked state https://bugs.launchpad.net/bugs/365485 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 365485] Re: Aborted upgrade process left laptop in totally fucked state
The difference is that on Debian, I can always resume an upgrade done with apt-get (or aptitude) dist-upgrade. Even though the dpkg process had gotten wedged in state D, the (first) reboot was a normal one; after I rebooted, I fully expected 'dpkg --configure -a' to resume where it left off, as it did. Now although it turns out that I can do that on Ubuntu too, I had no way of knowing that; all I had to go on was that the upgrade was started from a mysterious icon in the notification area that no longer appears; after some research I found out that this was update-manager, but since that requires pygtk and X, I was not able to run it. For all I knew, this upgrade script did important things in addition to a dist-upgrade, things that wouldn't be done if the script was not used... The problem here is basically the fragility of the upgrade process caused by relying on the update-manager script. From the PoV of an experienced Debian user, it seems like a pretty, but fragile front-end to running 'aptitude dist-upgrade'. And since it does not present any upgrade documentation to the user, the user is powerless to fix their system when an upgrade is aborted for whatever reaso. I have now got the system to a working state by doing the old 'dpkg --configure --pending' followed by a few invocations of 'aptitude dist-upgrade' punctuated by fixing the issues I listed above. Working enough to download an install CD, anyway, and do a fresh install. :) As for /usr/shareFeisty, I assumed that was an artifact of buggy maintainer scripts, rather than filesystem corruption; although, since I didn't run fsck before re-installing, I can't rule that out. -- Aborted upgrade process left laptop in totally fucked state https://bugs.launchpad.net/bugs/365485 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
