I can not reproduce this here. Do you see the button delete? This does not work? Is there an error? Is it a mass storage device? If so, could you check the permissions of the images?

I have only these two icons in the camera-dialog

http://web5.h5743.serverkompetenz.net/temp/_digikam-cam.png

Also with right click on a image I can't choose "delete" or sth.!?!?

Could you do a cvsup? Then you will see the option to delete images from the camera. 

Could you please explan "cvsup"? What to do exactly?

Isn't 0.7.0-cvs the latest version (I have it from the apt repos.)?

Thanks

Re-checkout CVS. Camera interface have been re-written this week. Look at this url :

http://digikam3rdparty.free.fr/newcamerainterface.png

Apt-repo?  Oh, I have not updated the pkgs for some time.
The new cameraclient is not in the cvs20040921 build.

Please try again.  I've build new pkg.  There no RMB
menu, but you can delete images from the camera with
a popdown menu in the lower right corner.

When reporting problem with debian pkg please specify
the version (e.g. reportbug --template digikam or
dpkg -l digikam).

Achim

@Achim Bohnet
I use apt with SuSE !!!

You only build debian pkg?

Hmm, I triad the install the latest cvs-version by saving the lines from http://digikam.sourceforge.net/Digikam-SPIP/rubrique.php3?id_rubrique=11 (the script.. removed the <br>-tags...)

But this didn't work :-(

Now I CAN'T start digikam any more :-(((

I get this KDE-Crash error when I start the program: 

-------------------------------------------------------------
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 12764)]
[KCrash handler]
#5  0x003a0062 in ?? ()
#6  0x40ee86f0 in QObject::QObject () from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0x401816c6 in Plugin (this=0x81d7038, instance=0x81d7e20, 
    parent=0x81c1470, name=0x41c1de37 "CDArchiving") at plugin.cpp:48
#8  0x41c06699 in Plugin_CDArchiving (this=0x81d7038, parent=0x81c1470)
    at plugin_cdarchiving.cpp:52
#9  0x41c082f3 in KDEPrivate::ConcreteFactory<Plugin_CDArchiving, QObject>::create (parent=0x81c1470, name=0x0, args=@0xbfffedb0) at kgenericfactory.tcc:167
#10 0x41c0827b in KDEPrivate::ConcreteFactory<Plugin_CDArchiving, QObject>::create (parentWidget=0x0, widgetName=0x0, parent=0x81c1470, name=0x0, 
    className=0x4127405c "QObject", args=@0xbfffedb0)
    at kgenericfactory.tcc:132
#11 0x41c0815d in KGenericFactory<Plugin_CDArchiving, QObject>::createObject (
    this=0x81c4ec0, parent=0x81c1470, name=0x0, 
    className=0x4127405c "QObject", args=@0xbfffedb0) at kgenericfactory.h:193
#12 0x40a4a191 in KLibFactory::create () from /opt/kde3/lib/libkdecore.so.4
#13 0x40185f8f in createInstanceFromFactory<KIPI::Plugin> (factory=0x81c4ec0, 
    parent=0x81c1470, name=0x0, args=@0xbfffedb0) at componentfactory.h:62
#14 0x40185f18 in createInstanceFromLibrary<KIPI::Plugin> (
    libraryName=0x81cd7f8 "kipiplugin_cdarchiving", parent=0x81c1470, 
    name=0x0, args=@0xbfffedb0, error=0xbfffedc8) at componentfactory.h:144
#15 0x40184da2 in KIPI::PluginLoader::loadPlugin (this=0x81c3668, 
    info=0x81c5860) at pluginloader.cpp:264
#16 0x40184cdb in KIPI::PluginLoader::loadPlugins (this=0x81c3668)
    at pluginloader.cpp:254
#17 0x400b4091 in DigikamApp::loadPlugins () from /opt/kde3/lib/libdigikam.so.0
#18 0x400b8780 in DigikamApp::DigikamApp () from /opt/kde3/lib/libdigikam.so.0
#19 0x0804a830 in main ()

-------------------------------------------------------------

Any idea?

just to clarify, suse has started providing snapshot rpms from cvs (which may or may not be a good thing). regarding your question, i have a feeling that you are mixing rpms (of libkipi, kipi-plugins, kexif, digikam) with cvs. if you want correct behavior, you will have to either stick to using only rpms or only cvs. if you plan on using the cvs version, first make sure that no stale rpms have been left behind.
rpm -qa |grep -i kipi => this will show if you have libkipi or kipi-plugins installed from rpm. if yes, uninstall them
rpm -qa |grep -i kexif => will show any installed libkexif from rpm. uninstall.

now recheckout the cvs versions of the above packages and recompile and reinstall them. order of compilation and installation: libkexif, libkipi, kipi-plugins and then digikam

@Renchi Raju

I've deleted all rpms (libkexif, libkipi, kipi-plugins and then digikam) and run the script (http://digikam.sourceforge.net/Digikam-SPIP/rubrique.php3?id_rubrique=11) again. But I get errors...

Look here please: http://paste.phpfi.com/31448

What's the problem?

looks like you are missing imlib2 development package. the script isn't very smart at detecting errors during individual steps. the configure step should have failed at not detecting imlib2. i would recommend doing each of the steps mentioned in the script by hand and checking the output of the step before proceeding. 

for any further questions please use the digikam user mailing list, as your queries can be better answered there and bugs.kde.org is not suited for this purpose.

Hi 

Information:
I am using Slackware 10.1, my "Concord (Eye) Easy Too" Digital camera (as Argus DC-1510) NOW Works by installing these packages:

   1. libgphoto2-2.1.5
   2. gphoto2-2.1.5
   3. digikam-0.6.2

BUG:
As ROOT user I can access the photos and save them, but as user "rizwaan" i get error message:

"Failed to initialize camera.
Please ensure camera is connected properly and turned on."


SHOULD BE Behavior:
Digikam is a wonderful application which is bridging the gap for the desktop users.

So, Please, please, please, on the first run, make a digikam-wizard, much like k3b-wizard, which will configure everything for the user. instead of the user reading lots of documentation to find out that the issues are with permissions and ownerships...

Still I am not able to access the CAMERA as user 'rizwaan'. and I don't have other users :)

Thank you very much for a wonderful application which eases home users' life.