Bug #8967
closedFile - New Not Working
100%
Description
In attempting to create a CSV file in CHIRP, the second step - after opening CHIRP - is "Go to File > New to create an empty CSV file." A New file does not appear when clicking on New. Instead of showing an empty file with grid lines and columns, it simply remains blank. No new file opens however saved image files and saved CSV files open as they should. I re-installed CHIRP twice and the problem persists.
Files
Updated by Jim Unroe about 3 years ago
- Status changed from New to Feedback
You aren't waiting long enough. Clicking "New" creates a "Generic CSV" tab with 1000 (0-999) rows with row 0 set to 146.010000 MHz. It takes several seconds to generate 1000 rows.
Jim KC9HI
Updated by John Sterner about 3 years ago
Jim Unroe wrote:
You aren't waiting long enough. Clicking "New" creates a "Generic CSV" tab with 1000 (0-999) rows with row 0 set to 146.010000 MHz. It takes several seconds to generate 1000 rows.
Jim KC9HI
Uh no. I've now waited over seven MINUTES, not seconds, and still blank.
Updated by Rudolph Gutzerhagen about 3 years ago
I see this issue first appear in change r3482 commit:9d2390ab9a62 .
At this time, I don't see what the issue is. Digging down.
Updated by Jim Unroe about 3 years ago
John Sterner wrote:
Jim Unroe wrote:
You aren't waiting long enough. Clicking "New" creates a "Generic CSV" tab with 1000 (0-999) rows with row 0 set to 146.010000 MHz. It takes several seconds to generate 1000 rows.
Jim KC9HI
Uh no. I've now waited over seven MINUTES, not seconds, and still blank.
Which version of CHIRP?
Which version of Windows?
When you install/upgrade, are previous versions of CHIRP closed?
When you install/upgrade, are you right-clicking the install file and choosing "Run as administrator"?
Jim KC9HI
Updated by Jim Unroe about 3 years ago
Also after you attempt to create a "new" file, close CHIRP and attach the debug.log file.
Updated by Rudolph Gutzerhagen about 3 years ago
Something in that identified changeset is igniting a latent bug somewhere else in the codebase.
That line in the debug log "chirp.drivers.fd268 - DEBUG: Unknowd Feidaxing radio, ID:" doesn't look right either. It smells out of place. Don't know if that is related or can help identify the problem?
Updated by John Sterner about 3 years ago
Jim Unroe wrote:
John Sterner wrote:
Jim Unroe wrote:
You aren't waiting long enough. Clicking "New" creates a "Generic CSV" tab with 1000 (0-999) rows with row 0 set to 146.010000 MHz. It takes several seconds to generate 1000 rows.
Jim KC9HI
Uh no. I've now waited over seven MINUTES, not seconds, and still blank.
Which version of CHIRP?
Which version of Windows?
When you install/upgrade, are previous versions of CHIRP closed?
When you install/upgrade, are you right-clicking the install file and choosing "Run as administrator"?Jim KC9HI
CHIRP daily-20210406
Windows 10
CHIRP does not install or upgrade unless previous versions are closed, as far as I know
Actually CHIRP worked fine in February performing this task. When I opened the program today, it said an updated version was available and I should install it asap. I did and now it fails at this task.
Updated by John Sterner about 3 years ago
Jim Unroe wrote:
Also after you attempt to create a "new" file, close CHIRP and attach the debug.log file.
Hope I did this right
Updated by Jim Unroe about 3 years ago
John Sterner wrote:
Jim Unroe wrote:
Also after you attempt to create a "new" file, close CHIRP and attach the debug.log file.
Hope I did this right
You computer is not allowing CHIRP to open the file "Untitled.csv". Try launching CHIRP by right-clicking the CHIRP shortcut and choosing "Run as administrator" to see if that makes a difference.
Jim KC9HI
Updated by Jim Unroe about 3 years ago
John Sterner wrote:
Jim Unroe wrote:
John Sterner wrote:
Jim Unroe wrote:
You aren't waiting long enough. Clicking "New" creates a "Generic CSV" tab with 1000 (0-999) rows with row 0 set to 146.010000 MHz. It takes several seconds to generate 1000 rows.
Jim KC9HI
Uh no. I've now waited over seven MINUTES, not seconds, and still blank.
Which version of CHIRP?
Which version of Windows?
When you install/upgrade, are previous versions of CHIRP closed?
When you install/upgrade, are you right-clicking the install file and choosing "Run as administrator"?Jim KC9HI
CHIRP daily-20210406
Windows 10
CHIRP does not install or upgrade unless previous versions are closed, as far as I know
Actually CHIRP worked fine in February performing this task. When I opened the program today, it said an updated version was available and I should install it asap. I did and now it fails at this task.
Nothing in CHIRP has changed that would affect this. If it had, then you could simply install the version that you were running in February to show that it works.
Did you happen to change or update your anti-virus program between then and now?
Jim KC9HI
Updated by John Sterner about 3 years ago
Jim Unroe wrote:
John Sterner wrote:
Jim Unroe wrote:
Also after you attempt to create a "new" file, close CHIRP and attach the debug.log file.
Hope I did this right
You computer is not allowing CHIRP to open the file "Untitled.csv". Try launching CHIRP by right-clicking the CHIRP shortcut and choosing "Run as administrator" to see if that makes a difference.
Jim KC9HI
Makes no difference. New continues not working.
Updated by John Sterner about 3 years ago
Jim Unroe wrote:
John Sterner wrote:
Jim Unroe wrote:
John Sterner wrote:
Jim Unroe wrote:
You aren't waiting long enough. Clicking "New" creates a "Generic CSV" tab with 1000 (0-999) rows with row 0 set to 146.010000 MHz. It takes several seconds to generate 1000 rows.
Jim KC9HI
Uh no. I've now waited over seven MINUTES, not seconds, and still blank.
Which version of CHIRP?
Which version of Windows?
When you install/upgrade, are previous versions of CHIRP closed?
When you install/upgrade, are you right-clicking the install file and choosing "Run as administrator"?Jim KC9HI
CHIRP daily-20210406
Windows 10
CHIRP does not install or upgrade unless previous versions are closed, as far as I know
Actually CHIRP worked fine in February performing this task. When I opened the program today, it said an updated version was available and I should install it asap. I did and now it fails at this task.Nothing in CHIRP has changed that would affect this. If it had, then you could simply install the version that you were running in February to show that it works.
Did you happen to change or update your anti-virus program between then and now?
Jim KC9HI
Well CHIRP daily-20210110 works as it should wrt opening a New file.
Updated by Jim Unroe about 3 years ago
Would you mind installing newer versions of CHIRP one-by-one to isolate at which version it breaks? That might offer a clue as to what has happened.
Jim KC9HI
Updated by Andrew Elert about 3 years ago
I too am having this issue.
chirp-unified-daily-20210406.app on Mac OS 11.2.3.
I too had a prompt to update to the newest version. The previous version worked fine. I have even given the application full disk access and that didn't change anything.
Updated by Andrew Elert about 3 years ago
Andrew Elert wrote:
I too am having this issue.
chirp-unified-daily-20210406.app on Mac OS 11.2.3.
I too had a prompt to update to the newest version. The previous version worked fine. I have even given the application full disk access and that didn't change anything.
The chirp-unified-daily-20210310.app version works fine for me. The latest version seems to have the bug.
Updated by Rudolph Gutzerhagen about 3 years ago
- File Generic_CSV_20210415.csv Generic_CSV_20210415.csv added
here is a copy of the csv file [ Generic_CSV_20210415.csv ] which you can use as a +workaround+ until a fix is in place.
I believe I've identified the issue in the code; question now is what to do about it.
Updated by Dan Smith about 3 years ago
- Status changed from Feedback to Closed
- % Done changed from 0 to 100
Applied in changeset commit:de4a5c7c0a9e.
Updated by Dan Smith about 3 years ago
- Status changed from Closed to Feedback
- % Done changed from 100 to 0
This has been a bug for a long time, technically forever, but practically since we moved to the metadata suffix format where we stopped using file size for model detection. Since the problem depends on the order in which models are returned from iterating the directory, the quoted recent change is not at fault, it just disturbed the ordering enough that we found something before CSVRadio in the list causing the appearance of a sudden break.
Updated by Dan Smith about 3 years ago
- Status changed from Feedback to Closed
- % Done changed from 0 to 100