Red Hat Bugzilla – Bug 221741
gphoto2-2.3.1-1.fc6 breaks Canon A430 communications
Last modified: 2013-07-02 19:19:09 EDT
Description of problem:
update to gphoto2-2.3.1-1.fc6.i386.rpm renders communication error with camera
Canon A430. consistent among various kernels versions. regression to
gphoto2-2.2.0-2.1.i386.rpm (original FC6 version) works perfectly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
communciation fails with updated version.
do you see something like this:
while communicating with your A430?
This issue remains in gphoto2-2.3.1-5.fc7
If I can provide more information to assist with fixing it please let me know.
The link provided in the previous request pointed to a post about junk mail, so
was not relevant.
I can confirm the original reporters comments that the previous version
gphoto2-2.2.0 worked fine. Upgrading two separate systems to Fedora 7 with
gphoto2-2.3.1 breaks communications with the Canon A430.
Camera is detected properly, but reports an I/O error when attempting to get the
list of images from the camera.
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.