Version: 0.9.2-final (using KDE 3.5.7, compiled sources) Compiler: Target: i486-slackware-linux OS: Linux (i686) release 2.6.21.5-smp If I leave the Camera window not used for a long time, the connection "expires" (probably because the camera turns itself off). If I want to perform some actions then (e.g. delete or download some images), I get only message saying that digikam cannot connect to the camera. I have to close the window and open it again (from Camera menu), which takes long because digikam reads all the contents of the camera again. In this case, digikam could ask if I want to reconnect, and try it (but not re-reading the content), and then perform desired action (like deleting or downloading images).
Of course, before confirming the "Do you want to try to reconnect..." dialogue box, I would turn the camera on again.
*** Bug 116904 has been marked as a duplicate of this bug. ***
*** Bug 119255 has been marked as a duplicate of this bug. ***
I think it's fully relevant of background deamon, who initialize UBS device list connected to computer. Here digiKam do not manage it as well... Marcus, your viewpoint ? Gilles Caulier
Lifetime management of a plugged in camera is difficult. Strategies: - Watch for udev / hotplug events when the camera is removed and either close the dialog. I am not sure if KDE offers such a framework. - As long as dialog is open try pinging the camera regulary might work, but then what if you forget this window and the camera battery is drained. - Or, detect IO error from the libgphoto2 API calls and reconnect after popping up a dialog? GNOME has a "gvfs" gphoto2 daemon which will attach to the cameras as soon as it plugged (and currently not let go from it). They see however a switch off and then unplug the service (after udev events). Suggestion is either to handle plug/unplug events ... or just ignore the issue for now (and hope users use it in a single shot import fashion usually).
Marcus, Thanks for the feedback. For the moment, this entry is out of scope... Gilles Caulier