For the record, the problem seemed to manifest itself when the memory
card in the camera was heavily utilised. Having fewer images stored on
the card seemed to make it less likely for the process of connecting to
stall. What I did notice was that the initialisation of hotplugged
devices did become
** Changed in: digikam
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to digikam in ubuntu.
https://bugs.launchpad.net/bugs/304193
Title:
digiKam fails to connect to a previously recognised/registered camera
Assuming fixed.
** Changed in: digikam (Ubuntu)
Status: Incomplete = Fix Released
--
digiKam fails to connect to a previously recognised/registered camera
https://bugs.launchpad.net/bugs/304193
You received this bug notification because you are a member of Kubuntu
Bugs, which is
Upstream bug was marked as FIXED.
Can you still reproduce this with recent version of Digikam (0.9.4/KDE3 or
0.10.0/KDE4).
You can get test packages for Ubuntu/Intrepid here:
https://launchpad.net/~digikam-experimental/+archive/ppa
** Bug watch added: KDE Bug Tracking System #100714
** Changed in: digikam
Status: Unknown = Fix Released
--
digiKam fails to connect to a previously recognised/registered camera
https://bugs.launchpad.net/bugs/304193
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to digikam in ubuntu.
--
I also found that if I open the Add camera... dialogue, edit the
existing camera, change the camera model and then change it back (so
that the dialogue thinks a change has been made), then press OK (and OK
to close the list of cameras), the connection problem seems to go away.
This is a better
