<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments for Avaktavyam</title>
	<atom:link href="http://lddubeau.com/avaktavyam/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://lddubeau.com/avaktavyam</link>
	<description>Some things just can't be expressed...</description>
	<pubDate>Thu, 20 Nov 2008 17:55:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>Comment on OOHanzi 0.5 released by Louis-Dominique</title>
		<link>http://lddubeau.com/avaktavyam/2008/06/28/oohanzi-05-released#comment-8340</link>
		<dc:creator>Louis-Dominique</dc:creator>
		<pubDate>Sun, 16 Nov 2008 01:16:57 +0000</pubDate>
		<guid isPermaLink="false">http://lddubeau.com/avaktavyam/2008/06/28/oohanzi-05-released/#comment-8340</guid>
		<description>Hi Christian,

I'm sorry.  I'm afraid I have never seen such error message.  "Unsupported class version" error suggest that maybe the Java Runtime Environment being used is older than would be desirable?  OOHanzi requires Java 6.  Unfortunately, I do not have a Mac so I cannot test OOHanzi on a Mac.

If you check the version of your Java Runtime Environment and find that it is high enough, then I suggest that you file a bug report on Launchpad:

https://bugs.launchpad.net/oohanzi

You will have to register if you are not already registered.  I know it is not pleasant to register on yet another site but reporting there allows me to keep some sort of structure to the project and to record problems and solutions.

