Bug 2403115 - JS8Call suddenly stop from working after years of working very okay !
Summary: JS8Call suddenly stop from working after years of working very okay !
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: js8call
Version: 42
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Richard Shaw
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-10 16:08 UTC by yousifjkadom@yahoo.com
Modified: 2026-01-26 17:28 UTC (History)
1 user (show)

Fixed In Version: js8call-2.3.1-1.fc42 js8call-2.3.1-1.fc43
Clone Of:
Environment:
Last Closed: 2026-01-26 17:28:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Error message from version 2.3.1 (233.42 KB, image/png)
2025-10-23 12:09 UTC, yousifjkadom@yahoo.com
no flags Details

Description yousifjkadom@yahoo.com 2025-10-10 16:08:49 UTC
Hello !
 
On 4rth of current October 2025, I launched my JS8Call & confronted by the following error message from program:
 
Hamlib error: icom.c(2812):icom_get_mode_without_data returning2(-9) Command rejected by the rig
icom.c(2951):icom_get_mode returning2(-9) Command rejected by the rig
rig_get_mode: retcode after get_mode=-9
rig_get_mode(3063): freqMainA=14078000, modeMainA=, widthMainA=0
rig_get_mode(3063): freqMainB=0, modeMainB=, widthMainB=0
**2:cache.c(40):rig_set_cache_mode entered
rig_set_cache_mode(42): freqMainA=14078000, modeMainA=, widthMainA=0
rig_set_cache_mode(42): freqMainB=0, modeMainB=, widthMainB=0
rig_set_cache_mode(155): freqMainA=14078000, modeMainA=, widthMainA=0
rig_set_cache_mode(155): freqMainB=0, modeMainB=, widthMainB=0
**2:cache.c(156):rig_set_cache_mode returning(0) 
rig_get_mode(3118): freqMainA=14078000, modeMainA=, widthMainA=0
rig_get_mode(3118): freqMainB=0, modeMainB=, widthMainB=0
rig_lock: client lock disengaged
*1:rig_get_mode: elapsed=18ms
*1:rig.c(3122):rig_get_mode returning(-9) Command rejected by the rig
Command rejected by the rig
 while getting current mode
 
 
I did not changed any thing from my side at all in the setting of program ! I reviewed previous setting but I never found any thing changed ! Every thing in program setting as it ! Also, I did not change any thing in setting of my STN ICOM-7100 regarding digital modes !
 
All what I remember is that I received before weeks a new update for HAMlib !
 
My system info:
- Fedora Linux version 42 X 64 bit,
- JS8Call version 2.2.0-devel from official Fedora repositories,
- Hamlib version 4.6.5 from official Fedora repositories.
 
Any help is appreciated !


Reproducible: Always

Steps to Reproduce:
1.launch JS8Call
Actual Results:
Program will launched with error message given above which showing that it is no further detect or communicate with my RIG (ICOM7100). I can not decode nor send JS8 at all !

Expected Results:
It should launched normally without error message & detect my ICOM7100 & communicate with it & control it as before. I should be able to decode & send JS8 as before

Additional Information:
1) I'm using USB connection between my laptop & my ICOM7100 via USB version 2.0 as I'm already doing with all digital mode programs.

2) there are other digital modes programs installed on my system which are: FlDigi (Fedora official repository), FreeDV (AppImage) all are working very well & recognizing my Rig & it's card sound & have no any problem !

Comment 1 Richard Shaw 2025-10-13 12:40:38 UTC
I can't promise when it will be done but somehow I missed that the project moved to Github and has had a new release. Working on it now.

Comment 2 Fedora Update System 2025-10-14 12:07:13 UTC
FEDORA-2025-21c445f483 (js8call-2.3.1-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-21c445f483

Comment 3 Fedora Update System 2025-10-14 12:07:19 UTC
FEDORA-2025-67fbca317d (js8call-2.3.1-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-67fbca317d

Comment 4 Fedora Update System 2025-10-15 01:17:20 UTC
FEDORA-2025-67fbca317d has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-67fbca317d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-67fbca317d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2025-10-15 01:36:06 UTC
FEDORA-2025-21c445f483 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-21c445f483`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-21c445f483

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2025-10-23 01:03:31 UTC
FEDORA-2025-21c445f483 (js8call-2.3.1-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 yousifjkadom@yahoo.com 2025-10-23 12:04:08 UTC
The bug is still existing with same error message ! I tested new version 2.3.1 just some minutes ago ! The program is unable to recognize sound card of rig ! See attached screenshot.

Comment 8 yousifjkadom@yahoo.com 2025-10-23 12:09:56 UTC
Created attachment 2110608 [details]
Error message from version 2.3.1

Comment 9 yousifjkadom@yahoo.com 2025-10-23 12:14:18 UTC
I checked all parameters that should entered for program to be able to communicate with rig & all were okay ! So, why this error ? I think it is HAMlib related. But, other program like FreeDV (AppImage) & FlDigi (official Fedora repositories package) that using new version of HAMlib are working okay on my system !

Comment 10 Fedora Update System 2025-10-25 21:08:38 UTC
FEDORA-2025-67fbca317d (js8call-2.3.1-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 yousifjkadom@yahoo.com 2025-10-26 13:40:08 UTC
No ! It is not fixed ! You blocked me from test your new build because you did not push it for Fedora 42 ! You pushed it to Fedora 43 only ! My system is Fedora 42 !

For that, I removed JS8Call from my system & installed last version from author repository as AppImage & run AppImage official version & same error happened ! It seem that it is an upstream bug ! For that I opened a bug file on their official GitHub site - look for:
https://github.com/js8call/js8call/issues/93

I will re-open this issue here & you can check it & re-closed it again if you find my analyses for the problem as an up stream issue is correct.

Regards.

YI1YJK
73

Comment 12 Richard Shaw 2025-10-26 19:41:48 UTC
I was not able to reproduce the error with my Yaesu FT-991A.

Hopefully upstream will have some insights.

Comment 13 yousifjkadom@yahoo.com 2026-01-26 17:28:27 UTC
Hello ! This is not due to bug in JS8Call, but due to old frimware on my IC-7100 !

Sorry, I forgot to mention this here ! Look for this:
https://github.com/JS8Call-improved/JS8Call-improved/issues/91

My user name on GitHub is Nokia808

However, please update version of JS8Call. Now, I'm on Fedora 43 & still Fedora package out of the date ! Up to date version now is 2.5.1

The official repository of JS8Call is expired & original author more into new repository shown in above link.


Note You need to log in before you can comment on or make changes to this bug.