Bug #9595

Can't access Memory Properties editor: Luiton LT-580 (all bands) and Retevis RT9000D (all bands)

Added by Jim Unroe about 1 month ago. Updated about 1 month ago.

Status:Closed Start date:12/11/2021
Priority:Normal Due date:
Assignee:Jim Unroe % Done:

100%
Category:-
Target version:chirp-daily
Chirp Version:daily Platform:All
Model affected:LT-580 and others

Description

After loading any of the Luiton LT-580 or Retevis RT9000D CHIRP Radio Images (*img) file from the repository, it is not possible to bring up the Memory Properties editor. The TYT TH9000 image in the repository works as expected.

The debug.log file reports the following...

[2021-12-11 19:17:08,453] chirp.ui.memedit - INFO: Comment supported: False
Traceback (most recent call last):
  File "chirp\ui\memedit.pyo", line 754, in edit_memory
  File "chirp\ui\memdetail.pyo", line 394, in __init__
  File "chirp\ui\memdetail.pyo", line 264, in _make_ui
  File "chirp\ui\memdetail.pyo", line 36, in __init__
  File "chirp\ui\memdetail.pyo", line 101, in _init
TypeError: Gtk.Entry.set_text() argument 1 must be string without null bytes, not str
[2021-12-11 19:17:14,894] chirp.ui.mainapp - DEBUG: Closing 0

This bug affects all Vendor/Model radios that are supported by the th9000.py driver: TYT TH9000 (all bands), Luiton LT-580 (all bands) and Retevis RT9000D (all bands).

Jim KC9HI

debug.log (37.5 kB) Jim Unroe, 12/11/2021 04:33 pm

Associated revisions

Revision 3631:20122be5e3f5
Added by Jim Unroe about 1 month ago

[LT-580] Cannot open Memory Properties editor

The factory CHIRP Radio Images (*.img) files available in the CHIRP repository
for the Luiton LT-580 and Retevis RT9000S have characters in the empty memory
name (0x00) that are incompatible with Gtk causing the Memory Properties editor
to fail to display. This patch sanitizes the memory names allowing the Memory
Properties editor to open.

fixes #9595

History

#1
Updated by Jim Unroe about 1 month ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

patch submitted

Jim KC9HI

#2
Updated by Anonymous about 1 month ago

  • Status changed from Resolved to Closed

Applied in changeset 20122be5e3f5.

Also available in: Atom PDF