Dear maintainer, with latest chirp (version 20160116) this bug does not appear any more. However, I do not know, if the fix is a bugfix in chirp directly (or a workaround) and if there is really a bug in python3-serial, or on the other hand, there is no bug in python3-serial and the bug was in chirp.
Maybe you might want to contact the maintainers of chirp to clear out things. What result you get from them, either python3-serial must be fixed, or on the other hand chirp should be updated in the repo to at least version 20160116. Thank you for reading this and all your attention. Best regards Hans-J. Ullrich
