<?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>the blog of Chris &#187; broken</title>
	<atom:link href="http://blog.christophersmart.com/tag/broken/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.christophersmart.com</link>
	<description>Fortiter Et Recte</description>
	<lastBuildDate>Wed, 28 Dec 2011 23:39:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Karmic upgrade, broken printing. Workaround.</title>
		<link>http://blog.christophersmart.com/2009/11/10/karmic-upgrade-broken-printing-workaround/</link>
		<comments>http://blog.christophersmart.com/2009/11/10/karmic-upgrade-broken-printing-workaround/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 22:50:34 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[FOSS]]></category>
		<category><![CDATA[broken]]></category>
		<category><![CDATA[karmic]]></category>
		<category><![CDATA[print]]></category>
		<category><![CDATA[update]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://blog.christophersmart.com/?p=1349</guid>
		<description><![CDATA[So on another machine (my Dad&#8217;s to be exact) after an upgrade to Karmic, both sound and printing were broken. I fixed the printing issue last night, which was truly strange. The original printer was still there (as I would expect) and could be seen in the GNOME print manager. The problem was that it [...]]]></description>
			<content:encoded><![CDATA[<p>So on another machine (my Dad&#8217;s to be exact) after an upgrade to Karmic, both sound and printing were broken.</p>
<p>I fixed the printing issue last night, which was truly strange. The original printer was still there (as I would expect) and could be seen in the GNOME print manager. The problem was that it just wouldn&#8217;t print at all. Taking a closer look, for some reason the driver had been reset to &#8220;Alps MD-1000&#8243; even though it&#8217;s a Samsung.</p>
<p><img src="http://blog.christophersmart.com/images/karmic-printer-driver-error-small.png" alt="Broken printer" /></p>
<p>Changing the driver to anything else and saving the changes <em>did not actually change the driver</em> &#8211; it went straight back to &#8220;Alps MD-1000.&#8221; Adding a new printer resulted in the same problem.</p>
<p>The fix was to log into the CUPS server directly (http://localhost:631) and from here I was able to select the right driver &#8211; and it stuck. It could now print correctly.</p>
<p>Going back to the GNOME print manager still shows the driver as being the &#8220;Alps MD-1000&#8243; which is just wrong.</p>
<p>So I&#8217;m not sure why GNOME print manager is broken, but if I configure the printer directly with CUPS it works.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.christophersmart.com/2009/11/10/karmic-upgrade-broken-printing-workaround/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Ubuntu does it again..</title>
		<link>http://blog.christophersmart.com/2009/11/04/ubuntu-does-it-again/</link>
		<comments>http://blog.christophersmart.com/2009/11/04/ubuntu-does-it-again/#comments</comments>
		<pubDate>Wed, 04 Nov 2009 01:06:21 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[FOSS]]></category>
		<category><![CDATA[broken]]></category>
		<category><![CDATA[dhcp]]></category>
		<category><![CDATA[fail]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://blog.christophersmart.com/?p=1320</guid>
		<description><![CDATA[So I&#8217;ve foolishly upgraded a machine at work to Karmic and after a reboot, networking was completely broken. Awesome. Why does Ubuntu break every time you upgrade? It gives &#8220;Linux&#8221; a bad name. Looks like it&#8217;s a problem with the dhcpcd script. When running dhcpcd eth0, it errors saying that eth0 does not exist, when [...]]]></description>
			<content:encoded><![CDATA[<p>So I&#8217;ve foolishly upgraded a machine at work to Karmic and after a reboot, networking was completely broken.</p>
<p>Awesome. Why does Ubuntu break every time you upgrade? It gives &#8220;Linux&#8221; a bad name.</p>
<p>Looks like it&#8217;s a problem with the dhcpcd script. When running <code>dhcpcd eth0</code>, it errors saying that eth0 does not exist, when indeed it does.<br />
Calling <code>dhcpcd-bin eth0</code> works correctly.</p>
<p>Removing dhcpcd with &#8211;purge and re-installing it fixed the problem.</p>
<p>Sigh.</p>
<p>Just have a look at the <a href="http://www.ubuntu.com/getubuntu/releasenotes/910">release notes</a> for some impressive 40+ bugs. File corruption on <em>large files</em> (over 512MB! Woh!), Hibernation broken, Jockey awesomeness, broken RAID, X server crash with Wacom table, blah, blah, blah.  Then there&#8217;s all the others which surface when every poor sod running Jaunty tries an upgrade..</p>
<blockquote><p>Ubuntu, where stable != stable.</p></blockquote>
<p>-c</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.christophersmart.com/2009/11/04/ubuntu-does-it-again/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

