<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Electric Dirt Farmer &#187; jaunty</title>
	<atom:link href="http://ditto.ca/weblog/tag/jaunty/feed/" rel="self" type="application/rss+xml" />
	<link>http://ditto.ca/weblog</link>
	<description>A conglomeration of foolishness.</description>
	<lastBuildDate>Thu, 08 Sep 2011 07:10:12 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.1.1</generator>
	<item>
		<title>Series of Unfortunate Jaunty Upgrade Events</title>
		<link>http://ditto.ca/weblog/2009/04/unfortunate-jaunty-upgrade/</link>
		<comments>http://ditto.ca/weblog/2009/04/unfortunate-jaunty-upgrade/#comments</comments>
		<pubDate>Tue, 28 Apr 2009 18:32:30 +0000</pubDate>
		<dc:creator><![CDATA[the proprietor]]></dc:creator>
				<category><![CDATA[My Computer Hates Me]]></category>
		<category><![CDATA[jaunty]]></category>
		<category><![CDATA[problems]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://ditto.ca/weblog/?p=346</guid>
		<description><![CDATA[Recently, there was a new release of Ubuntu. I&#8217;ve had relatively good experiences with past releases, and I was looking forward to trying out the new notification system, so I decided to run the upgrade from 8.10 to 9.04. This turned out to be a very bad idea. I think it might have been something [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Recently, there was a <a href="http://www.ubuntu.com/news/ubuntu-9.04-desktop" title="Canonical PR (Ubuntu.com), 20 April 2009: Canonical Announces Availability of Ubuntu 9.04 Desktop Edition">new release</a> of Ubuntu. I&#8217;ve had relatively good experiences with past releases, and I was looking forward to trying out the <a href="http://www.markshuttleworth.com/archives/253" title="Mark Shuttleworth (blog), 22 Dec 2008: Notifications, indicators and alerts">new notification system</a>, so I decided to run the upgrade from 8.10 to 9.04. This turned out to be a very bad idea.</p>
<p>I think it might have been something to do with a video card but I&#8217;ve never had a lot of luck messing around with anything related to graphics. The system was continually locking up: i.e. display frozen with an unresponsive mouse and keyboard leaving me with one option: hard reset the system. It was really frustrating, and a fresh install from CD (originally I had used the Update Manager) didn&#8217;t seem to resolve the issues. I couldn&#8217;t find anything in the release notes but I could have missed it.</p>
<p>Anyway, I really need my PC to be working right now, so I was going to revert to 8.10. I didn&#8217;t have an 8.10 install CD available so I downloaded the current 8.04 ISO and made a new CD from that. I moved my PC to another location where I could use a faster Internet connection and other computers to burn the CDs and got 8.04 up and running. At the other location, I had statically configured the network IP address via Network Manager. For reasons I don&#8217;t understand very well that appears to have cause a broken Network Manager once I had completed the upgrade to 8.10. The network connection worked but Network Manager had no defined connections (&#8220;No valid active connections found!&#8221;) and would not take over management when I defined one through the applet.</p>
<p>I found some threads on the <a href="ubuntuforums.org">Ubuntu Forums</a> but still wasn&#8217;t getting anywhere. I also found <a href="https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/279262" title="Network Manager bugs (Launchpad), 6 Oct 2008: #279262 [regression] devices/interfaces not set to "auto" in /etc/network/interfaces get blacklisted in 0.7 (intrepid) but were managed in 0.6 (hardy and before)">this bug in Launchpad</a>. I&#8217;m comfortable with Linux but not an expert by any means so it took me a while to resolve the issue. In the end I commented out any reference to eth0 in /etc/network/interfaces, purged Network Manager (apt-get purge network-manager), and rebooted my computer. Then I reinstalled network-manager and rebooted again. Might not be exactly the right procedure but it seemed to work. Just making changes to the configuration files and logging off and back on didn&#8217;t work. Doing that caused other problems like not being able to launch the Terminal app.</p>
<p>The whole process was made more frustrating because now I have to reinstall and reconfigure many of the bits and pieces of my working environment (apache, vmware, etc). I also accidentally deleted my archive of podcasts and downloads somewhere along the line. Obviously, that&#8217;s not all the result of trying to install Jaunty but it does more or less guarantee I won&#8217;t be trying the upgrade again.</p>
]]></content:encoded>
			<wfw:commentRss>http://ditto.ca/weblog/2009/04/unfortunate-jaunty-upgrade/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
