Same problem with Slackware 14.1 and R14 GIT.

Connecting my Canon A590 Powershot results in a desktop icon appearing and a standard TDE dialog asking me what to do. Selecting 'Open in new window' results in Konqueror opening with an Error dialog  'Could not read file /.'. After acknowledging the Error dialog, the device does not appear in Konqueror media:/ (Storage Devices).

Same results for the root account, thereby eliminating permissions as the likely cause.

Downloading images through Digikam works. Inserting the camera's SDC device also works.

Connecting the camera worked previously with R14 GIT. I cannot say how long ago I connected the camera and opened in Konqueror because the last few times I used Digikam to copy the images to my computer.

I updated the bug report Summary to be more generic.

Fresh full TDE package set. I connected my Canon Powershot camera. An icon appeared on the desktop.

The new bug is the dialog no longer asks whether I want to open in Digikam.

Next, I selected the (only) option to open in a new window and a dialog appeared, "Could not read file /." Same problem previously reported.

Attempting to access the files as root does not works, as previously reported.

I now have to pull the memory card to access photo files or use a different desktop environment.

It looks like this camera uses the PTP protocol; other PTP protocol cameras work fine here so this must be an implementation-specific issue with the Kamera tdeioslave.

Did this camera work with older versions of TDE or did you test this camera first with R14?

Thanks!

(In reply to Darrell from comment #2)
> Fresh full TDE package set. I connected my Canon Powershot camera. An icon
> appeared on the desktop.
> 
> The new bug is the dialog no longer asks whether I want to open in Digikam.

This particular bug is now fixed in GIT.  DigiKam shipped its service files with a "desktop.in" suffix so I originally missed them when bringing the service types up to XDG standards.

>Did this camera work with older versions of TDE or did you test this
>camera first with R14?
I have used the camera with TDE for several years. I don't know when the /. dialog problem appeared.

With the latest digikam fix, the dialog now includes digikam in the options. I can again access photos that way. I have downloaded photos this way in TDE for so long that I can't say with any certainty how the camera functioned in TDE outside of digikam.

The problem might be permissions related. With the latest digikam fix, I can access the camera in konqueror as root but not as non-root. As non-root I receive the /. dialog. As root, the file permissions are 666.

(In reply to Darrell from comment #5)
> >Did this camera work with older versions of TDE or did you test this
> >camera first with R14?
> I have used the camera with TDE for several years. I don't know when the /.
> dialog problem appeared.
> 
> With the latest digikam fix, the dialog now includes digikam in the options.
> I can again access photos that way. I have downloaded photos this way in TDE
> for so long that I can't say with any certainty how the camera functioned in
> TDE outside of digikam.
> 
> The problem might be permissions related. With the latest digikam fix, I can
> access the camera in konqueror as root but not as non-root. As non-root I
> receive the /. dialog. As root, the file permissions are 666.

So digikam works but Konqueror does not?  That's an important clue.

Thanks!

Also the camera:/ protocol does not work. Probably related.

BTW, none of the protocol help guides appear in the help handbook. Probably a regression from the XDG updates.

(In reply to Darrell from comment #7)
> Also the camera:/ protocol does not work. Probably related.

Yep, AFAIK that uses the Kamera tdeioslave.  Unfortunately the PTP cameras I have access to (friends and family) all seem to work, though none of them advertise a "camera" folder (usually they advertise a folder with the name of the device).

> BTW, none of the protocol help guides appear in the help handbook. Probably
> a regression from the XDG updates.

Strange; I just tested this on my R14 development system and it seemed to work fine.  I opened the help center and selected various protocols from under the Protocols tree item with no issues.  Did you access them through a different mechanism?

Thanks!

>Yep, AFAIK that uses the Kamera tdeioslave.
Same result with a fresh profile.

>Did you access them through a different mechanism?
Using the Help option for the TDE menu. Same result with a fresh profile.

.xsession-error log shows several '[tdeinit] Got EXEC_NEW 'tdeio_kamera' from launcher' messages but nothing more. /var/log/messages shows the camera being recognized, but that was already known by the TDE dialog asking what to do and that digikam recognizes the file system.

The camera:/ protocol is not working with KDE 4.10 on the same Slackware system. The camera:/ protocol bug could be a Slackware problem, but there still is a problem with TDE konqueror.

If I connect an android (4.4) device as a camera (PTP device) I get the window:
Unknown Device 1-1:1.0 - TDE Daemon
Medium type: Camera
Open in New Window
digiKam Detect and Download
Do Nothing
-------
Selecting Open... brings up Konq with system:/media/Unknown Device 1-1:1.0
and Error - Konqueror
Could not read file /.

Selecting digiKam../ brings up Failed to auto-detect camera;...
-------

These both worked before 14.0, and auto-detecting also worked.

/var/log/messages has this:
Dec 19 12:34:15 vega1 kernel: [ 5089.828073] usb 1-1: new high-speed USB device number 12 using xhci_hcd
Dec 19 12:34:15 vega1 kernel: [ 5089.958592] usb 1-1: New USB device found, idVendor=18d1, idProduct=4ee6
Dec 19 12:34:15 vega1 kernel: [ 5089.958606] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 19 12:34:15 vega1 kernel: [ 5089.958612] usb 1-1: Product: Nexus 7
Dec 19 12:34:15 vega1 kernel: [ 5089.958618] usb 1-1: Manufacturer: asus
Dec 19 12:34:15 vega1 kernel: [ 5089.958622] usb 1-1: SerialNumber: xxxxxxx