CHIRP

The programming cable I have connects as /dev/ttyUSB0. chirpw now (it used to work fine) fails to connect and reports that "serial" has no setTimeout attribute.

ERROR: -- Exception: --
ERROR: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/clone.py", line 238, in run
self.__radio.sync_in()
File "/usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py", line 705, in sync_in
raise errors.RadioError("Failed to communicate with radio: %s" % e)
RadioError: Failed to communicate with radio: 'Serial' object has no attribute 'setTimeout'

ERROR: ----------------
ERROR: Clone failed: Failed to communicate with radio: 'Serial' object has no attribute 'setTimeout'
ERROR: --- Exception Dialog: Failed to communicate with radio: 'Serial' object has no attribute 'setTimeout' ---
ERROR: None

ERROR: ----------------------------

If I kludge the chirp uv5r driver thusly:

sudo chmod 666 /usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py
vi /usr/lib/python2.7/dist-packages/chirp/drivers/uv5r.py

edit:

...
407
408
409 def _do_ident(radio, magic):
410 serial = radio.pipe
411 #DMK# serial.setTimeout(1)
412
413 LOG.info("Sending Magic: %s" % util.hexprint(magic))
...
`
Save and rerun chirpw. chirp now connects to the Baofeng UV-5R, etc. and can download/upload as before.

My guess: ubuntu changed the python2.7 "serial" class...

The same failure occurs on all my Ubuntu 16.04 LTS systems (which are up to date as of this morning), but chirpw on the Raspberry pies here (wheezy and jessie distros, also up to date as of thie AM)) all work fine, using the same cable (connects as /dev/ttyUSB0 on all systems).