[Digikam-devel] HAL and digikam download and detect does not work as expected

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[Digikam-devel] HAL and digikam download and detect does not work as expected

Oliver Dörr
Hi,

i just upgraded my KDE from 3.4.2 to 3.5.4. digikam is on 0.9 beta. I'll
get a dialog where i could select digikam detect and download, when  i
connect my camera Canon Powershot A80 to my computer and power it on.
(Great).

Sadly the next window thjat appears is a Error - KIOExec
File or folder / does not exists   (translated from german).

Starting digiKam and using the libgphoto driver works as expected.

Any ideas?
Oliver

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] HAL and digikam download and detect does not work as expected

Oliver Dörr
Hi,

i've just tried it with the konqueror and now i know that i have to set
the path first. However, my camera does not really work as mass storage
device.

Is it possible that digikam donwload and detect uses libgphoto2 instead?

Oliver

Oliver Dörr wrote:

> Hi,
>
> i just upgraded my KDE from 3.4.2 to 3.5.4. digikam is on 0.9 beta. I'll
> get a dialog where i could select digikam detect and download, when  i
> connect my camera Canon Powershot A80 to my computer and power it on.
> (Great).
>
> Sadly the next window thjat appears is a Error - KIOExec
> File or folder / does not exists   (translated from german).
>
> Starting digiKam and using the libgphoto driver works as expected.
>
> Any ideas?
> Oliver
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
>  
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] HAL and digikam download and detect does not work as expected

Marcel Wiesweg
In reply to this post by Oliver Dörr
> Hi,
>
> i just upgraded my KDE from 3.4.2 to 3.5.4. digikam is on 0.9 beta. I'll
> get a dialog where i could select digikam detect and download, when  i
> connect my camera Canon Powershot A80 to my computer and power it on.
> (Great).
>
> Sadly the next window thjat appears is a Error - KIOExec
> File or folder / does not exists   (translated from german).
>
> Starting digiKam and using the libgphoto driver works as expected.
>

If the media support finds a gphoto2 camera, it is supposed to use the
digikam-gphoto2-camera.desktop service.
(/usr/kde/3.5/share/apps/konqueror/servicemenus/)

This one will call "digikam-camera detect"
/usr/kde/3.5/share/apps/digikam/utils/digikam-camera detect
which start digikam with the --detect-camera option, if it does not yet run.

You can try if any of this works.
Unfortunately, I have no gphoto2 camera so I cannot test it.

Marcel

> Any ideas?
> Oliver
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] HAL and digikam download and detect does not work as expected

Oliver Dörr


Marcel Wiesweg wrote:
Hi,

i just upgraded my KDE from 3.4.2 to 3.5.4. digikam is on 0.9 beta. I'll
get a dialog where i could select digikam detect and download, when  i
connect my camera Canon Powershot A80 to my computer and power it on.
(Great).

Sadly the next window thjat appears is a Error - KIOExec
File or folder / does not exists   (translated from german).

Starting digiKam and using the libgphoto driver works as expected.

    

If the media support finds a gphoto2 camera, it is supposed to use the 
digikam-gphoto2-camera.desktop service. 
(/usr/kde/3.5/share/apps/konqueror/servicemenus/)
  
ok, I'll just checked all /opt/kde3/share/apps/konqueror/servicemenus/digikam-*. Only the gphoto related one has the name "digiKam Detect and Download". As i could see this one after connecting my camera, i'll suppose this works as expected. Even changing the name, lets the change appear on my desktop
This one will call "digikam-camera detect"
/usr/kde/3.5/share/apps/digikam/utils/digikam-camera detect
which start digikam with the --detect-camera option, if it does not yet run.
  
hmmm, /opt/kde3/share/apps/digikam/utils/digikam-camera detect works also as expected and starts digiKam and connects to the camera...

So the question is, why that does not work automatically the right way....

or other way around... What is he starting?

Any ideas?
Oliver

 

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] HAL and digikam download and detect does not work as expected

Hubert Figuiere-3
In reply to this post by Oliver Dörr
On Sunday 06 August 2006 13:45, Oliver Dörr wrote:

> i've just tried it with the konqueror and now i know that i have to set
> the path first. However, my camera does not really work as mass storage
> device.

Like any Canon. No Canon camera work as mass storage

> Is it possible that digikam donwload and detect uses libgphoto2 instead?

It should do that.  (0.8.x does at least)

Hub
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: [Digikam-devel] HAL and digikam download and detect does not work as expected

Marcel Wiesweg
In reply to this post by Oliver Dörr
> ok, I'll just checked all
> /opt/kde3/share/apps/konqueror/servicemenus/digikam-*. Only the gphoto
> related one has the name "digiKam Detect and Download". As i could see
> this one after connecting my camera, i'll suppose this works as
> expected. Even changing the name, lets the change appear on my desktop
>
> > This one will call "digikam-camera detect"
> > /usr/kde/3.5/share/apps/digikam/utils/digikam-camera detect
> > which start digikam with the --detect-camera option, if it does not yet
> > run.
>
> hmmm, /opt/kde3/share/apps/digikam/utils/digikam-camera detect works
> also as expected and starts digiKam and connects to the camera...
>
> So the question is, why that does not work automatically the right way....
>
> or other way around... What is he starting?

One idea, the other two desktop files contain a "%u" in their exec string. I
have a faint memory there was some problem with this at a time, but I don't
know any more. What happens if media:/ wants to call the service with an URL
argument? Is a "%u" required?
How the KDE media support works internally is unfortunately a great mystery to
me, I don't know where to look.

Marcel

>
> Any ideas?
> Oliver
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel