[chirp_users] cannot read from com port

eric oyen eric.oyen at gmail.com
Thu Oct 3 23:22:16 PDT 2013

I managed to take care of that. I simply edited the group file to reflect that. now I can get it to read the radio, but it seems to be reading every 3rd memory location (or displaying only those).

Also, there appears to be a missing packeage  in the repositories. python-gtk is not a listed package. thats going to make it a lot more difficult to compile a daily build.


On Oct 3, 2013, at 11:01 PM, Andrew Errington wrote:

> The typical cause of this problem is that the the com port permissions
> are set by the 'dialout' group and the user is not a member of the
> 'dialout' group.  Check the permissions of the port, and the
> membership of the user.
> If the user must be added to the 'dialout' group then once you have
> done that don't forget to logout and login again as that user, or the
> new group membership won't take effect.
> It's possible that this is not your problem, but it's very common,
> easy to check, and easy to eliminate.  It would be a good place to
> start.
> Andrew
> On 4 October 2013 12:38, eric oyen <eric.oyen at gmail.com> wrote:
>> ok,
>> I have chirp installed on a ubuntu 13.04 box. Its operation appears to be a bit inconsistent. Sometimes it will run and display the program frame. other times it just sits there and is invisible to the orca screen reader.
>> the second issue is that it can't seem to obtain permissions to read from the com port (which is a prolific device on a USB dongle). I have confirmed that the device is loaded and working properly (I can set up a terminal session between 2 machines with it). However, all attempts (that are visible to me) result in the error "cannot read from device. Permission denied".
>> I have tried running it from a terminal session using sudo and it won't even become visible to my screen reader.
>> In case you are wondering, I am blind. So, I need a little help here.
>> now, I have made sure that my user is administrator on the machine, so there shouldn't be this problem. suggestions?
>> -eric
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users

More information about the chirp_users mailing list