Bug 5225 - Canon digital camera (gphoto) not working on 2.6.13.1 - usb error
Canon digital camera (gphoto) not working on 2.6.13.1 - usb error
Status: CLOSED PATCH_ALREADY_AVAILABLE
Product: Drivers
Classification: Unclassified
Component: USB
i386 Linux
: P2 normal
Assigned To: Greg Kroah-Hartman
:
Depends on:
Blocks: USB
  Show dependency treegraph
 
Reported: 2005-09-11 14:04 UTC by mulaz
Modified: 2005-09-12 14:17 UTC (History)
0 users

See Also:
Kernel Version: 2.6.13.1
Tree: Mainline
Regression: ---


Attachments

Description mulaz 2005-09-11 14:04:05 UTC
Most recent kernel where this bug did not occur: 2.6.12.2
Distribution: Slackware
Hardware Environment: Athlon 1800+/ Gigabyte GA7VRX motherboard / 256mb ram ddr 333
Software Environment: gphoto
Problem Description: when i try to download pictures from my digital camera
(Canon PowerShot A95) using gphoto over usb cable i get this message:
bash-3.00# gphoto2 -P
                                                                               
*** Error ***              
Could not apply USB settings

*** Error ***              
An error occurred in the io-library ('Error updating the port settings'): Could
not set config 0/1 (Device or resource busy)
*** Error (-37: 'Error updating the port settings') ***       

For debugging messages, please use the --debug option.
Debugging messages may help finding a solution to your problem.
If you intend to send any error or debug messages to the gphoto
developer mailing list <gphoto-devel@lists.sourceforge.net>, please run
gphoto2 as follows:

    env LANG=C gphoto2 --debug -P

Please make sure there is sufficient quoting around the arguments.

bash-3.00# 


Steps to reproduce:
just type gphoto -P
Comment 1 David Brownell 2005-09-11 15:29:44 UTC
I heard that this is fixed in current versions of gphoto.
If not, bug them for the fix.

(This is a dup of some other bug, fwiw.)
Comment 2 Greg Kroah-Hartman 2005-09-12 14:17:56 UTC
Yes, this is a userspace issue, just update gphoto and it should work properly.

Sorry, I don't remember the other bug number, but it is a previous one...

Note You need to log in before you can comment on or make changes to this bug.