Bug 2218889

Summary: Hamlib NET rigctl connection does not work anymore
Product: [Fedora] Fedora Reporter: Daniel Rusek <drusek>
Component: wsjtxAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 38CC: hobbes1069, jskarvad, mail
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-30 13:10:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
My rigctl config none

Description Daniel Rusek 2023-06-30 12:56:04 UTC
It looks like that rig control using "Hamlib NET rigctl" recently stopped working. See the additional info for complete error message. Also see the attached screenshot for my configuration.

It does not look like a problem on the rig (Gqrx SDR software in my case) side since "nc 127.0.0.1 7356" seems to work fine and I can communicate with Gqrx, set or read frequency etc. without any problem.

Reproducible: Always

Additional info:
Hamlib error:   2:rig.c(7481):async_data_handler_start entered
async_data_handler_start: async data support disabled since async_data_enabled=0
  2:rig.c(7488):async_data_handler_start returning(0) 
rig.c(254):add_opened_rig returning2(0) 
rig_open: 0x562b105dab2c rs->comm_state==1?=1
  2:rig.c(6084):rig_get_powerstat entered
rig.c(6104) trace
netrigctl_get_powerstat called
netrigctl_transaction: called len=15
rig_flush: called for network device
network_flush called
write_block(): TX 15 bytes, method=2
0000    5c 67 65 74 5f 70 6f 77 65 72 73 74 61 74 0a        \get_powerstat. 
read_string_generic called, rxmax=1024 direct=1, expected_len=1
read_string_generic(): RX 7 characters, direct=1
0000    52 50 52 54 20 31 0a                                RPRT 1.         
  2:rig.c(6109):rig_get_powerstat returning(0) 
rig_open: rig power is off, use --set-conf=auto_power_on if power on is wanted
Rig is not powered on
Rig is not powered on
 while opening connection to rig

Comment 1 Daniel Rusek 2023-06-30 12:56:39 UTC
Created attachment 1973403 [details]
My rigctl config

Comment 2 Daniel Rusek 2023-06-30 13:10:55 UTC
Interesting, it looks like that it also happens with Flatpak version of WSJT-X. Downgrading Gqrx did not help so it is most likely a regression caused by hamlib on a Gqrx side.