Bug 2008230
Summary: | wsjtx-2.5.0 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | wsjtx | Assignee: | Jaroslav Škarvada <jskarvad> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | hobbes1069, jskarvad |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | wsjtx-2.5.0-1.fc36 wsjtx-2.5.0-1.fc33 wsjtx-2.5.1-1.fc35 wsjtx-2.5.1-1.fc34 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-10-18 17:17:04 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: |
Description
Upstream Release Monitoring
2021-09-27 15:59:18 UTC
$DAYJOB has been limiting my spare cycles as of late but I have created some test packages. I'm having the no audio/RF issue with my Yaesu FT-991A so I've been hesitant to build official packages, but it may not be a problem across the board if you have time to work on it. (In reply to Richard Shaw from comment #1) > $DAYJOB has been limiting my spare cycles as of late but I have created some > test packages. I'm having the no audio/RF issue with my Yaesu FT-991A so > I've been hesitant to build official packages, but it may not be a problem > across the board if you have time to work on it. I can check with my radios, but only on f33. Isn't the problem related to the pipewire (f34 and up)? I surprisingly didn't have any issues with Fldigi or WSJT-X (at least on 2.4.0), but it could be part of the problem. (In reply to Richard Shaw from comment #3) > I surprisingly didn't have any issues with Fldigi or WSJT-X (at least on > 2.4.0), but it could be part of the problem. It works OK for me on f33. I checked only FT8. I used the following scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=77197780 (In reply to Jaroslav Škarvada from comment #4) > (In reply to Richard Shaw from comment #3) > > I surprisingly didn't have any issues with Fldigi or WSJT-X (at least on > > 2.4.0), but it could be part of the problem. > > It works OK for me on f33. I checked only FT8. I used the following scratch > build: > https://koji.fedoraproject.org/koji/taskinfo?taskID=77197780 I used it to successfully work S9OK expedition with the nearly mirror report, so for me it seems it works OK :). The only problem I spotted is that the 'auto log' feature doesn't work and I had to click the 'log QSO' button which is quite annoying. I guess this change is intentional, but I wasn't able to find anything related in the changelog. I am tempted to patch it out :) Are you going to do more testing? Or can I build it and push it to the testing? Unfortunately, I am currently unable to test it with the PipeWire, but hopefully I will be able to do it soon :). I'm using hamlib with the flrig "rig". I built test packages in a new COPR and now when I try 2.4.0 or 2.5.0 I only get rapid relay clicking when using the "tune" button in WSJT-X and it randomly loses connection to hamlib. I don't think it's an audio issue since I can turn the output all the way down and it does the same thing. Also, Fldigi works perfectly. It looks like it's hamlib<-->flrig that's broke. I setup my FT-991A directly in WJST-X and it appears to work fine so far. So I think it's safe to build everything, BUT... With the f35 beta freeze going on I wonder if we should? I'm also working on updating hamlib to the latest version. I was going to coordinate the update of 2.5.0 at the same time. Per the feedback from the devel mailing list looks like it's OK to build. Do you want me to take care of it while I'm updating hamlib? (In reply to Richard Shaw from comment #9) > Per the feedback from the devel mailing list looks like it's OK to build. Do > you want me to take care of it while I'm updating hamlib? OK, no problem I will update it (wsjtx). Are you experiencing the problems with the old (4.2) or new hamlib (4.3.1)? For me with the Icom the CAT and the remote tuning worked without any regression. I tested both with 4.1 and 4.3.1 with the same result this time. Rapid relay clicking when trying to TX but Test PTT works fine. Switched from Flrig "radio" to my actual radio and it works fine. (In reply to Richard Shaw from comment #11) > I tested both with 4.1 and 4.3.1 with the same result this time. Rapid relay > clicking when trying to TX but Test PTT works fine. Switched from Flrig > "radio" to my actual radio and it works fine. So the problem is probably not in the hamlib. Maybe the problem is in the fldigi or in the way how wsjtx uses hamlib (if this is not reproducible with the older wsjtx)? FEDORA-2021-1d52a9badb has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-1d52a9badb FEDORA-2021-1d52a9badb has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-89b655463d has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-89b655463d FEDORA-2021-6c3f55caf8 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-6c3f55caf8 FEDORA-2021-fd0fbd4bea has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-fd0fbd4bea FEDORA-2021-6c3f55caf8 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-6c3f55caf8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6c3f55caf8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-fd0fbd4bea has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-fd0fbd4bea` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-fd0fbd4bea See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-89b655463d has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-89b655463d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-89b655463d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-62c33c5ec1 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-62c33c5ec1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-62c33c5ec1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-0b28112902 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-0b28112902` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-0b28112902 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-fd0fbd4bea has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-62c33c5ec1 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-0b28112902 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. |