| Summary: | Can't open camera folder | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | Clodoaldo <clodoaldo.pinto.neto> |
| Component: | kamera | Assignee: | Marcus Meissner <marcus> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | frank78ac, ostroffjh, rdieter |
| Priority: | NOR | ||
| Version First Reported In: | 4.9.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
gphoto2 debug output
Screen shot of the Removable Devices dialogue options |
||
|
Description
Clodoaldo
2013-02-16 13:04:52 UTC
Thanks for the bug report. Reassigning to the kamera kioslave (not sure if this is a dup of another issue which has been reported already). While it tries to open the folder this message is shown: Loading camera drivers from 'usr/lib64/libgphoto2/2.5.0'... Hmm. Does the gphoto2 commandline tool work for you? gphoto2 -L (might need to install the gphoto2 RPM) (Can you also report the USB ids for the P80, we do not know them yet ... however it should work even so via the generic USB PTP Class camera that is mentioned.) # lsusb -v -d 04b0:016c
Bus 003 Device 002: ID 04b0:016c Nikon Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x04b0 Nikon Corp.
idProduct 0x016c
bcdDevice 1.00
iManufacturer 1 NIKON
iProduct 2 NIKON DSC COOLPIX P80-PTP
iSerial 3 000030192319
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 6 Imaging
bInterfaceSubClass 1 Still Image Capture
bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470)
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 100
Device Status: 0x0001
Self Powered
$ gphoto2 -L
*** Error ***
PTP I/O error
*** Error ***
An error occurred in the io-library ('Unspecified error'): The supplied vendor or product id (0x0,0x0) is not valid.
*** Error (-1: 'Unspecified error') ***
Created attachment 77387 [details]
gphoto2 debug output
Its not doing the initial write at all. Please check if the gvfs gphoto process has already grabbed the camera. ps auxw|grep gvfs.*gphoto If present, kill the gphoto2 gvfs slave and then try again :/ With the last round of updates, libgphoto2 was one of them, the camera is not mounted but gphoto2 can list the folders: $ gphoto2 -L There is no file in folder '/'. There is no file in folder '/store_00010001'. There is no file in folder '/store_00010001/DCIM'. There is 1 file in folder '/store_00010001/DCIM/100NIKON'. #1 DSCN1898.JPG rd 2556 KB 3648x2736 image/jpeg $ ps auxw|grep gvfs.*gphoto cpn 2291 0.0 0.0 317524 4968 ? Sl 21:02 0:00 /usr/libexec/gvfs-gphoto2-volume-monitor cpn 2668 0.0 0.0 109176 908 pts/1 S+ 21:10 0:00 grep --color=auto gvfs.*gphoto When I launch the device notifier it says 'no devices available'. Indeed it does not show the pen drive also. Created attachment 77418 [details]
Screen shot of the Removable Devices dialogue options
If I disconnect the camera the pendrive is show in Device Notifiers This problem is still present. I currently have gphoto2 2.5.4, gvfs 1.20.2, and kamera 4.12.5. At base, it appears to me that gphoto2 and gvfs don't play nice together, so I don't know that it's really a KDE issue, but I haven't yet found anything definitive. Killing the gvfs io slave generally lets me do one or two more gphoto2 commands without error, but I have not succeeded in doing a gphoto -P. I've got a long debug log from gphoto2, if it would help, but it loks like after reading the first jpeg from the camera (NIKON D5000) it ends with 0.546967 x_write(2): (0x1efd2c0,0x1efd490,65536) 0.547559 gphoto2-port(2): Reading 65536=0x10000 bytes from port... 0.547579 libusb1(2): reading with timeout 20000 0.579408 libusb1(2): ret = -1 0.579586 ptp2/usbread(2): Clearing halt on IN EP and retrying once. 0.579608 gphoto2-port(2): Clear halt... 0.580710 ptp2/usb_getdata(2): request code 0x1009 getting data error 0x02ff 0.580780 context(0): PTP I/O error 0.580892 libgphoto2//usr/portage/tmpdir/portage/media-libs/libgphoto2-2.5.4-r1/work/libgphoto2-2.5.4/libgphoto2/gphoto2-filesys.c(2): Download of 'DSC_0892.JPG' from '/store_00010001/DCIM/100D5000' (type 1) failed. Reason: 'Unspecified error' 0.580918 gphoto2-camera(2): Operation failed! after which it cleans up and exits. I had given up on dealing with photos for a while, but this problem still exists. I currently have libgphoto2 2.5.7 gphoto2 2.5.6 kamera 4.14.3 gvfs 1.22.4 Today, even killing the gvfs gphoto2 slave doesn't seem to help at all, even disconnecting and reconnecting the camera. Are there any ideas for further troubleshooting? Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved. Things seem different, perhaps better, but something is still wrong.
libgphoto2 2.5.30
gphoto2 2.5.28
kamera 22.08.3
gvfs 1.50.2
Device is: Bus 001 Device 050: ID 22b8:2e84 Motorola PCS Moto G (5) Plus (android phone in PTP mode)
gphoto2 -L gives me *** Error ***
An error occurred in the io-library ('Could not claim the USB device'): Could not claim interface 0 (Device or resource busy). Make sure no other program (gvfs-gphoto2-volume-monitor) or kernel module (such as sdc2xx, stv680, spca50x) is using the device and you have read/write access to the device.
*** Error (-53: 'Could not claim the USB device') ***
I get that error even as root, and even with no gvfs tasks running. I don't see any relevant kernel modules, but can't be certain. I cannot identify any process accessing the device. Shotwell also claims the device is locked by another application, but doesn't give me any hint as to what. Gwenview also says Could not claim the USB device.
However, clicking the removable devices icon in the systray does allow me to successfully open the device in Dolphin and browse down to the photos.
I'd use lsof to see what has the device open, but I don't know what device to look at.
Any other suggestions?
|