<?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>Nancy Fusco &#187; bug</title>
	<atom:link href="http://nancyfusco.com/wp/index.php/tag/bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://nancyfusco.com/wp</link>
	<description></description>
	<lastBuildDate>Sun, 05 Feb 2012 14:47:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
		<item>
		<title>How to fix startup memory error in Cinelerra</title>
		<link>http://nancyfusco.com/wp/index.php/2009/02/how-to-fix-startup-memory-error-in-cinelerra/</link>
		<comments>http://nancyfusco.com/wp/index.php/2009/02/how-to-fix-startup-memory-error-in-cinelerra/#comments</comments>
		<pubDate>Wed, 04 Feb 2009 23:14:06 +0000</pubDate>
		<dc:creator>Nancy</dc:creator>
				<category><![CDATA[debian]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[cinelerra]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[memory]]></category>

		<guid isPermaLink="false">http://nancyfusco.com/wp/?p=252</guid>
		<description><![CDATA[In the current release of Cinelerra, the Linux Video editing tool, version 2.1 CV, you may get the error when starting up the program: The following errors occurred: void MWindow::init_shm0: WARNING:/proc/sys/kernel/shmmax is 0&#215;2000000, which is too low. Before running Cinelerra do the following as root: echo &#8220;0x7fffffff&#8221;&#62;/proc/sys/kernel/shmmax Sure, you can run over to Terminal as [...]]]></description>
			<content:encoded><![CDATA[<p>In the current release of Cinelerra, the Linux Video editing tool, version 2.1 CV, you may get the error when starting up the program:<br />
<i>The following errors occurred:<br />
void MWindow::init_shm0: WARNING:/proc/sys/kernel/shmmax is 0&#215;2000000, which is too low.<br />
Before running Cinelerra do the following as root:<br />
echo &#8220;0x7fffffff&#8221;&gt;/proc/sys/kernel/shmmax </i></p>
<p>Sure, you can run over to Terminal as Root and enter that command everytime your reboot and want to use Cinelerra, and yes, that&#8217;s 7 f&#8217;s. But why not make a more permanent change. <span id="more-252"></span> This error message is just trying to say to allocate more memory space to Cinelerra. Cinelerra will be happy. Linux will be happy. You&#8217;ll be happy. So let&#8217;s go team!</p>
<p>Open terminal in super user mode, I just used the icon already on Debian, under Applications | System Tools | Terminal Server &#8211; Super User Mode and enter the following at the command prompt to make a backup of this file. You always make a backup, right!?</p>
<p>cp /etc/sysctl.conf /etc/sysctl.conf.backup</p>
<p>Now let&#8217;s edit this file. Enter this next:</p>
<p>nano /etc/sysctl.conf</p>
<p>At the very bottom of the file, add this line, and remember that&#8217;s 7 f&#8217;s, we&#8217;re talking memory size here. After adding this line, save and close the file, CTRL-X and then Y for yes to save it.</p>
<p>kernel/shmmax=0x7fffffff</p>
<p>Now, let&#8217;s put this file in action, at the command prompt enter:</p>
<p>sudo sysctl -p</p>
<p>Test by opening Cinelerra. Yay! No more annoying error message! Well, at least at startup. <img src='http://nancyfusco.com/wp/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://nancyfusco.com/wp/index.php/2009/02/how-to-fix-startup-memory-error-in-cinelerra/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Upgraded to Lenny &#8211; How to fix broken sound</title>
		<link>http://nancyfusco.com/wp/index.php/2009/02/upgraded-to-lenny-how-to-fix-broken-sound/</link>
		<comments>http://nancyfusco.com/wp/index.php/2009/02/upgraded-to-lenny-how-to-fix-broken-sound/#comments</comments>
		<pubDate>Mon, 02 Feb 2009 18:01:09 +0000</pubDate>
		<dc:creator>Nancy</dc:creator>
				<category><![CDATA[debian]]></category>
		<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[broken]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[no sound]]></category>
		<category><![CDATA[sound]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://nancyfusco.com/wp/?p=240</guid>
		<description><![CDATA[After upgrading to Lenny, everything was really smooth and in order. The only package that didn&#8217;t upgrade automatically was Quanta. So from the command line, I did a quick install of Quanta and good to go. Well, sort of. After the upgrade, I rebooted to find that my sound was broken. Up in the top [...]]]></description>
			<content:encoded><![CDATA[<p>After upgrading to Lenny, everything was really smooth and in order. The only package that didn&#8217;t upgrade automatically was Quanta. So from the command line, I did a quick install of Quanta and good to go. Well, sort of. After the upgrade, I rebooted to find that my sound was broken. Up in the top right of the screen, when I clicked on the Gnome Mixer Volume Control icon (which had a diabolical red x on it), I got this error message:</p>
<p><i>The volume control did not find any elements and/or devices to control. This means either that you don&#8217;t have the right GStreamer plugins installed, or that you don&#8217;t have a sound card configured. </i></p>
<p>After some research, I found that the new kernel did not have built in support for Alsa sound firmware! What?! Ok, I&#8217;m not going to rant about this too much, suffice it to say, it worked with the previous kernel why in the world would they not include it in the most recent kernel? Rant over. Let&#8217;s fix it. <img src='http://nancyfusco.com/wp/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>First thing, you have to do a manual install of the alsa-source and the build-essential files. Open terminal in super user mode, I just used the icon already on Debian, under Applications | System Tools | Terminal Server &#8211; Super User Mode and enter the following at the command prompt:</p>
<p><code>aptitude install alsa-source build-essential</code></p>
<p>This will take a few minutes, but now you&#8217;ll have the groundwork for installing the firmware to connect to your sound card in Debian Lenny. <span id="more-240"></span> Next, you&#8217;ll need to download the firmware for Alsa from here:</p>
<p><a href="ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.16.tar.bz2">ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.16.tar.bz2</a></p>
<p>Make a directory to store this file:</p>
<p><code> mkdir /usr/src/alsa </code></p>
<p>At the Terminal command line, copy the downloaded file to the sources area you just created. Adjust this path as needed, depending on where you saved your download (remember Unix is case sensitive):</p>
<p><code> cp /home/nancyfusco/Desktop/alsa* /usr/src/alsa </code></p>
<p>Now path out to that area, so you can unpack the tar:</p>
<p><code> cd /usr/src/alsa </code></p>
<p>Unpack it:</p>
<p><code> tar -vxjf alsa-firmware-1.0.16.tar.bz2 </code></p>
<p>Path out to the unpackaged folder:</p>
<p><code> cd /usr/src/alsa/alsa-firmware-1.0.16 </code></p>
<p>Are you ready? Good! Here we go! Now to compile and install the firmware and configuration for your sound card. At the command prompt enter:</p>
<p><code> ./configure &amp;&amp; make &amp;&amp; make install </code></p>
<p>Watch it work while sipping on a cold one. <b>Reboot.</b> Hey! Look! We got sound again! Now go watch some <a href="http://www.filmcow.com/youtube-charlietheunicorn.html" target="_blank">Charlie the Unicorn</a> to celebrate!</p>
]]></content:encoded>
			<wfw:commentRss>http://nancyfusco.com/wp/index.php/2009/02/upgraded-to-lenny-how-to-fix-broken-sound/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Peek-a-boo display bug in IE</title>
		<link>http://nancyfusco.com/wp/index.php/2009/01/peek-a-boo-display-bug-in-ie/</link>
		<comments>http://nancyfusco.com/wp/index.php/2009/01/peek-a-boo-display-bug-in-ie/#comments</comments>
		<pubDate>Wed, 21 Jan 2009 03:20:47 +0000</pubDate>
		<dc:creator>Nancy</dc:creator>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[div]]></category>
		<category><![CDATA[explorer]]></category>
		<category><![CDATA[firefox]]></category>

		<guid isPermaLink="false">http://nancyfusco.com/wp/?p=110</guid>
		<description><![CDATA[There is a pesky display bug that will render a &#8220;peek-a-boo&#8221; effect when you layer div containers in CSS. When this bug is at it&#8217;s best, content that should stream after a previous div container, instead partially hides behind it. This is how my home page displays without the position: relative in the post div [...]]]></description>
			<content:encoded><![CDATA[<p>There is a pesky display bug that will render a &#8220;peek-a-boo&#8221; effect when you layer div containers in CSS. When this bug is at it&#8217;s best, content that should stream after a previous div container, instead partially hides behind it. This is how my home page displays without the position: relative in the post div tag:</p>
<p><a href="http://nancyfusco.com/wp/wp-content/uploads/2009/01/peek-a-boo-ie.jpg"></a><a href="http://nancyfusco.com/wp/wp-content/uploads/2009/01/peek-a-boo-ie2.jpg"><img class="alignnone size-full wp-image-114" title="peek-a-boo-ie2" src="http://nancyfusco.com/wp/wp-content/uploads/2009/01/peek-a-boo-ie2.jpg" alt="peek-a-boo-ie2" width="313" height="137" /></a></p>
<p>A pretty simple fix by adding in the position: relative; to the containing div tag, as in the stylesheet for my blog:</p>
<p>.post{<br />
position: relative;<br />
margin: 10px 0;<br />
padding: 11px 11px 0;<br />
background: url(images/bg_post.jpg) no-repeat;<br />
}</p>
<p>Nice thing about this tweak &#8211; It doesn&#8217;t break how Firefox/Mozilla renders the page. It just makes IE play nice with your div layout.</p>
]]></content:encoded>
			<wfw:commentRss>http://nancyfusco.com/wp/index.php/2009/01/peek-a-boo-display-bug-in-ie/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Image Upload Fix</title>
		<link>http://nancyfusco.com/wp/index.php/2009/01/wordpress-image-upload-fix/</link>
		<comments>http://nancyfusco.com/wp/index.php/2009/01/wordpress-image-upload-fix/#comments</comments>
		<pubDate>Mon, 19 Jan 2009 18:49:03 +0000</pubDate>
		<dc:creator>Nancy</dc:creator>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[.htaccess]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[fix]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[image]]></category>
		<category><![CDATA[upload]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://nancyfusco.com/wp/?p=65</guid>
		<description><![CDATA[On WordPress 2.7, if you use the image uploader to add images to posts, you may get this error: Precondition Failed The precondition on the request for the URL /blog/wp-admin/media-upload.php evaluated to false. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. It generally goes without [...]]]></description>
			<content:encoded><![CDATA[<p>On WordPress 2.7, if you use the image uploader to add images to posts, you may get this error:</p>
<p>Precondition Failed<br />
The precondition on the request for the URL /blog/wp-admin/media-upload.php evaluated to false. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.</p>
<p>It generally goes without saying, however, make a backup of your .htaccess file before editing it.</p>
<p>Add this to your .htaccess file in the root of your website to fix this issue:</p>
<pre class="alt2" style="border: 1px inset; margin: 0px; padding: 6px; overflow: auto; width: 340px; height: 82px; text-align: left;" dir="ltr">&lt;IfModule mod_security.c&gt;
SecFilterEngine Off
SecFilterScanPOST Off
&lt;/IfModule&gt;</pre>
]]></content:encoded>
			<wfw:commentRss>http://nancyfusco.com/wp/index.php/2009/01/wordpress-image-upload-fix/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