Thank you.</description>
		<content:encoded><![CDATA[<p>Hi Christian,</p>
<p>I&#8217;m sorry.  I&#8217;m afraid I have never seen such error message.  &#8220;Unsupported class version&#8221; error suggest that maybe the Java Runtime Environment being used is older than would be desirable?  OOHanzi requires Java 6.  Unfortunately, I do not have a Mac so I cannot test OOHanzi on a Mac.</p>
<p>If you check the version of your Java Runtime Environment and find that it is high enough, then I suggest that you file a bug report on Launchpad:</p>
<p><a href="https://bugs.launchpad.net/oohanzi" rel="nofollow">https://bugs.launchpad.net/oohanzi</a></p>
<p>You will have to register if you are not already registered.  I know it is not pleasant to register on yet another site but reporting there allows me to keep some sort of structure to the project and to record problems and solutions.</p>
<p>Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on OOHanzi 0.5 released by Christian Wittern</title>
		<link>http://lddubeau.com/avaktavyam/2008/06/28/oohanzi-05-released#comment-8339</link>
		<dc:creator>Christian Wittern</dc:creator>
		<pubDate>Sat, 15 Nov 2008 23:17:44 +0000</pubDate>
		<guid isPermaLink="false">http://lddubeau.com/avaktavyam/2008/06/28/oohanzi-05-released/#comment-8339</guid>
		<description>Hi Louis-Dominique,
I tried to install your extension on Mac OS X 10.5.5 and OO 3.0.  When I come to the step where it says "Add the extensions", I get an error, saying something like UNO bridge error, unsupported class version error.

Do you know what this means and how to fix this?

Christian</description>
		<content:encoded><![CDATA[<p>Hi Louis-Dominique,<br />
I tried to install your extension on Mac OS X 10.5.5 and OO 3.0.  When I come to the step where it says &#8220;Add the extensions&#8221;, I get an error, saying something like UNO bridge error, unsupported class version error.</p>
<p>Do you know what this means and how to fix this?</p>
<p>Christian</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Linux on a Compal IFL90 and JFL92 by Jori</title>
		<link>http://lddubeau.com/avaktavyam/linux-on-a-compal-ifl90#comment-8338</link>
		<dc:creator>Jori</dc:creator>
		<pubDate>Tue, 11 Nov 2008 19:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://lddubeau.com/avaktavyam/linux-on-a-compal-ifl90/#comment-8338</guid>
		<description>Louis,

I never got your xorg.conf.  Perhaps I entered my email wrong.  It is jyro215 at gmail dot com.</description>
		<content:encoded><![CDATA[<p>Louis,</p>
<p>I never got your xorg.conf.  Perhaps I entered my email wrong.  It is jyro215 at gmail dot com.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Linux on a Compal IFL90 and JFL92 by sum41</title>
		<link>http://lddubeau.com/avaktavyam/linux-on-a-compal-ifl90#comment-8337</link>
		<dc:creator>sum41</dc:creator>
		<pubDate>Sat, 08 Nov 2008 10:59:37 +0000</pubDate>
		<guid isPermaLink="false">http://lddubeau.com/avaktavyam/linux-on-a-compal-ifl90/#comment-8337</guid>
		<description>fingerprint works great for me (hardy ifl90)! follow the instructions in this file: http://www.n-view.net/Appliance//fingerprint/ubuntu-step-by-step.pdf

you will need to adapt the file /etc/udev/rules.d/50-libfprint0.rules once it has been created. simply add the following line at the end:
ATTRS{idVendor}=="147e", ATTRS{idProduct}=="2016", MODE="0664", GROUP="plugdev"

continue the installation afterwords and everything will work great!!!</description>
		<content:encoded><![CDATA[<p>fingerprint works great for me (hardy ifl90)! follow the instructions in this file: <a href="http://www.n-view.net/Appliance//fingerprint/ubuntu-step-by-step.pdf" rel="nofollow">http://www.n-view.net/Appliance//fingerprint/ubuntu-step-by-step.pdf</a></p>
<p>you will need to adapt the file /etc/udev/rules.d/50-libfprint0.rules once it has been created. simply add the following line at the end:<br />
ATTRS{idVendor}==&#8221;147e&#8221;, ATTRS{idProduct}==&#8221;2016&#8243;, MODE=&#8221;0664&#8243;, GROUP=&#8221;plugdev&#8221;</p>
<p>continue the installation afterwords and everything will work great!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Linux on a Compal IFL90 and JFL92 by sum41</title>
		<link>http://lddubeau.com/avaktavyam/linux-on-a-compal-ifl90#comment-8336</link>
		<dc:creator>sum41</dc:creator>
		<pubDate>Fri, 07 Nov 2008 17:42:51 +0000</pubDate>
		<guid isPermaLink="false">http://lddubeau.com/avaktavyam/linux-on-a-compal-ifl90/#comment-8336</guid>
		<description>@cezary
how did you do?</description>
		<content:encoded><![CDATA[<p>@cezary<br />
how did you do?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Linux on a Compal IFL90 and JFL92 by Cezary</title>
		<link>http://lddubeau.com/avaktavyam/linux-on-a-compal-ifl90#comment-8335</link>
		<dc:creator>Cezary</dc:creator>
		<pubDate>Wed, 05 Nov 2008 16:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://lddubeau.com/avaktavyam/linux-on-a-compal-ifl90/#comment-8335</guid>
		<description>BTW: fingerprint works with Fingerprint GUI and libbsapi.so - 
without problem. In GUI or console (debian, 32bit).</description>
		<content:encoded><![CDATA[<p>BTW: fingerprint works with Fingerprint GUI and libbsapi.so -<br />
without problem. In GUI or console (debian, 32bit).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intrepid: Growing Pains by Louis-Dominique</title>
		<link>http://lddubeau.com/avaktavyam/2008/10/31/intrepid-growing-pains#comment-8334</link>
		<dc:creator>Louis-Dominique</dc:creator>
		<pubDate>Mon, 03 Nov 2008 05:26:19 +0000</pubDate>
		<guid isPermaLink="false">http://lddubeau.com/avaktavyam/?p=313#comment-8334</guid>
		<description>Good question Bill.  There is nothing yet which I think is "OMG, this is something I must have!!1!"  What I've noticed:

1. The power management subsystem has been significantly revamped.  Prior to Intrepid, there were several packages involved in suspending or putting the computer to sleep and those packages were held together by very fragile glue.  I know because I've had to go mess with them at some point in the past.  It was very hard to know what does what.  In Intrepid, they've decided to retire the old acpi-support package.  That's a welcome change.  The upshot for the end user is that it should be easier to have full support for suspend and hibernate.

2. I do not need to mess as much with configuration in /etc/ as I did in previous releases.

3. There is support for a private encrypted directory.  But I don't use that because I encrypt all of my Linux partitions anyway.

4. Pulseaudio seems to work better than it did in Hardy.  See my point about skype in my post.  In the past, I've had issues with skype working properly.  If I used any other application which outputs sound before using skype then skype would complain about not being able to output audio.  With the "pluse" devices, I'm hoping that this won't happen.

5. Then there's a bunch of little things here and there.</description>
		<content:encoded><![CDATA[<p>Good question Bill.  There is nothing yet which I think is &#8220;OMG, this is something I must have!!1!&#8221;  What I&#8217;ve noticed:</p>
<p>1. The power management subsystem has been significantly revamped.  Prior to Intrepid, there were several packages involved in suspending or putting the computer to sleep and those packages were held together by very fragile glue.  I know because I&#8217;ve had to go mess with them at some point in the past.  It was very hard to know what does what.  In Intrepid, they&#8217;ve decided to retire the old acpi-support package.  That&#8217;s a welcome change.  The upshot for the end user is that it should be easier to have full support for suspend and hibernate.</p>
<p>2. I do not need to mess as much with configuration in /etc/ as I did in previous releases.</p>
<p>3. There is support for a private encrypted directory.  But I don&#8217;t use that because I encrypt all of my Linux partitions anyway.</p>
<p>4. Pulseaudio seems to work better than it did in Hardy.  See my point about skype in my post.  In the past, I&#8217;ve had issues with skype working properly.  If I used any other application which outputs sound before using skype then skype would complain about not being able to output audio.  With the &#8220;pluse&#8221; devices, I&#8217;m hoping that this won&#8217;t happen.</p>
<p>5. Then there&#8217;s a bunch of little things here and there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intrepid: Growing Pains by Bill magee</title>
		<link>http://lddubeau.com/avaktavyam/2008/10/31/intrepid-growing-pains#comment-8332</link>
		<dc:creator>Bill magee</dc:creator>
		<pubDate>Sun, 02 Nov 2008 00:04:11 +0000</pubDate>
		<guid isPermaLink="false">http://lddubeau.com/avaktavyam/?p=313#comment-8332</guid>
		<description>Thanks for this cautionary post, Louis. Has anything gotten better with Intrepid?</description>
		<content:encoded><![CDATA[<p>Thanks for this cautionary post, Louis. Has anything gotten better with Intrepid?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Linux on a Compal IFL90 and JFL92 by Louis-Dominique</title>
		<link>http://lddubeau.com/avaktavyam/linux-on-a-compal-ifl90#comment-8331</link>
		<dc:creator>Louis-Dominique</dc:creator>
		<pubDate>Fri, 31 Oct 2008 08:27:36 +0000</pubDate>
		<guid isPermaLink="false">http://lddubeau.com/avaktavyam/linux-on-a-compal-ifl90/#comment-8331</guid>
		<description>&lt;strong&gt;@Jori&lt;/strong&gt;: I'll send you my xorg.conf.

&lt;strong&gt;@Revan&lt;/strong&gt;: Merci pour l'info.</description>
		<content:encoded><![CDATA[<p><strong>@Jori</strong>: I&#8217;ll send you my xorg.conf.</p>
<p><strong>@Revan</strong>: Merci pour l&#8217;info.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Intrepid: Growing Pains by Louis-Dominique</title>
		<link>http://lddubeau.com/avaktavyam/2008/10/31/intrepid-growing-pains#comment-8330</link>
		<dc:creator>Louis-Dominique</dc:creator>
		<pubDate>Fri, 31 Oct 2008 08:15:21 +0000</pubDate>
		<guid isPermaLink="false">http://lddubeau.com/avaktavyam/?p=313#comment-8330</guid>
		<description>&lt;strong&gt;@Simon&lt;/strong&gt;: An incorrect assumption rather than a stupid question.  I do not use skim in Gnome.  The skim package was left over from an earlier KDE installation.  In the past I have been pretty good at purging my system of all things KDE after trying KDE out but now I still use some KDE apps from time to time so going through the list of packages to remove is error-prone.  

skim was a left-over.  The mere existence of /usr/bin/skim, whether it is actually used or not by the user, is enough to prevent scim to run.  There is an actual test in a session script which does what I'm talking about: if skim exists, then do not run scim.  It is a bad test.  Somebody has fixed it but the fix has yet to trickle down to the repository.</description>
		<content:encoded><![CDATA[<p><strong>@Simon</strong>: An incorrect assumption rather than a stupid question.  I do not use skim in Gnome.  The skim package was left over from an earlier KDE installation.  In the past I have been pretty good at purging my system of all things KDE after trying KDE out but now I still use some KDE apps from time to time so going through the list of packages to remove is error-prone.  </p>
<p>skim was a left-over.  The mere existence of /usr/bin/skim, whether it is actually used or not by the user, is enough to prevent scim to run.  There is an actual test in a session script which does what I&#8217;m talking about: if skim exists, then do not run scim.  It is a bad test.  Somebody has fixed it but the fix has yet to trickle down to the repository.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
