Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: When I attach my Canon EOS 400D camera (PTP device) to my computer, it is automatically mounted by gvfs. However, the Nautilus browser window does not open. There is an "Opening Canon Digital Camera" entry in the window list, and I see a spin-pointer cursor, but the window does not open. Otherwise, I can double-click the camera icon on the desktop and access the files without problem. Every time I attach the camera, the following is added to ~/.xsession-errors: mount: -c: line 0: unexpected EOF while looking for matching `"' mount: -c: line 1: syntax error: unexpected end of file Version-Release number of selected component (if applicable): gvfs-gphoto2-1.4.3-1.fc12.x86_64 nautilus-2.28.4-1.fc12.x86_64 How reproducible: Always. Steps to Reproduce: 1. Attach and switch on camera. Actual results: Camera mounted, no browser window. Expected results: Camera mounted, browser window.
This problem seems to go away if I set the action for Photos to "Open Folder". So this could be a nautilus or gthumb bug. I'll change the component to Nautilus as it's a common thread here. gthumb-2.10.11-6.fc12.x86_64
I'm not sure i understand, the old action was to launch gthumb, and that didn't succeed in launching gthumb, but if you change it to open folder it succeeds in opening nautilus?
Apologies for the confusing early bug report, I had become accustomed to an earlier behaviour where Nautilus opened a window for the camera (I believe by default). Somewhere this got changed, leading to the odd behaviour, which I think I now understand better: The Open Folder action works correctly. However, I think choosing Import with gThumb fails because gthumb-importer tries to get the USB device via libgphoto2. However this is already in use via gvfsd, so it fails with a device-busy error, which in this case manifests as it silently failing to bring up an import window. This seems to be a duplicate of bug 552890, bug 553934, etc. I'll alter the component and description of this bug accordingly and then close as a duplicate. *** This bug has been marked as a duplicate of bug 553934 ***