<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> | | This is so frustrating.  Ubuntu peaked with Dapper, as far as smooth | upgrades are concerned.   I upgraded my old iMac G3 from Dapper to | Feisty, and it's even more messed up.  Wish I'd learned my lesson and | not upgraded my main desktop. I have exactly the opposite experience.  I have been upgrading (as opposed to reinstalling) my laptop since dapper and it is still working flawlessly.</blockquote><div> </div><div>I'm glad for you, but I have talked to others who have had similar, and worse, experiences--merely seach this list's archives and you'll see what I mean.  Gutsy was especially traumatic. </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I guess to start I would be interested in having a look at your /etc/apt/sources.list.</blockquote><div> OK, to save space I'll leave out everything that's commented out: </div><div> deb cdrom:[Ubuntu-Studio 8.04.1 _Hardy Heron_ - Release i386 (20080701)]/ hardy main multiverse restricted universe deb <a href="http://us.archive.ubuntu.com/ubuntu/" target="_blank">http://us.archive.ubuntu.com/ubuntu/</a> hardy main restricted deb-src <a href="http://us.archive.ubuntu.com/ubuntu/" target="_blank">http://us.archive.ubuntu.com/ubuntu/</a> hardy main restricted deb <a href="http://us.archive.ubuntu.com/ubuntu/" target="_blank">http://us.archive.ubuntu.com/ubuntu/</a> hardy-updates main restricted universe deb-src <a href="http://us.archive.ubuntu.com/ubuntu/" target="_blank">http://us.archive.ubuntu.com/ubuntu/</a> hardy-updates main restricted deb <a href="http://us.archive.ubuntu.com/ubuntu/" target="_blank">http://us.archive.ubuntu.com/ubuntu/</a> hardy universe deb-src <a href="http://us.archive.ubuntu.com/ubuntu/" target="_blank">http://us.archive.ubuntu.com/ubuntu/</a> hardy universe deb <a href="http://us.archive.ubuntu.com/ubuntu/" target="_blank">http://us.archive.ubuntu.com/ubuntu/</a> hardy multiverse deb-src <a href="http://us.archive.ubuntu.com/ubuntu/" target="_blank">http://us.archive.ubuntu.com/ubuntu/</a> hardy multiverse deb <a href="http://security.ubuntu.com/ubuntu" target="_blank">http://security.ubuntu.com/ubuntu</a> hardy-security main restricted deb-src <a href="http://security.ubuntu.com/ubuntu" target="_blank">http://security.ubuntu.com/ubuntu</a> hardy-security main restricted deb <a href="http://security.ubuntu.com/ubuntu" target="_blank">http://security.ubuntu.com/ubuntu</a> hardy-security universe deb-src <a href="http://security.ubuntu.com/ubuntu" target="_blank">http://security.ubuntu.com/ubuntu</a> hardy-security universe deb <a href="http://security.ubuntu.com/ubuntu" target="_blank">http://security.ubuntu.com/ubuntu</a> hardy-security multiverse deb-src <a href="http://security.ubuntu.com/ubuntu" target="_blank">http://security.ubuntu.com/ubuntu</a> hardy-security multiverse This looks good to me.  Yesterday, when I tried to sudo aptitude update, then sudo aptitude dist-upgrade, it didn't install or upgrade anything.  I'll try again now: The following packages will be upgraded:   gtk2-engines-murrine gtk2-engines-ubuntulooks libpoppler-glib2   libpoppler-qt2 libpoppler2 linux-restricted-modules-2.6.24-19-generic   linux-restricted-modules-common poppler-utils 8 packages upgraded, 0 newly installed I'll save this draft and report back after I run the upgrade and reboot. later.... Ok, now it won't boot at all.  It says it's going to check the drive, then it just hangs there. "Ubuntu Studio has been mounted 22 times without being checked, check forced. Checking drive Ubuntustudio (/dev/sda3): 0% (stage  1/5, 1/737) UbuntuStudio: 318790/12075008 files 95.2% noncontiguous), 6403122/24147703 blocks [blinking cursor]" It's been like that at least 10 minutes now, so I think that's all it's going to do. I'll try booting in recovery mode and send another e-mail with the results. FWIW I ran upgrade instead of dist-upgrade by mistake...but that shouldn't have hurt anything. --Paul </div></div>