Fwd: Re: Re: Digikam support Nikon D3100

[Robert Zeller]

Gerlos,

thanks for the hint; I already found out that there was a process
"gvfs-gphoto2-volume-monitor" that grabbed the ptp-camera-device and
mounted it under $HOME/.gvfs/something. So killing  this process freed
the camera such that it could be mounted in digikam. But I was not aware
what started this process, so I did a chmod -x
/usr/lib/gvfs/gvfs-gphoto2-volume-monitor to prevent the gvfs-mounter to
be started again upon login. You are right: I just checked and found
that the nautilus process was running on my kde-desktop. After killing
nautilus, the gvfs-gphoto2-volume-monitor did not start again, even with
the x bit enabled.

Thanks again,

Robert



On 02/15/2011 12:52 AM, gerlos wrote:

> Il giorno 02/feb/2011, alle ore 13.20, Robert Zeller ha scritto:
>
>  
>> Gerlos et al.:
>>
>> I am having the same problem with my Nikon D200 in ptp mode (camera is
>> correctly recognized by DK; but no access to the images on the camera);
>> I completely agree with you that this is not a DK problem but related to
>> some strange mounting of the ptp-camera by some other application; here
>> are my findings:
>>
>> I am running two almost identical systems with the following configurations:
>> 1. PC : 64 bit system: SuSE 11.3, DK 1.8 ; kde 4.4.4
>> 2. Laptop : 32 bit system SuSE 11.3, DK 1.8  both systems have the same
>> software level
>>    
> [CUT]
>  
>> Anybody any ideas ???
>>    
>
> Sorry for the (maybe) stupid question, but I don't use neither know the default desktop environment of Suse 11.3.
> Are you running Digikam under KDE Plasma desktop or under Gnome?
>
> If you're running KDE, is there any Gnome app running when you are on KDE?
> The problem could be for example Nautilus that is running in the background (Nautilus doesn't have a "quit switch" like KDE's Dolphin), look at you task manager (ksysguard, htop, top, ...) or at the output of ps. Try to kill it, and look if it solves the problem.
>
> Usually one expects Digikam running fine under KDE Plasma because they both use the same system to mount/umount removable media (solid), but something could (COULD) go wrong if another system (such Gnome's one) tries to do the same thing  on your hardware.
>
> Remember, mine are just hints/ideas about possible interpretations of the problem -- I usually run Digikam under KDE Plasma (when I don't play with it under Mac Os X) and never had such problems (I neither have a Nikon SLR, anyway), so I can't test these things.
>
> good luck,
> gerlos
>
>
> --
> "Life is pretty simple: You do some stuff. Most fails. Some works. You do more
> of what works. If it works big, others quickly copy it. Then you do something
> else. The trick is the doing something else."
>            < http://gerlos.altervista.org >
>  gerlos  +- - - >  gnu/linux registred user #311588
>
>
>  

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[gerlos]

Il giorno 15/feb/2011, alle ore 12.48, Robert Zeller ha scritto:

> Gerlos,
[CUT]
> You are right: I just checked and found
> that the nautilus process was running on my kde-desktop. After killing
> nautilus, the gvfs-gphoto2-volume-monitor did not start again, even with
> the x bit enabled.


I'm happy I guessed right and helped you!

Hope that this hint can help other people too... why don't add this notice to the official Digikam documentation, to help people solve this problem in the future?

regards
gerlos

--
"Life is pretty simple: You do some stuff. Most fails. Some works. You do more
of what works. If it works big, others quickly copy it. Then you do something
else. The trick is the doing something else."
           < http://gerlos.altervista.org >
 gerlos  +- - - >  gnu/linux registred user #311588

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users