Bug 783618

Summary: Crash when runnning garmin-sync
Product: [Fedora] Fedora Reporter: Phil Anderson <pza>
Component: pyusbAssignee: Gwyn Ciesla <gwync>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: gwync, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-14 01:51:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Phil Anderson 2012-01-21 02:31:02 UTC
When you attempt to run garmin-sync with pyusb-1.0.0-0.1.a1.fc16.noarch you get the following:
Traceback (most recent call last):
  File "/usr/bin/garmin-sync", line 26, in <module>
    exit_value = garmin_sync.run()
  File "/usr/share/garmin-sync/garminsync.py", line 391, in run
    link = garmin.USBLink()
  File "/usr/share/garmin-sync/garmin.py", line 2092, in __init__
    self.startSession()
  File "/usr/share/garmin-sync/garmin.py", line 2097, in startSession
    self.sendUSBPacket(start_packet)
  File "/usr/share/garmin-sync/garmin.py", line 2145, in sendUSBPacket
    sent = self.handle.bulkWrite(0x02, packet)
  File "/usr/lib/python2.7/site-packages/usb/legacy.py", line 148, in bulkWrite
    return self.dev.write(endpoint, buffer, self.__claimed_interface, timeout)
  File "/usr/lib/python2.7/site-packages/usb/core.py", line 601, in write
    _interop.as_array(data),
  File "/usr/lib/python2.7/site-packages/usb/_interop.py", line 134, in as_array
    return array.array('u', data)
TypeError: array item must be unicode character

I found a reference to what appears to be the same issue on the pyusb list:
http://www.mail-archive.com/pyusb-users@lists.sourceforge.net/msg00690.html

When you downgrade to pyusb-0.4.1-7, it works as expected.

Comment 1 Tim Waugh 2012-01-23 11:24:55 UTC
Is pyusb-1.0.0-0.3.a2.fc16 any better?

http://koji.fedoraproject.org/koji/buildinfo?buildID=294877

Comment 2 Phil Anderson 2012-01-29 12:54:53 UTC
Just tried pyusb-1.0.0-0.3.a2.fc16.noarch and it failed with the same error.

Comment 3 Gwyn Ciesla 2012-02-29 14:06:30 UTC
Is either libusb or libusb1 installed on your system?

Comment 4 Fedora Admin XMLRPC Client 2012-02-29 14:14:59 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Phil Anderson 2012-03-01 00:12:09 UTC
Yes, both libraries are:

$ rpm -q libusb libusb1
libusb-0.1.3-9.fc16.x86_64
libusb1-1.0.9-0.3.rc1.fc16.x86_64

Comment 6 Gwyn Ciesla 2012-03-13 14:48:09 UTC
Try this build of the latest git snapshot:

http://fedorapeople.org/~limb/pyusb/pyusb-1.0.0-0.4.git5b97bb2.fc16.noarch.rpm

Comment 7 Fedora End Of Life 2013-01-16 23:27:29 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Fedora End Of Life 2013-02-14 01:51:44 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.