Bug 113430

Summary:	camera detection via konqueror
Product:	[Unmaintained] kio	Reporter:	Daniel Moyne <dmoyne>
Component:	kamera	Assignee:	Marcus Meissner <marcus>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	null
Priority:	NOR
Version:	3.4.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Daniel Moyne 2005-09-27 12:42:05 UTC

Version:           3.4.2 (using KDE 3.4.2, Kubuntu Package 4:3.4.2-0ubuntu0hoary2 )
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-8ubuntu2)
OS:                Linux (i686) release 2.6.10-5-k7

camera detection with konqueror is cahotic : though KDE Conrol center detects my Powershot A80 Canon camera with the test option and an camera icon pops up on the desktop no way to see the pictures in the poposed "camera://...." URL with Konqueror ; eventually I have to use Gtkam to do the job ; this latter application has no problem with automatic camera detection and then review + dowload of pictures !

Comment 1 Marcus Meissner 2006-04-26 22:49:07 UTC

the desktop icon is not from the kamera kio slave.

what happens if you ppen the URL

camera:/

in konqueror? does it list the camera? can you browse it>?

Comment 2 Daniel Moyne 2006-06-05 21:53:45 UTC

if I do :
Marcus,
if I use "camera:/" URL with konqueror it does open camera memory through my "Canon PowerShot A80" directory and works !

media:/camera
shows the "Canon PowerShot A80" directory but I cannot get anything out of it by double clicking on the directory icon

By the way even after KDE 3.5.3 migraztion I experience the same problem ; the solution is to use Konqueror with "camera:/"

Comment 3 null 2018-08-05 22:37:33 UTC

If it works with camera:/ but not media:/camera, there might be an issue in the media:/ kioslave. However, the latter is not shipped with KF5 anymore (IIRC it was last used in KDE 3).

I'm closing this now, but feel free to open a new bug if the Plasma based device notifier still has problems accessing your images.

Comment 4 null 2018-08-05 22:42:06 UTC

*** Bug 127931 has been marked as a duplicate of this bug. ***