Version: (using KDE 4.3.1) OS: Linux Installed from: Ubuntu Packages When trying to access a PTP camera (Nikon D90) as 'dolphin camera:/', I can navigate down in the file structure a few directories, but then I get either of these error messages: Unknown error code 150 Bad parameters or Could not lock device and although I can sometimes access the list of pictures, copying them somewhere fails. dmesg contains these lines: [ 1556.916039] usb 1-2: new high speed USB device using ehci_hcd and address 7 [ 1557.049156] usb 1-2: configuration #1 chosen from 1 choice [ 2176.551617] kio_kamera[2052]: segfault at 95515ac8 ip 02c2bfb8 sp bf82f510 error 4 in libc-2.10.1.so[2bfd000+151000] right after starting 'dolphin camera:/', and then when I try to navigate, several segfault lines. Importing pictures through digikam works.
I have a similar behavior with my Canon EOS 40D. The funny thing is that the PTP-access via dolphin worked flawlessly with a previous KDE version (4.2.x as far as I can recall), but not anymore since 4.3.x (up to 4.4.4). Here's a scenario I just tried out and wrote down: * plug in the camera to an USB port * turn on the camera - dmesg shows: [ 4855.496020] usb 1-1: new high speed USB device using ehci_hcd and address 5 [ 4855.629873] usb 1-1: New USB device found, idVendor=04a9, idProduct=3146 [ 4855.629883] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4855.629888] usb 1-1: Product: Canon Digital Camera [ 4855.629892] usb 1-1: Manufacturer: Canon Inc. [ 4855.630622] usb 1-1: configuration #1 chosen from 1 choice * open dolphin, click on "Camera" in the "Places" bar => dolphin shows: Canon EOS 40D (PTP mode) USB PTP Class Camera * Click on "Canon EOS 40D (PTP mode)" => Initializing camera (some seconds) => directory "store_00010001" is shown * Click on directory "store_00010001" => Immediate status bar message: Could not read file Could not lock the device. * press F5 => Initializing camera + Camera LED is flashing (for some seconds) => directory "DCIM" is shown * Click on directory "DCIM" => Initializing camera (some seconds, Camera LED is NOT flashing here anymore) => Could not read file Could not lock the device. * press F5 => Loading camera drivers from... => Could not read file Could not lock the device. * press F5 => Initializing Camera (some seconds) => directory "100CANON" is shown * Click on directory "100CANON" => dolphin shows all pictures * select and copy some pictures to a second dolphin window => it's working, but it needs about 15-20 seconds per picture (which is quite unusable when transferring hundreds of pictures...) This scenario is also my "best case", since the file transfer actually works (although is very slow). In other scenarios I get the "Could not lock the device" message during file transfer. When clicking on Auto Skip, the final behavior then is that only every second file gets transferred (which is quite unusable too). In other scenarios I alternatively get an "Unknown error code 150" error, in others I don't even get a single file transferred. The same behavior occurs, when selecting "USB PTP Class Camera" instead of "Canon EOS 40D (PTP mode)" at the very beginning. As "workaround" I'm using "gphoto2 -P" most times, which just works flawlessly. Some information about my system: - Debian sid, kernel = 2.6.32-5-686 - KDE package versions: 4:4.4.4-1 - gphoto2: 2.4.5-2 Feel free to contact me in case you need more information or have an idea I can/shall try out... Thanks!
> Some information about my system: > - Debian sid, kernel = 2.6.32-5-686 > - KDE package versions: 4:4.4.4-1 > - gphoto2: 2.4.5-2 Update: Some time ago, I replaced my old machine with a new one, now running the amd64 flavor of a current Debian sid. The good news is that copying images from my 40D works perfectly now. :-) - Debian sid, kernel = 3.0.0-1-amd64 - KDE package versions: 4:4.6.5 - gphoto2: 2.4.11
Bernhard: Thanks for the update (and sorry nobody responded in the last 7 years). Great to hear it works now for you, however it does not sound to me like it was the same issue the bug was originally about (the segfault in particular). Daniel: Could you test whether this still is an issue for you with a recent version? (With a another device it is working fine for me as of kamera v18.07.90 and libmtp 1.1.14, so if this is still an issue it's likely hardware specific.)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!