Red Hat Bugzilla – Bug 365891
kernel 18.104.22.168-10 breaks access to usb camera under KDE
Last modified: 2007-11-30 17:12:21 EST
Description of problem:
kernel22.214.171.124-10 breaks access to Canon sd110 under KDE
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.connect camera to USB port while running kde
2.try to access camera
access to camera's memory either through digikam, or as a USB storage device
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 126.96.36.199-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 188.8.131.52-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
This may be a duplicate of bug #362221.
Can you try to run "gphoto2 --debug --auto-detect --summary" and see if the
Created attachment 261621 [details]
Output of gphoto2 --debug --auto-detect --summary
Output of gphoto2 --debug --auto-detect --summary on Linux moby.eshu.net
184.108.40.206-49.fc8 #1 SMP Thu Nov 8 22:14:09 EST 2007 x86_64 x86_64 x86_64
As you see above, the problem persists to the latest F8 kernel. Since it's
absolutely essential to me that I be able to download photos from my camera and
upload them onto the net, I've kept my laptop w/ F7 where I have access to a
working configuration with a 2.6.22 kernel.
However, when I do boot into the 220.127.116.11-10 kernel, running gphotoq ... reveals
Created attachment 262411 [details]
a second run of gphoto --debug ...
gphoto2 --debug --auto-detect --summary output under Linux pequod.eshu.net
18.104.22.168-10.jpc1 #1 SMP Wed Oct 31 13:15:20 PDT 2007 i686 i686 i386 GNU/Linux
If this is F8, can you bump the version on the bug report which is still F7?
From the gphoto output, this does look like a duplicate of bug #362221 but I
assume both should be left open to track different Fedora releases - one F7 and
the other F8.
*** This bug has been marked as a duplicate of 362221 ***