Unfortunately, I cannot give you this additional information. I wish I could, but, after a couple more glitchy reboots, the system is now completely dead. It seems it can no longer find the root file system. It reports a correct UUID, but then says it doesn't exist. I waded through the script files, and found where the message was coming from, but it used a #DEFINE for the name/UUID of the filesystem, and I couldn't find where the value was assigned to that variable. It dumps me into a shell (one I am not familiar with), and I am tired of fudging around trying to get a system I already know is fraught with problems to start--it wasn't really usable anyway. My plan now is to install a clean copy of 7.10, and then restore my backup over that. It was when I tried to restore the backup over the messed up 8.04 that things really went South. I got a message that there were upgrades available (after the "restore"); there were 664 of them. I let them install, but several gave me t he message I couldn't "upgrade" from 8.04 to 7.10. For an install on another machine, I downloaded the ISO file (for 8.04), but came up with a bad MD5 check. A second try got me a clean download, and resulted in a clean disk, and [apparently] a clean install (this one is the 64 bit version, the other was the i386 version). So, I am guessing that, if I got a glitched download of the ISO file, I very well might have gotten a glitched download of something during the upgrade. So, I'm going to try to get back to where I started, and try the whole thing again. If I have any problems the second time, I'll take more complete notes, and try to get you better information to work with. For now, I'm going to blame it on corrupted data coming in from the internet, during the upgrade. Thanks for your help, and let me know if there is anything more I can do for you.
Sincerely, Bili Joe -------------- Original message ---------------------- From: Martin Pitt <[EMAIL PROTECTED]> > To walk through the crash reports one by one it should be enough to > open /var/crash/ in the file browser and click on the ones you want to > report (the ones which happened as your user, at least). However, apport > is not supposed to report all at the same time (it doesn't do that > here), so I wonder what's wrong on your system. > > What is the output of > > ls -l /var/crash > > ? What happens if you do > > sudo touch /var/crash/* > > ? You should get notifications about the crashes, with an offer to > submit them (they shouldn't open firefox tabs straight away). > > -- > pstops crashed with SIGSEGV > https://bugs.launchpad.net/bugs/223495 > You received this bug notification because you are a direct subscriber > of the bug. -- pstops crashed with SIGSEGV https://bugs.launchpad.net/bugs/223495 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
