<?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; print</title>
	<atom:link href="http://blog.christophersmart.com/tag/print/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>Firefox default print DPI fix</title>
		<link>http://blog.christophersmart.com/2010/07/16/firefox-default-print-dpi-fix/</link>
		<comments>http://blog.christophersmart.com/2010/07/16/firefox-default-print-dpi-fix/#comments</comments>
		<pubDate>Fri, 16 Jul 2010 03:44:17 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[FOSS]]></category>
		<category><![CDATA[300]]></category>
		<category><![CDATA[600]]></category>
		<category><![CDATA[dpi]]></category>
		<category><![CDATA[firefox]]></category>
		<category><![CDATA[mozilla]]></category>
		<category><![CDATA[print]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://blog.christophersmart.com/?p=2197</guid>
		<description><![CDATA[Firefox on my Dad&#8217;s machine always wants to print to 300 DPI by default. He can manually change it, but it&#8217;s annoying. Other browsers pick up the printer default of 600 DPI and are happy, but not Firefox. He posted a bug on Launchpad for it and then afterwards I found a fix for it [...]]]></description>
			<content:encoded><![CDATA[<p>Firefox on my Dad&#8217;s machine always wants to print to 300 DPI by default. He can manually change it, but it&#8217;s annoying. Other browsers pick up the printer default of 600 DPI and are happy, but not Firefox. He posted a <a href="https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/606061?comments=all">bug on Launchpad for it</a> and then afterwards I found a <a href="http://support.mozilla.com/en-US/forum/1/504098">fix for it upstream in Mozilla&#8217;s Bugzilla</a>.</p>
<p>It&#8217;s as simple as:</p>
<blockquote><p>As user, open a shell and enter:<br />
<code>lpoptions -o Resolution=600dpi</code></p>
<p>This will add a default resolution to ~/.cups/lpoptions </p>
<p>My ~/.cups/lpoptions contains:<br />
<code>Default IP4200 Resolution=600dpi</code>
</p></blockquote>
<p>So anyone who has the same issue, here&#8217;s the work around.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.christophersmart.com/2010/07/16/firefox-default-print-dpi-fix/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<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>
	</channel>
</rss>

