<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: When digiKam Failed to Connect</title>
	<atom:link href="http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/</link>
	<description>Sci-fi, comics, humor, photos...it&#039;s all fair game.</description>
	<lastBuildDate>Mon, 02 Nov 2009 04:10:50 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: avocadohead</title>
		<link>http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-47891</link>
		<dc:creator>avocadohead</dc:creator>
		<pubDate>Fri, 21 Aug 2009 16:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-47891</guid>
		<description>Nice informative post. On my system (libgphoto2-2.4.0-25.2, opensuse 10.3, KDE 4.3), the print-camera-list syntax did not work, I had to use
print-camera-list udev-rules version 0.98 group users ...
Oh, and what was ultimately the cause for the connection failure in my particular case was a leftover Konqueror/KDE3 trying to automount the camera.</description>
		<content:encoded><![CDATA[<p>Nice informative post. On my system (libgphoto2-2.4.0-25.2, opensuse 10.3, KDE 4.3), the print-camera-list syntax did not work, I had to use<br />
print-camera-list udev-rules version 0.98 group users &#8230;<br />
Oh, and what was ultimately the cause for the connection failure in my particular case was a leftover Konqueror/KDE3 trying to automount the camera.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Torsten</title>
		<link>http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-47658</link>
		<dc:creator>Torsten</dc:creator>
		<pubDate>Tue, 07 Jul 2009 23:07:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-47658</guid>
		<description>Thanks a lot! You&#039;ve helped me even today with my gentoo install :)</description>
		<content:encoded><![CDATA[<p>Thanks a lot! You&#8217;ve helped me even today with my gentoo install <img src='http://www.hyperborea.org/journal/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lasse</title>
		<link>http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-47133</link>
		<dc:creator>Lasse</dc:creator>
		<pubDate>Sun, 19 Apr 2009 19:23:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-47133</guid>
		<description>Hi, 

great work with this article.
Did you notify the developers so they can incorporate it as a general fix?

Kind regards.</description>
		<content:encoded><![CDATA[<p>Hi, </p>
<p>great work with this article.<br />
Did you notify the developers so they can incorporate it as a general fix?</p>
<p>Kind regards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PowerShot S2 IS in Linux &#171; Ponderology</title>
		<link>http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-45695</link>
		<dc:creator>PowerShot S2 IS in Linux &#171; Ponderology</dc:creator>
		<pubDate>Fri, 09 Jan 2009 23:30:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-45695</guid>
		<description>[...] actually figuring out which rule was being enforced I had come across a custom fix (When digiKam Failed to Connect) that created a new rule. I only modified the group as I have a shared group [...]</description>
		<content:encoded><![CDATA[<p>[...] actually figuring out which rule was being enforced I had come across a custom fix (When digiKam Failed to Connect) that created a new rule. I only modified the group as I have a shared group [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-41855</link>
		<dc:creator>Ed</dc:creator>
		<pubDate>Mon, 26 May 2008 14:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-41855</guid>
		<description>Thanks a lot.
Saved me some time...

But things like :

&quot;/usr/lib/libgphoto2/print-camera-list udev-rules-0.98 group users mode 0660 &gt; /etc/udev/rules.d/90-libgphoto2.rules

&quot;

...shouldn&#039;t be necessary to get things working.

And even if so.....IT SHOULD BE MENTIONED IN THE ERROR MESSAGE !

( sorry for the caps....)

But now things work.
Thanks again.</description>
		<content:encoded><![CDATA[<p>Thanks a lot.<br />
Saved me some time&#8230;</p>
<p>But things like :</p>
<p>&#8220;/usr/lib/libgphoto2/print-camera-list udev-rules-0.98 group users mode 0660 &gt; /etc/udev/rules.d/90-libgphoto2.rules</p>
<p>&#8221;</p>
<p>&#8230;shouldn&#8217;t be necessary to get things working.</p>
<p>And even if so&#8230;..IT SHOULD BE MENTIONED IN THE ERROR MESSAGE !</p>
<p>( sorry for the caps&#8230;.)</p>
<p>But now things work.<br />
Thanks again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ante</title>
		<link>http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-39088</link>
		<dc:creator>ante</dc:creator>
		<pubDate>Sat, 19 Jan 2008 09:59:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-39088</guid>
		<description>Thanks a lot, it helped me by pointing to the correct location of the problem. 

I solved the problem in a different way, as Debian has a group plugdev and gives this group rwx-permission in the ruleset. So I simply added the allowed users to the plugdev group and won&#039;t have problems with the rules-file at the next updates.

BTW: It is fine, that you have included the error message in the post. In this way it could be googled. ;-)</description>
		<content:encoded><![CDATA[<p>Thanks a lot, it helped me by pointing to the correct location of the problem. </p>
<p>I solved the problem in a different way, as Debian has a group plugdev and gives this group rwx-permission in the ruleset. So I simply added the allowed users to the plugdev group and won&#8217;t have problems with the rules-file at the next updates.</p>
<p>BTW: It is fine, that you have included the error message in the post. In this way it could be googled. <img src='http://www.hyperborea.org/journal/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mica</title>
		<link>http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-37591</link>
		<dc:creator>Mica</dc:creator>
		<pubDate>Fri, 21 Dec 2007 13:36:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-37591</guid>
		<description>Thanks for the information!

It fixed the problem after my camera stopped working with a recommended kernel upgrade to FC7.

This also happened about 1 month earlier again with a kernel upgrade, however I was able to fix it on this occasion by updating the 50-udev.rules file (changing mode 0644 to 0666 for the usb device)

see http://www.fedoraforum.org/forum/printthread.php?t=170607 for further details

Great to see that the Linux community spirit is alive and well.

The rest of us certainly appreciate it!! :o)</description>
		<content:encoded><![CDATA[<p>Thanks for the information!</p>
<p>It fixed the problem after my camera stopped working with a recommended kernel upgrade to FC7.</p>
<p>This also happened about 1 month earlier again with a kernel upgrade, however I was able to fix it on this occasion by updating the 50-udev.rules file (changing mode 0644 to 0666 for the usb device)</p>
<p>see <a href="http://www.fedoraforum.org/forum/printthread.php?t=170607" >http://www.fedoraforum.org/forum/printthread.php?t=170607</a> for further details</p>
<p>Great to see that the Linux community spirit is alive and well.</p>
<p>The rest of us certainly appreciate it!! <img src='http://www.hyperborea.org/journal/wp-includes/images/smilies/icon_surprised.gif' alt=':o' class='wp-smiley' /> )</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: a cornellian</title>
		<link>http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-35863</link>
		<dc:creator>a cornellian</dc:creator>
		<pubDate>Sun, 18 Nov 2007 23:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-35863</guid>
		<description>thank you:)

fixed my problem as well</description>
		<content:encoded><![CDATA[<p>thank you:)</p>
<p>fixed my problem as well</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TSD</title>
		<link>http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-35789</link>
		<dc:creator>TSD</dc:creator>
		<pubDate>Sat, 17 Nov 2007 18:23:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.hyperborea.org/journal/archives/2007/11/14/digikam-permissions/#comment-35789</guid>
		<description>Thank you so much for your help! I panicked when my digiKam software stopped working after I reinstalled Fedora. Being a Linux newb I would have never figured out how to fix it, but with your instructions digiKam works fine!</description>
		<content:encoded><![CDATA[<p>Thank you so much for your help! I panicked when my digiKam software stopped working after I reinstalled Fedora. Being a Linux newb I would have never figured out how to fix it, but with your instructions digiKam works fine!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
