Bug #11538
closeduv-k5/ezgumer v0.22 won't connect (linux)
0%
Description
Chirp will not connect to the radio. Verified usb port, turned on radio, plugged in the cable, chose Download from radio from the Chirp menu. Nothing happens.
I had already installed ezgumer v0.22 on the radio (with the same cable.) I cannot locate a copy of the original factory firmware to test. Radio was newly purchased.
I belong to the dialout group, but the error log says that Chirp cannot open usbTTY0.
Files
Updated by Merton Eastman 8 months ago
- File config.txt config.txt added
- File debug_log.txt debug_log.txt added
[Uploaded from CHIRP next-20240911]
Updated by Dan Smith 8 months ago
- Status changed from New to Not a bug
You are lacking permission for your own serial port:
PermissionError: [Errno 13] Permission denied: '/dev/ttyUSB0'
You need to resolve that OS issue, which is not a CHIRP problem. I'm marking this as not a bug because that problem is not something related to CHIRP.
Also, I'm not sure why you have enabled developer mode, but I would recommend you disable it as it is adding fake serial fixtures to your list which are for developer use only.
Updated by Merton Eastman 8 months ago
You're right of course, Argh! Fixed with chmod 666. I was thrown for a loop because I was in the dialout group... guess python3 doesn't see that? Anyway, thanks for the quick response.
Updated by Dan Smith 8 months ago
No, python or chirp can't bypass security restrictions imposed by the OS -- that would kinda defeat the purpose. My guess would be that you added yourself to the dialout group after logging in, which won't affect applications started in the session from before that happened. A logout/login or reboot would end up with that having the desired effect.