Bug #10869
closedCHIRP Mac OS 12.7 does nothing when I try to open a recent file after I select it.
0%
Description
MAC Monterey OS 12.7 After installing CHIRP, it starts normally. When I try to open a recent file, nothing happens. When I try to upload from radio, nothing happens. I have removed, rebooted and reinstalled multiple times. Everything has been working fine up to this point. Radio is Baofeng UV-S9PLUS and I use the Radioddity UV-5RX3 selection. (Though I guess that would not matter for opening recent files). TIA
Files
Updated by Dan Smith over 1 year ago
Need a debug log per How_To_Report_Issues or this is not actionable.
Updated by Jeff Eglen over 1 year ago
[2023-09-26 20:32:10,252] chirp.logger - DEBUG: CHIRP next-20230924 on Darwin Jeffreys-Air.lan1 21.6.0 Darwin Kernel Version 21.6.0: Fri Sep 15 16:17:23 PDT 2023; root:xnu-8020.240.18.703.5~1/RELEASE_X86_64 x86_64 (Python 3.8.2)
[2023-09-26 20:32:10,602] chirp.wxui - DEBUG: Using locale: en_US (276)
[2023-09-26 20:32:10,608] chirp.wxui - DEBUG: Translation loaded=True for CHIRP: en_US (pl,uk_UA,en_US,pt_BR,el,it,ru,zh_CN,hu,nl,de,fr,es,tr_TR) from /Applications/CHIRP.app/Contents/MacOS/chirp/locale
[2023-09-26 20:32:10,613] chirp.wxui - DEBUG: Translation loaded=False for wxstd: en_US (fa_IR,sl,sk,pl,vi,sq,sv,ms,da,gl_ES,pt_BR,ko_KR,ja,el,lv,co,it,ca,zh_TW,cs,ru,ro,zh_CN,pt,uk,an,ar,hr,hu,nl,ne,af,nb,hi,ka,de,ca@valencia,fi,id,fr,es,lt,eu,ta,tr)
[2023-09-26 20:32:11,183] main - INFO: Python/3.8.2 // Darwin/macOS-12.7-x86_64-i386-64bit // CHIRP/next-20230924 // wx/4.2.0 osx-cocoa (phoenix) wxWidgets 3.2.0
[2023-09-26 20:32:11,536] chirp.wxui.main - INFO: Server reports next-20230924 is latest
[2023-09-26 20:32:20,565] chirp.chirp_common - DEBUG: Loaded metadata: {'mem_extra': {}, 'rclass': 'RadioddityUV5RX3Radio', 'vendor': 'Radioddity', 'model': 'UV-5RX3', 'variant': '', 'chirp_version': 'next-20230924'}
[2023-09-26 20:32:20,567] chirp.chirp_common - DEBUG: Loaded metadata: {'mem_extra': {}, 'rclass': 'RadioddityUV5RX3Radio', 'vendor': 'Radioddity', 'model': 'UV-5RX3', 'variant': '', 'chirp_version': 'next-20230924'}
[2023-09-26 20:32:20,567] chirp.chirp_common - DEBUG: Parsed version 'next-20230924' to (0,)
[2023-09-26 20:32:20,567] chirp.chirp_common - DEBUG: Parsed version 'next-20230924' to (0,)
Updated by Dan Smith over 1 year ago
I don't see any attempt to open a file from recent nor do an upload in that log. Did you reproduce the issue(s) and then capture the log? Also, please attach it as a file using the shortcut in the Help menu in the future.
Updated by Jeff Eglen over 1 year ago
- File 20230927CHIRP log.rtf 20230927CHIRP log.rtf added
I started CHIRP, did a read from radio and this is the log.
Updated by Dan Smith about 1 year ago
Okay, I think you're not understanding the instructions in How_To_Report_Issues. I need you to reproduce the problem and then capture a debug log so that any errors that get generated are captured there. Your report said that upload to the radio wasn't working and opening a file from the recent menu. I need you to do one of those things, then capture a debug log and we can go from there.
I see in the log you provided that there's an issue with using the debug log capture from the help menu on your system. I've got a fix queued for that for the next build. However, I still need the above for your actual issue.
Updated by Jeff Eglen about 1 year ago
Sorry Dan. Here is what I did:
- Closed CHIRP
- Opened CHIRP
- Connected the Radio
- Selected Download from Radio.
- The process went as expected, but CHIRP did not show the downloaded file.
- Got the log file per the instructions in the link and sent to you. Thanks,
Jeff
Updated by Dan Smith about 1 year ago
Your original report says "when I try to upload from radio" .. do you mean "download"? Meaning radio to computer?
Your log shows no errors (related to clone) so I don't even know where to start. I'm able to open your image file that you attached earlier no problem. You attempted to paste an screenshot but it seems unrelated.
Updated by Jeff Eglen about 1 year ago
It is now working. The only difference is that I used a different USB port. Thanks for your help!
Best,
Jeff