Bug 533691

David, any idea ?

(In reply to comment #1)
> David, any idea ?  

Not really, seems like a gthumb problem to me - I mean, the device is mounted and there's a DCIM folder so...

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Yes, I can confirm that gthumb worked just fine in F11, and it no longer works in F12 (despite nautilus seeing the DCIM dir just fine).

I would say this is a fairly important bug, as dealing with one's pictures is an important operation in today's desktop.

Any progress with this issue, it would be nice to have my camera working again properly with gthumb.

I confirm the problem with Fedora 12.

gthumb-2.10.11-6.fc12.x86_64
DeviceKit-disks-009-3.fc12.x86_64
gvfs-1.4.3-1.fc12.x86_64

I think it's important to note that, in my case, I am using a card reader.

I see that when I plug it in, the system detects and mounts it just fine:

Dec 20 11:45:12 mteixeira kernel: usb 1-8: new high speed USB device using ehci_hcd and address 5
Dec 20 11:45:12 mteixeira kernel: usb 1-8: New USB device found, idVendor=0cf2, idProduct=6225

The Nautilus asks what I want to do with it. I select to open with gThumb, then I see:

Dec 20 11:45:23 mteixeira gnome-keyring-daemon[1801]: removing removable location: /media/7845-C2F9
Dec 20 11:45:23 mteixeira gnome-keyring-daemon[1801]: no volume registered at: /media/7845-C2F9

If I look at /media, there is nothing mounted.

After that, gThumb opens the import window, but says "No camera found".

If I mount the device (sdc1) manually, gThumb finds the device and is able to import the photos just fine.

This bug is related to https://bugzilla.redhat.com/show_bug.cgi?id=540039

I plug in the media (either in the camera via USB or directly in the card reader), and it is automounted. As soon as I start gthumb either in the device notifier or by pressing the "Photos detected: Start gthumb?"-Button in Nautilus, the device is immediately unmounted.

Here's the log (at 14:19:30 I start gthumb):

Dec 30 14:18:22 rotezora kernel: sd 4:0:0:3: [sdf] 1986560 512-byte logical locks: (1.01 GB/970 MiB)
Dec 30 14:18:22 rotezora kernel: sd 4:0:0:3: [sdf] Assuming drive cache: write through
Dec 30 14:18:22 rotezora kernel: sd 4:0:0:3: [sdf] Assuming drive cache: write through
Dec 30 14:18:22 rotezora kernel: sdf: sdf1
Dec 30 14:19:32 rotezora gnome-keyring-daemon[1696]: removing removable location: /media/disk
Dec 30 14:19:32 rotezora gnome-keyring-daemon[1696]: no volume registered at: /media/disk

Gthumb then starts with the "Could not lock device" error mentioned in Bug 540039.

This bug is still and issue with up to date Fedora 12 as of 2010/3/19. Can still see the files in nautilus and it auto opens gthumb for me, but gthumb can't see any images on the camera.

I opened this bug 5 months ago, this is getting a little long for this type of issue.

Hi,

I using gthumb-2.10.11-8.fc12.x86_64 and I have exactly the same problem as described here no matter what digital camera I try to connect. Any idea on how to fix this, besides just manually copying the pictures?

Thanks!
Enrique

Hi Kevin, Enrique,

First of all from a terminal do:
rmdir $HOME/.gthumb-importer.lock

Can you both describe your problem with a bit more details. Plug in your camera, and then what happens ? Does gthumb pop up, and / or does nautilus pop up ? Do you get any error messages or just an empty pictures list in gthumb. What sort of camera are you using?

After plugging in the camera, and before doing the unmounting described below
please run the following command from a terminal:

ls -l .gvfs

And paste the output here.

Then try the following, go to places->computer, right click on your camera and select unmount. Then start a terminal and from that terminal run
gthumb-importer

Please also let me know if gthumb-importer shows any messages, and if it
does work now.

(In reply to comment #10)
> Hi Kevin, Enrique,

Hi Ian, I have the same issue and I'll try to describe what happens to me.

> First of all from a terminal do:
> rmdir $HOME/.gthumb-importer.lock

There is no such file on my system.
 
> Can you both describe your problem with a bit more details. Plug in your
> camera, and then what happens ? Does gthumb pop up, and / or does nautilus pop
> up ? Do you get any error messages or just an empty pictures list in gthumb.
> What sort of camera are you using?

1. I plug my camera (a Casio Exilim wx-z110) and I turn it on.

2. I see it in /var/log/messages:

Apr  6 21:25:22 localhost kernel: usb 6-1: new full speed USB device using uhci_hcd and address 2
Apr  6 21:25:22 localhost kernel: usb 6-1: New USB device found, idVendor=07cf, idProduct=1004
Apr  6 21:25:22 localhost kernel: usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr  6 21:25:22 localhost kernel: usb 6-1: Product: CASIO QV DIGITAL
Apr  6 21:25:22 localhost kernel: usb 6-1: Manufacturer: CASIO COMPUTER
Apr  6 21:25:22 localhost kernel: usb 6-1: configuration #1 chosen from 2 choices
Apr  6 21:25:22 localhost kernel: Initializing USB Mass Storage driver...
Apr  6 21:25:22 localhost kernel: scsi6 : SCSI emulation for USB Mass Storage devices
Apr  6 21:25:22 localhost kernel: usbcore: registered new interface driver usb-storage
Apr  6 21:25:22 localhost kernel: USB Mass Storage support registered.
Apr  6 21:25:27 localhost kernel: scsi 6:0:0:0: Direct-Access     CASIO    DIGITAL_CAMERA   1.00 PQ: 0 ANSI: 0 CCS
Apr  6 21:25:27 localhost kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
Apr  6 21:25:27 localhost kernel: sd 6:0:0:0: [sdb] 1950720 512-byte logical blocks: (998 MB/952 MiB)
Apr  6 21:25:27 localhost kernel: sd 6:0:0:0: [sdb] Write Protect is off
Apr  6 21:25:27 localhost kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr  6 21:25:27 localhost kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr  6 21:25:27 localhost kernel: sdb: sdb1
Apr  6 21:25:27 localhost kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr  6 21:25:27 localhost kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk

3. Device is mounted. I see an icon on the desktop and I can navigate the device with Nautilus.

4. At the same time I get a pop-up asking me if I want to open a program to import my photos. The default is gthumb. I click the OK button.

5. Device is (I think) unmounted. I can no longer see the icon on the desktop and doing "ls /media" shows no subdirectory.

6. Gthumb is launched and I get the following error:

"Si è verificato un errore nella libreria di I/O ("Impossibile bloccare il dispositivo"): La fotocamera è già in uso."

Sorry, It's in Italian. A translation is:

"An error occurred in the I/O library ("It is not possible to lock the device"): the camera is already in use."

> After plugging in the camera, and before doing the unmounting described below
> please run the following command from a terminal:
> 
> ls -l .gvfs
> 
> And paste the output here.

The directory is empty.

> Then try the following, go to places->computer, right click on your camera and
> select unmount. Then start a terminal and from that terminal run
> gthumb-importer
> 
> Please also let me know if gthumb-importer shows any messages, and if it
> does work now.    

Although I no longer see a device mounted in /media, an icon for the device is still present in "Computer" and I cannot unmount it.

I unplug the camera and plug it back. I press Cancel on the pop-up (point 4). I unmount the camera. I still see an icon in the "Computer" panel.

I run gthumb-importer from a terminal. There is no output in the terminal and I get the same error (point 6).

HTH,

Andrea.

Andrea,

Thanks for the info, a common denominator in people with problems seems to be they have cameras which present themselves as mass storage devices.

Can you edit /usr/bin/gthumb-importer (it is a script), and comment out
the part where it unmounts the gvfs share (this is needed for proprietary protocol and ptp cams), and see if that helps ?

If it helps can you do "ls -l ~/.gvfs" again after plugging in the camera ?

Thanks,

Hans

(In reply to comment #12)
> Andrea,
> 
> Thanks for the info, a common denominator in people with problems seems to be
> they have cameras which present themselves as mass storage devices.
> 
> Can you edit /usr/bin/gthumb-importer (it is a script), and comment out
> the part where it unmounts the gvfs share (this is needed for proprietary
> protocol and ptp cams), and see if that helps ?

I just run "gthumb --import-photos" because that was almost what it remains if I comment out the unmount part of gthumb-importer script and ... roll of drums... it works :)

> If it helps can you do "ls -l ~/.gvfs" again after plugging in the camera ?

It's an empty directory.

$ ls -la ~/.gvfs
totale 4
dr-x------.   2 andrea andrea    0  6 apr 20:53 .
drwxr-xr-x. 126 andrea andrea 4096  6 apr 22:30 ..


Bye,

Andrea.

(In reply to comment #13)
> It's an empty directory.
> 
> $ ls -la ~/.gvfs
> totale 4
> dr-x------.   2 andrea andrea    0  6 apr 20:53 .
> drwxr-xr-x. 126 andrea andrea 4096  6 apr 22:30 ..
> 

Hmm, that is rather weird, because the unmount part of the
gthumb-importer script does the following:

if [[ "$1" =~ "$HOME/.gvfs/.*gphoto2" ]]; then
    gvfs-mount --unmount "$1"
fi

gthumb --import-photos

So if there is nothing under ~/.gvfs, then how can running
gthumb --import-photos instead of gthumb-importer
make a difference ?

I mean having nothing under ~/.gvfs makes sense as this is
a mass storage device, so its mounted under /media,
but then when nautilus calls gthumb-importer to import the photo's
gthumb-importer gets called with a /media/foo path, and should do
nothing but call gthumb --import-photos, can you debug this a bit further:

put debug echo's in the script and echo to a file under /tmp, then unplug camera, plug it in again and when asked what to do choose the default action.

Also maybe do an "ls -l ~/.gvfs > /tmp/gvfs.ls" at the beginning of the script

Regards,

Hans

Well, I debugged it a bit better.

I don't think that the /usr/bin/gthumb-importer script is the one called from the Nautilus pop-up when inserting the camera. It must be something else. 

If I run the aformentioned script from the command line, everything is fine. It even prints the echo I put in the script (only the gthumb --import-photos line and following are executed).

However, if I choose the gthumb action in the Nautilus pop-up, this script is not run (there are no files in /tmp).

How can I check what application is called from Nautilus?

(In reply to comment #15)
> How can I check what application is called from Nautilus?    
>

I'm afraid I don't know, the best place to ask is probably #fedora-desktop, which is a channel on gimpnet (not on freenode).

I think I have found the problem. In the Fedora gthumb package there are 3 desktop files:

/usr/share/applications/gthumb-import.desktop
/usr/share/applications/gthumb-importer.desktop
/usr/share/applications/gthumb.desktop

The latter is the one shown in the desktop menu, the others are the ones that appears in the Nautilus pop-up after plugging-in the USB camera. Yes, I didn't notice but there are actually two different gthumb entries in the pop-up!

The default one is gthumb-import.desktop. If I remove this file (or if I choose the other gthumb entry in the pop-up) I can successfully import photos. 

gthumb-import.desktop has the following Exec parameter:

Exec=sh -c 'gvfs-mount -u "%U"; exec gthumb --import-photos'

While the other, gthumb-importer.desktop, has this one instead:

Exec=gthumb-importer %U

gthumb-importer.desktop is provided by Fedora. gthumb-import.desktop is provided by upstream.

Andrea,

Thanks that is great detective work, an update fixing this is on its way.

Regards,

Hans

gthumb-2.10.11-9.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/gthumb-2.10.11-9.fc12

gthumb-2.10.11-9.fc12 seems to fix it for me.

gthumb-2.10.11-9.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update gthumb'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gthumb-2.10.11-9.fc12

gthumb-2.10.11-9.fc12 seems to fix the bug for me too.

Cool. I had been looking for this since months!

Please put the patch into production. In any case it is better than the present broken version.

gthumb-2.10.11-9.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.