Bug 365891

Description of problem:
kernel2.6.23.1-10 breaks access to Canon sd110 under KDE

Version-Release number of selected component (if applicable):
2.6.23.1-10 

How reproducible:
every time

Steps to Reproduce:
1.connect camera to USB port while running kde
2.try to access camera
3.experience frustration
  
Actual results:
abject failure

Expected results:
access to camera's memory either through digikam, or as a USB storage device

Additional info:
When I connect this camera I get a KDE panel asking if I want to (1) open it in
a new window, (2) digikam detect and download, or (3) do nothing.

Under earlier kernels, I could access the photos on the camera by any of these
three routes. In case (1) digikam launches and throws up a window for the
camera; it then puts up a panel telling me that it cannot access the camera,  to
check that it is turned on and properly connected, and asks if I want to retry
or abort. Choosing retry the connection succeeds and the digikam camera window
show me the photos on the camera. In case (2), a new konqueror window appears
and presents me with a list of the photos on the camera. In case (3), I launch
digikam, open the camera from the camera menu, and proceed as in case (1).

Under kernel 2.6.23.1-10, in cases (1) and (3), digikam fails fails and throws
up the warning panel ad infinitum, as long as I press retry. Pressing abort and
starting a new from the camera menu behaves identically. In case (2), the
konqueror window opens, but informs me that it cannot access the device.

With earlier kernels, in cases (1) and (3) lsof shows a single digikam process
accessing the usb device in question, and no instances of kio_kamera are
running. With kernel 2.6.23.1-10, a dozen or so instances of kio_kamera process
are launched  in any of the three cases, and in cases (1) and (3), lsof shows
them contending amongst themselves and with 2 or 3 digikam process for the USB
device.