Bug 356662 - dolphin 15.08 does not know the camera protocol
Summary: dolphin 15.08 does not know the camera protocol
Status: RESOLVED FIXED
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: kamera (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Marcus Meissner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-14 09:46 UTC by Éric Brunet
Modified: 2016-02-23 18:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Éric Brunet 2015-12-14 09:46:20 UTC
When plugging my fujifilm X10 camera, which uses the PTP protocol, in a fedora 23 with kde, nothing happens. When I plug the same camera in a fedora 21, the device notifier pops up and gives me some options. The fact that nothing happens on the fedora 23 is an annoying bug by itself, but it is not really the bug I want to report now.

On the fedora 21 machine, I can browse and modify the files on the camera from within dolphin by entering the url "camera:/". On fedora 23, entering "camera:/" gives me an "invalid protocol" error message.

Of course, fedora 21 uses dolphin 15.04.0 based on kde 4.14.11, while fedora 23 uses dolphin 15.08.1 based on kde frameworks 5.16.0. I presume that the camera ioslave was not ported to kde 5.

As a matter of fact, if I fire good old konqueror on the fedora 23 computer, I can access the filesystem on the camera by entering the "camera:/" url. konqueror is still a kde 4 application.

This is a very serious regression. In 2015, one expects to have a window popping up when plugging a camera and having no trouble browsing the files on it. Is there any way to make dolphin5 use the kde4 kioslave ? Is there a plan porting the kioslave to kde5 ?

For information, the relevant output from "solid-hardware5 list details" when the camera is plugged:

udi = '/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3/1-1.3.2'
  parent = '/org/kde/solid/udev'  (string)
  vendor = '04cb'  (string)
  product = 'USB PTP Camera'  (string)
  description = 'Appareil photo'  (string)
  Block.major = 189  (0xbd)  (int)
  Block.minor = 8  (0x8)  (int)
  Block.device = '/dev/bus/usb/001/009'  (string)
  Camera.supportedProtocols = {'ptp'}  (string list)
  Camera.supportedDrivers = {'gphoto'}  (string list)



Reproducible: Always
Comment 1 Éric Brunet 2015-12-14 09:55:03 UTC
Still experimenting with this issue, on the fedora 23 computer:

$ kioclient ls camera:/
Fuji%20FinePix%20X10@usb:001,009
$ kioclient5 ls camera:/
couldn't create slave: "Unable to create io-slave:\nklauncher said: Protocle « camera » inconnu.\n"
"Could not start process Unable to create io-slave:\nklauncher said: Protocle « camera » inconnu.\n"

("Protocole camera inconnu" is of course french for "camera protocol is unknown". I don't know why english and french are mixed up in the error message.)
Comment 2 Christoph Feck 2015-12-15 00:30:32 UTC
The kio-kamera slave was only recently ported to Qt5 and is now part of the KDE Applications 15.12 release. Please check if this version works.
Comment 3 Éric Brunet 2015-12-15 08:20:21 UTC
Excellent news. 15.12 does not seem to be released yet, I'll wait a few days in the hope that I'll find some already compiled packages and I'll report back.

Thanks.
Comment 4 Éric Brunet 2015-12-18 10:27:54 UTC
So, on my uptodate fedora 23, I downloaded the file
http://mirror.rit.edu/archlinux/testing/os/x86_64/kamera-15.12.0-1-x86_64.pkg.tar.xz
from the archlinux distribution and manually put the files kcm_kamera.so and kio_kamera.so
into /usr/lib64/qt5/plugins, and the files camera.protocol and kamera.desktop into /usr/share/kservices5, and the file solid_camera.desktop into /usr/share/solid/actions. In logged out of my kde session, logged in again and tried my camera.

1) on plugging my camera, a notification happens, and I can click on the "devices" icon to look at my possible actions. Good.
2) it proposes to open my camera in the file manager. Good.
3) clicking on the action, dolphin opens. I can browse my camera, display previews and copy files from my camera to the computer file system. Good.
4) HOWEVER, if I click on a photo to open it, it fires up okular which fails to open the photo: okular's window appears empty, and after about fifteen seconds an error window appears with the message:

Could not open
camera:/Fuji%2520FinePix%2520X10@usb:001,006/store_10000001/DCIM/111_FUJI/DSCF1377.JPG. 
Reason: Unknown error
Impossible de communiquer avec le périphérique USB

(the last sentence being "impossible to communicate with the USB device")

After closing the error message in okular, I can go to the File->Open Recent dialog. The URL of the photo I tried to open is there and if I attempt to open it from here, it works AFTER A COUPLE OF TRIES. (On the first tries it usually fails with the same error message, but without the fifteen second wait. After a couple of atttempts it works, and once it worked, all the subsequent tries work also)

From okular, I can also go to the File->Open dialog, and type camera:/ and access my files without any problem.

And now, for the very weird stuff: from dolphin, if I right-click a file to open the contextual menu, select  "open with" and then "okular", it works most of the time: the file opens. Sometimes, it opens after a very small wait (1 second), sometimes one has to wait about 10 seconds, sometimes it fails after 15 seconds.

I cannot make sense of this!
So, okular is not a kf5 application
Comment 5 Marcus Meissner 2015-12-18 17:02:38 UTC
The second issue is unrelated to the first, for such please open new bugs.

I think the second one is caused by the fact that only 1 process can access the camera. the kioslave in dolphin/konqueror is still open, but the one for okular tries to access the camera, getting blocked.

as the kioslave will autoclose the camera after some seconds, you will be getting success if you reload after some seconds
Comment 6 Éric Brunet 2016-02-23 18:31:10 UTC
I confirm that kamera-15.12 allows dolphin to browse the camera. I am marking this bug as resolved(fixed).

I have opened bug 359714 to cover the second issue, the fact that clicking on a file from the camera from dolphin fails to open okular on that file, even though okular by itself is able to open it.


(In reply to Marcus Meissner from comment #5)
> The second issue is unrelated to the first, for such please open new bugs.
> I think the second one is caused by the fact that only 1 process can access
> the camera. the kioslave in dolphin/konqueror is still open, but the one for
> okular tries to access the camera, getting blocked.
> as the kioslave will autoclose the camera after some seconds, you will be
> getting success if you reload after some seconds