Menu
▾
▴
wsjt-devel — WSJT software development
You can subscribe to this list here.
| 2007 |
Jan
(30) |
Feb
|
Mar
(10) |
Apr
(60) |
May
(62) |
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(10) |
Oct
(17) |
Nov
(1) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
|
Feb
(21) |
Mar
(4) |
Apr
(15) |
May
(37) |
Jun
(98) |
Jul
(120) |
Aug
(1) |
Sep
(14) |
Oct
|
Nov
(31) |
Dec
(8) |
| 2009 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(25) |
May
(88) |
Jun
(5) |
Jul
(31) |
Aug
(25) |
Sep
(4) |
Oct
(19) |
Nov
(119) |
Dec
(11) |
| 2010 |
Jan
(3) |
Feb
(19) |
Mar
(4) |
Apr
|
May
(7) |
Jun
(17) |
Jul
|
Aug
(4) |
Sep
(20) |
Oct
(3) |
Nov
(29) |
Dec
(86) |
| 2011 |
Jan
(6) |
Feb
|
Mar
(6) |
Apr
(8) |
May
(1) |
Jun
(12) |
Jul
(9) |
Aug
(4) |
Sep
(7) |
Oct
(9) |
Nov
|
Dec
(1) |
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
(5) |
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(10) |
Feb
(7) |
Mar
(4) |
Apr
(76) |
May
(66) |
Jun
(101) |
Jul
(210) |
Aug
(255) |
Sep
(83) |
Oct
(18) |
Nov
(3) |
Dec
(3) |
| 2014 |
Jan
(187) |
Feb
(139) |
Mar
(99) |
Apr
(173) |
May
(106) |
Jun
(61) |
Jul
(50) |
Aug
(66) |
Sep
(342) |
Oct
(238) |
Nov
(251) |
Dec
(189) |
| 2015 |
Jan
(96) |
Feb
(295) |
Mar
(260) |
Apr
(271) |
May
(358) |
Jun
(531) |
Jul
(311) |
Aug
(231) |
Sep
(267) |
Oct
(219) |
Nov
(452) |
Dec
(390) |
| 2016 |
Jan
(367) |
Feb
(128) |
Mar
(208) |
Apr
(308) |
May
(237) |
Jun
(272) |
Jul
(90) |
Aug
(289) |
Sep
(153) |
Oct
(214) |
Nov
(167) |
Dec
(282) |
| 2017 |
Jan
(194) |
Feb
(173) |
Mar
(267) |
Apr
(102) |
May
(39) |
Jun
(201) |
Jul
(1064) |
Aug
(363) |
Sep
(383) |
Oct
(289) |
Nov
(237) |
Dec
(185) |
| 2018 |
Jan
(175) |
Feb
(198) |
Mar
(489) |
Apr
(222) |
May
(414) |
Jun
(297) |
Jul
(329) |
Aug
(136) |
Sep
(383) |
Oct
(590) |
Nov
(834) |
Dec
(1114) |
| 2019 |
Jan
(425) |
Feb
(177) |
Mar
(319) |
Apr
(515) |
May
(337) |
Jun
(447) |
Jul
(525) |
Aug
(252) |
Sep
(119) |
Oct
(108) |
Nov
(211) |
Dec
(228) |
| 2020 |
Jan
(158) |
Feb
(141) |
Mar
(94) |
Apr
(99) |
May
(545) |
Jun
(470) |
Jul
(211) |
Aug
(142) |
Sep
(181) |
Oct
(128) |
Nov
(219) |
Dec
(213) |
| 2021 |
Jan
(243) |
Feb
(514) |
Mar
(279) |
Apr
(101) |
May
(97) |
Jun
(259) |
Jul
(164) |
Aug
(205) |
Sep
(149) |
Oct
(301) |
Nov
(139) |
Dec
(159) |
| 2022 |
Jan
(116) |
Feb
(70) |
Mar
(63) |
Apr
(46) |
May
(50) |
Jun
(114) |
Jul
(173) |
Aug
(106) |
Sep
(127) |
Oct
(65) |
Nov
(117) |
Dec
(102) |
| 2023 |
Jan
(139) |
Feb
(99) |
Mar
(52) |
Apr
(132) |
May
(238) |
Jun
(75) |
Jul
(91) |
Aug
(25) |
Sep
(36) |
Oct
(64) |
Nov
(45) |
Dec
(91) |
| 2024 |
Jan
(156) |
Feb
(56) |
Mar
(30) |
Apr
(16) |
May
(40) |
Jun
(53) |
Jul
(327) |
Aug
(171) |
Sep
(67) |
Oct
(53) |
Nov
(43) |
Dec
(78) |
| 2025 |
Jan
(112) |
Feb
(27) |
Mar
(46) |
Apr
(49) |
May
(58) |
Jun
(54) |
Jul
(42) |
Aug
(11) |
Sep
(92) |
Oct
(45) |
Nov
(33) |
Dec
(2) |
|
From: <aa...@ma...> - 2025-10-06 09:39:52
|
Map Grid locator to U.S. State is ALSO checked. It was checked by default. And, no, it did not get me going. It still does not work. I even tried unchecking it, closing preferences, re-opening and checking it. No change. > On Oct 5, 2025, at 3:16 PM, George Molnar <ge...@mo...> wrote: > > Try also checking the box to map grids to states, that should get you going. > > > George J Molnar, KF2T > >> On Oct 5, 2025, at 3:10 PM, aa4lr--- via wsjt-devel <wsj...@li...> wrote: >> >> Installed WSJT-X v3.0.0-rc1 250915 build on a Mac. Machine is an Intel-based 13” MacBook Air 2017 running macOS Monterray 12.7.6. >> >> I enabled the General setting Show U.S. States in messages with grid, but the decodes do not change. There are not states being listed in the decode window for any of the US stations that are displaying a grid. >> >> Show distance in messages with grid, in contrast, appears to be working fine, and those messages appear and disappear when the checkbox is enabled, disabled, respectively. >> >> Steps to repeat: >> >> 1. Run WSJT-X >> 2. In Preferences, General tab, turn the Show U.S. States in messages with grid on, by clicking the checkbox. >> 3. Decode messages from USA stations that supply a grid. >> 4. Note that the decode window does not show any State(s) information after the decode >> 5. In Preferences, General tab, turn the Show distance in messages with grid on, by clicking the checkbox. >> 6. Note that the distance is displayed on those messages that supply a grid >> 7. Quitting and restarting WSJT-X has no effect on this setting >> >> >> Bill Coleman, AA4LR, PP-ASEL Mail: aa...@ma... >> Quote: "Boot, you transistorized tormentor! Boot!" >> -- Archibald Asparagus, VeggieTales >> >> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsj...@li... >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel Bill Coleman, AA4LR, PP-ASEL Mail: aa...@ma... Quote: "Boot, you transistorized tormentor! Boot!" -- Archibald Asparagus, VeggieTales |
|
From: Reino T. <rei...@ko...> - 2025-10-06 09:16:04
|
Hi, You may have followed this discussion on WSJTX group. The problem in short is that sometimes the first transmission of a message chain activates the PTT, but there is no audio signal. Hopefully my conclusions are correct and this helps a bit to study the problem. 73, Reino OH3mA -----Original Message----- From: Reino Talarmo <rei...@ko...> Sent: Monday, October 6, 2025 12:08 PM To: 'ma...@WS...' <ma...@WS...> Subject: [WSJTX] WSJT-X 3.0.0 rc1 comments and #IssueReport - missing first Tx Hi, many thanks to all answering my questions. I try to make a summary of the observations about the missing first Tx mystery. I appended the subject to help identify easily any further discussion. 1. This is not a new issue in v3.0.0-rc1 but been there at least since v.2.7.0. 2. It is operating system or version independent, seen in Windows 10 and 11, MacOS and Linux including Raspberry Pi. 3. There seems to be no pattern, when it hits. A faint indication is that a high processor load may affect. 4. RFI as a general reason is ruled out, would have been too simple, hi! 5. The missing transmission can be evoked by hitting the Tune button and it continues normally to the end of the timeslot. 6. After the missing Tx period the next one happens at random interval, typically after a long time. 7. Nobody has reported whether this happens also, when VOX is used for PTT, resulting a total missing first transmission. I assume that there is no relation to the various power saving methods used in operating system. Unless also Raspberry Pi has a power saving mode? It may be a resource management issue in some common operation system independent entity, QT as one possibility. Next step is to allocate more resources to study it would be the normal scientific entity wish I assume. May I ask some questions as I am basically a hardware man (discrete components and soldering iron) and programming is another field of expertise. Would it be possible to add into the wsjt-x another bug detection entity? Does wsjt-x have any knowledge about the audio connection state or audio output level? Hopefully my observations are correct. Any further reports are welcomed. 73, Reino OH3mA |
|
From: George M. <ge...@mo...> - 2025-10-05 20:32:37
|
Try also checking the box to map grids to states, that should get you going. George J Molnar, KF2T > On Oct 5, 2025, at 3:10 PM, aa4lr--- via wsjt-devel <wsj...@li...> wrote: > > Installed WSJT-X v3.0.0-rc1 250915 build on a Mac. Machine is an Intel-based 13” MacBook Air 2017 running macOS Monterray 12.7.6. > > I enabled the General setting Show U.S. States in messages with grid, but the decodes do not change. There are not states being listed in the decode window for any of the US stations that are displaying a grid. > > Show distance in messages with grid, in contrast, appears to be working fine, and those messages appear and disappear when the checkbox is enabled, disabled, respectively. > > Steps to repeat: > > 1. Run WSJT-X > 2. In Preferences, General tab, turn the Show U.S. States in messages with grid on, by clicking the checkbox. > 3. Decode messages from USA stations that supply a grid. > 4. Note that the decode window does not show any State(s) information after the decode > 5. In Preferences, General tab, turn the Show distance in messages with grid on, by clicking the checkbox. > 6. Note that the distance is displayed on those messages that supply a grid > 7. Quitting and restarting WSJT-X has no effect on this setting > > > Bill Coleman, AA4LR, PP-ASEL Mail: aa...@ma... > Quote: "Boot, you transistorized tormentor! Boot!" > -- Archibald Asparagus, VeggieTales > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: <aa...@ma...> - 2025-10-05 19:05:30
|
Installed WSJT-X v3.0.0-rc1 250915 build on a Mac. Machine is an Intel-based 13” MacBook Air 2017 running macOS Monterray 12.7.6.
I enabled the General setting Show U.S. States in messages with grid, but the decodes do not change. There are not states being listed in the decode window for any of the US stations that are displaying a grid.
Show distance in messages with grid, in contrast, appears to be working fine, and those messages appear and disappear when the checkbox is enabled, disabled, respectively.
Steps to repeat:
1. Run WSJT-X
2. In Preferences, General tab, turn the Show U.S. States in messages with grid on, by clicking the checkbox.
3. Decode messages from USA stations that supply a grid.
4. Note that the decode window does not show any State(s) information after the decode
5. In Preferences, General tab, turn the Show distance in messages with grid on, by clicking the checkbox.
6. Note that the distance is displayed on those messages that supply a grid
7. Quitting and restarting WSJT-X has no effect on this setting
Bill Coleman, AA4LR, PP-ASEL Mail: aa...@ma...
Quote: "Boot, you transistorized tormentor! Boot!"
-- Archibald Asparagus, VeggieTales
|
|
From: Christopher S. <cjs...@gm...> - 2025-10-01 03:04:05
|
It appears that WSJT-X v3.0.0-rc1 250915 is not flagging stations recently worked? Running on Windows 11, 24H2, 26100.6725. Per this screen shot, you can see that I worked NP3DM at 225800, and at 230545, he was heard again, but there was no color change to indicate that I had worked him recently. I'm using the Improved WSJT-X color scheme. I've included two screen shots, showing the WSJT-X version, and a screen shot showing the problem. Thank you, Chris Shaker, KJ7BLE [image: About WSJT-X.png][image: NP3DM_not_flagged_already_worked.png] |
|
From: Marco C. <PY...@ou...> - 2025-09-30 11:01:21
|
Charlie, Thanks for the update, I will follow your suggestion. 73 de PY1ZRJ Marco Inviato da Outlook per Android<https://aka.ms/AAb9ysg> ________________________________ From: Charles Suckling <g3...@gm...> Sent: Tuesday, September 30, 2025 2:00:16 AM To: PY...@ou... <PY...@ou...>; WSJT software development <wsj...@li...> Subject: Re: [wsjt-devel] Hamlib new version fails on YAESU FT-100 VFO handling Hi Marko If you want to be sure that the Hamlib developers are informed, it may be best to contact them directly. Contact information for them is given in WSJT-X's Help menu 'How to deal with rig control errors' 73 Charlie DL3WDG On Mon, 29 Sept 2025 at 23:17, Marco Calistri via wsjt-devel <wsj...@li...<mailto:wsj...@li...>> wrote: Hello, Hope someone of the Hamlib group being sneaking here. So far my rigctld command to drive my YAESU FT-100 CAT port has worked flawlessly: /usr/local/bin/rigctld -m 1021 -r /dev/FT-100_USB1 -t 4532 -s 4800 --vfo & This by using older Hamlib version: rigctld --version: rigctld Hamlib 4.6~git 2023-07-20T21:59:57Z SHA=aacf06 64-bit Now, using the new Hamlib version: rigctld --version: rigctld Hamlib 4.7~git 2025-09-27T16:16:32Z SHA=0d122f6b1 64-bit One of the VFO stays on previous frequency when I switch band. For example: I start working on 10 meters band then VFOA tunes on 28.074 and VFOB tunes on the same frequency minus or plus the audio shift. When I switch band, for example to 17 meters, VFOA sets on 18.100, whereas VFOB stays on 28.074! This is a really annoying behavior! I tried also without adding the --vfo parameter at rigctld without success and obtaining a worst and slower switching from TX to RX. Thanks for any inputs you could provide. Marco, PY1ZRJ --- 73 de Marco, PY1ZRJ (former IK5BCU) [cid:ii_19998fae1c919f93fe71] _______________________________________________ wsjt-devel mailing list wsj...@li...<mailto:wsj...@li...> https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Charles S. <g3...@gm...> - 2025-09-30 05:00:47
|
Hi Marko If you want to be sure that the Hamlib developers are informed, it may be best to contact them directly. Contact information for them is given in WSJT-X's Help menu 'How to deal with rig control errors' 73 Charlie DL3WDG On Mon, 29 Sept 2025 at 23:17, Marco Calistri via wsjt-devel < wsj...@li...> wrote: > Hello, > > Hope someone of the Hamlib group being sneaking here. > > So far my rigctld command to drive my YAESU FT-100 CAT port has worked > flawlessly: > > /usr/local/bin/rigctld -m 1021 -r /dev/FT-100_USB1 -t 4532 -s 4800 *--vfo* > & > > This by using older Hamlib version: > rigctld --version: rigctld Hamlib 4.6~git 2023-07-20T21:59:57Z SHA=aacf06 > 64-bit > > Now, using the new Hamlib version: > > rigctld --version: rigctld Hamlib 4.7~git 2025-09-27T16:16:32Z > SHA=0d122f6b1 64-bit > > One of the VFO stays on previous frequency when I switch band. > > For example: I start working on 10 meters band then VFOA tunes on 28.074 > and VFOB tunes on the same frequency minus or plus the audio shift. > > When I switch band, for example to 17 meters, VFOA sets on 18.100, whereas > VFOB stays on 28.074! > > This is a really annoying behavior! > > I tried also without adding the *--vfo* parameter at rigctld without > success and obtaining a worst and slower switching from TX to RX. > > Thanks for any inputs you could provide. > > Marco, PY1ZRJ > --- > > *73 de Marco, PY1ZRJ (former IK5BCU) * > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Marco C. <PY...@ou...> - 2025-09-29 21:14:02
|
Hello, Hope someone of the Hamlib group being sneaking here. So far my rigctld command to drive my YAESU FT-100 CAT port has worked flawlessly: /usr/local/bin/rigctld -m 1021 -r /dev/FT-100_USB1 -t 4532 -s 4800 *--vfo* & This by using older Hamlib version: rigctld --version: rigctld Hamlib 4.6~git 2023-07-20T21:59:57Z SHA=aacf06 64-bit Now, using the new Hamlib version: rigctld --version: rigctld Hamlib 4.7~git 2025-09-27T16:16:32Z SHA=0d122f6b1 64-bit One of the VFO stays on previous frequency when I switch band. For example: I start working on 10 meters band then VFOA tunes on 28.074 and VFOB tunes on the same frequency minus or plus the audio shift. When I switch band, for example to 17 meters, VFOA sets on 18.100, whereas VFOB stays on 28.074! This is a really annoying behavior! I tried also without adding the *--vfo* parameter at rigctld without success and obtaining a worst and slower switching from TX to RX. Thanks for any inputs you could provide. Marco, PY1ZRJ --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
|
From: Thomas L. <to...@dl...> - 2025-09-29 19:04:56
|
Hi, I want to report two minor graphical issues: The Dark theme does not change with the system style automatically. When a horizontal scrollbar in the 'Band activity' or 'RX Frequency' tables is visible, it covers the bottom table row. 73 de Tom, DL2RUM |
|
From: Reino T. <rei...@ko...> - 2025-09-29 15:22:01
|
Hi Tony, You may want to install latest release candidate v3.0.0-rc1 and see whether that behavior is still there. The development team may not be interested in going back in bug hunting for v2.7.0. If it is in the v3.0.0-rc1, then could you describe exact keystrokes to repeat it. 73, Reino OH3mA |
|
From: Tony S. <ton...@ih...> - 2025-09-29 14:29:17
|
Reporting bug, After completing QSO and sending 73, application always sends CQ. Disable Tx after sending 73 check box is ticked in Settings. Tried deleting wsjt-x.ini and re-start app, same result. Running v2.7.0 on Win 7 32bit King Regards, Tony Salvemini -- This email has been checked for viruses by Avast antivirus software. www.avast.com |
|
From: Christoph B. <my...@de...> - 2025-09-24 14:31:15
|
Re: Doug Breault, Sr. > Thanks. If I wait until the improved version is available, will I then not > have to delete anything from my 2.7.0 wsjt-x? I'd like to keep 2.7.0 > working and untouched if possible. I need daily FT8 sustenance to stay > alive. The "wsjtx" and "wsjtx-improved" packages conflict with each other because they install things into the same place. You can reinstall either after uninstalling the other, though. Your config/logs/other data in your home directory will stay untouched. 73, Christoph DF7CB |
|
From: Marco C. <PY...@ou...> - 2025-09-24 13:54:31
|
Hello, Noticed this on my Linux Opensuse Tumbleweed and would like to report that when starting WSJTX 3.0 as always I did so far with older versions, by adding "--style Fusion" as QT style definition of the window style, the submenu windows of settings are not resizeable, they stay always at their full size, difficulting to click on the buttons at the right bottom end, which are hidden by the desktop task bar. TNX, PY1ZRJ, Marco Inviato da Outlook per Android<https://aka.ms/AAb9ysg> |
|
From: Doug B. Sr. <dou...@gm...> - 2025-09-24 13:42:51
|
Thanks. If I wait until the improved version is available, will I then not have to delete anything from my 2.7.0 wsjt-x? I'd like to keep 2.7.0 working and untouched if possible. I need daily FT8 sustenance to stay alive. On Wed, Sep 24, 2025 at 7:12 AM Christoph Berg via wsjt-devel < wsj...@li...> wrote: > > > Preparing to unpack .../wsjtx_3.0.0_improved_PLUS_250924_amd64.deb ... > > > Unpacking wsjtx (3.0.0) ... > > > dpkg: error processing archive > > > /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb > > > (--install): > > > trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also > > > in package wsjtx-data 2.7.0~rc3+repack-1build2 > > You are mixing packages from different sources (upstream packaging for > improved, Debian/Ubuntu packaging for 2.7.0). These have not been > designed to work together, so you will have to remove the other one > before installation. > > I haven't yet had the time to upload the new improved version to > Debian, will do that soonish. > > Christoph > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Christoph B. <my...@de...> - 2025-09-24 11:08:58
|
> > Preparing to unpack .../wsjtx_3.0.0_improved_PLUS_250924_amd64.deb ... > > Unpacking wsjtx (3.0.0) ... > > dpkg: error processing archive > > /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb > > (--install): > > trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also > > in package wsjtx-data 2.7.0~rc3+repack-1build2 You are mixing packages from different sources (upstream packaging for improved, Debian/Ubuntu packaging for 2.7.0). These have not been designed to work together, so you will have to remove the other one before installation. I haven't yet had the time to upload the new improved version to Debian, will do that soonish. Christoph |
|
From: Adrian <vk...@gm...> - 2025-09-24 10:28:34
|
Copy > backup your logs to a another folder, then run ; sudo apt purge wsjtx try install again and restore logs. 73 vk4tux On 24/9/25 19:45, Doug Breault, Sr. via wsjt-devel wrote: > Hi All, > > Getting an error trying to install 3.0 on Mint > > (Reading database ... > (Reading database ... 5%% > (Reading database ... 10%% > (Reading database ... 15%% > (Reading database ... 20%% > (Reading database ... 25%% > (Reading database ... 30%% > (Reading database ... 35%% > (Reading database ... 40%% > (Reading database ... 45%% > (Reading database ... 50%% > (Reading database ... 55%% > (Reading database ... 60%% > (Reading database ... 65%% > (Reading database ... 70%% > (Reading database ... 75%% > (Reading database ... 80%% > (Reading database ... 85%% > (Reading database ... 90%% > (Reading database ... 95%% > (Reading database ... 100%% > (Reading database ... 662932 files and directories currently installed.) > Preparing to unpack .../wsjtx_3.0.0_improved_PLUS_250924_amd64.deb ... > Unpacking wsjtx (3.0.0) ... > dpkg: error processing archive > /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb > (--install): > trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is > also in package wsjtx-data 2.7.0~rc3+repack-1build2 > dpkg-deb (subprocess): decompressing archive > '/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb' > (size=27241192) member 'data.tar': internal gzip write error: Broken pipe > dpkg-deb: error: <decompress> subprocess returned error exit status 2 > dpkg-deb (subprocess): cannot copy archive member from > '/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb' to > decompressor pipe: failed to write (Broken pipe) > Processing triggers for mailcap (3.70+nmu1ubuntu1) ... > Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ... > Processing triggers for mate-menus (1.26.1+mint1) ... > Processing triggers for desktop-file-utils (0.27-2build1) ... > Processing triggers for man-db (2.12.0-4build2) ... > Errors were encountered while processing: > /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb > > uname -a > Linux Squatch 6.8.0-79-generic #79-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug > 12 14:42:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux > > lsb_release -a > No LSB modules are available. > Distributor ID: Linuxmint > Description: Linux Mint 22 > Release: 22 > Codename: wilma > > TNX > KC1UUH Doug > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Doug B. <kv...@gm...> - 2025-09-24 09:59:41
|
I have the same error on Linux Mint 22.2 codename Zara Dougl KV4ZY On Wed, Sep 24, 2025, 5:51 AM Doug Breault, Sr. via wsjt-devel < wsj...@li...> wrote: > Hi All, > > Getting an error trying to install 3.0 on Mint > > (Reading database ... > (Reading database ... 5%% > (Reading database ... 10%% > (Reading database ... 15%% > (Reading database ... 20%% > (Reading database ... 25%% > (Reading database ... 30%% > (Reading database ... 35%% > (Reading database ... 40%% > (Reading database ... 45%% > (Reading database ... 50%% > (Reading database ... 55%% > (Reading database ... 60%% > (Reading database ... 65%% > (Reading database ... 70%% > (Reading database ... 75%% > (Reading database ... 80%% > (Reading database ... 85%% > (Reading database ... 90%% > (Reading database ... 95%% > (Reading database ... 100%% > (Reading database ... 662932 files and directories currently installed.) > Preparing to unpack .../wsjtx_3.0.0_improved_PLUS_250924_amd64.deb ... > Unpacking wsjtx (3.0.0) ... > dpkg: error processing archive > /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb (--install): > trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also in > package wsjtx-data 2.7.0~rc3+repack-1build2 > dpkg-deb (subprocess): decompressing archive > '/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb' > (size=27241192) member 'data.tar': internal gzip write error: Broken pipe > dpkg-deb: error: <decompress> subprocess returned error exit status 2 > dpkg-deb (subprocess): cannot copy archive member from > '/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb' to > decompressor pipe: failed to write (Broken pipe) > Processing triggers for mailcap (3.70+nmu1ubuntu1) ... > Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ... > Processing triggers for mate-menus (1.26.1+mint1) ... > Processing triggers for desktop-file-utils (0.27-2build1) ... > Processing triggers for man-db (2.12.0-4build2) ... > Errors were encountered while processing: > /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb > > uname -a > Linux Squatch 6.8.0-79-generic #79-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 12 > 14:42:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux > > lsb_release -a > No LSB modules are available. > Distributor ID: Linuxmint > Description: Linux Mint 22 > Release: 22 > Codename: wilma > > TNX > KC1UUH Doug > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > |
|
From: Doug B. Sr. <dou...@gm...> - 2025-09-24 09:46:07
|
Hi All, Getting an error trying to install 3.0 on Mint (Reading database ... (Reading database ... 5%% (Reading database ... 10%% (Reading database ... 15%% (Reading database ... 20%% (Reading database ... 25%% (Reading database ... 30%% (Reading database ... 35%% (Reading database ... 40%% (Reading database ... 45%% (Reading database ... 50%% (Reading database ... 55%% (Reading database ... 60%% (Reading database ... 65%% (Reading database ... 70%% (Reading database ... 75%% (Reading database ... 80%% (Reading database ... 85%% (Reading database ... 90%% (Reading database ... 95%% (Reading database ... 100%% (Reading database ... 662932 files and directories currently installed.) Preparing to unpack .../wsjtx_3.0.0_improved_PLUS_250924_amd64.deb ... Unpacking wsjtx (3.0.0) ... dpkg: error processing archive /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb (--install): trying to overwrite '/usr/share/pixmaps/wsjtx_icon.png', which is also in package wsjtx-data 2.7.0~rc3+repack-1build2 dpkg-deb (subprocess): decompressing archive '/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb' (size=27241192) member 'data.tar': internal gzip write error: Broken pipe dpkg-deb: error: <decompress> subprocess returned error exit status 2 dpkg-deb (subprocess): cannot copy archive member from '/home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb' to decompressor pipe: failed to write (Broken pipe) Processing triggers for mailcap (3.70+nmu1ubuntu1) ... Processing triggers for gnome-menus (3.36.0-1.1ubuntu3) ... Processing triggers for mate-menus (1.26.1+mint1) ... Processing triggers for desktop-file-utils (0.27-2build1) ... Processing triggers for man-db (2.12.0-4build2) ... Errors were encountered while processing: /home/doug/Downloads/wsjtx_3.0.0_improved_PLUS_250924_amd64.deb uname -a Linux Squatch 6.8.0-79-generic #79-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 12 14:42:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Linuxmint Description: Linux Mint 22 Release: 22 Codename: wilma TNX KC1UUH Doug |
|
From: <n3...@ea...> - 2025-09-23 15:36:53
|
Hello all, I'm new to this group list so I apologize if my following request is misplaced or not proper. I use my own logging software (Win-EQF) and it interfaces nicely with WSJT-X in realtime, so my request is related to that end. It would be helpful if the WSJT-X.ini could be updated when BAND or MODE is changed. The existing [COMMON] parameters, DialFreq and Mode, if refreshed when the program changes band or mode, would be useful. Thank you in advance for any consideration. 73, Tom N3EQF |
|
From: Glenn W. <af...@al...> - 2025-09-23 12:51:29
|
Further testing indicated that operation of 3.0.0-rc1 started with a 30 second timeout (Settings->General->Behavior) used in months-old prior operation of 2.7.0-ga. The 6 second value for SuperHound is apparently a SH default that overrides the display only when the time has decremented to 2 minutes or below. A video is available. --Glenn, AF8C -- This email has been checked for viruses by Avast antivirus software. www.avast.com |
|
From: DG2YCB <DG...@gm...> - 2025-09-22 16:20:50
|
Hi Erik, So far, HighDPI scaling has only been implemented in the wsjtx main program, not yet in QMAP. 73 de DG2YCB, Uwe _________________________________________ German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: DG...@gm... Info: www.qrz.com/db/DG2YCB Am 22. September 2025 17:27:00 schrieb Erik Icket via wsjt-devel <wsj...@li...>: > Dear developers, > > In QMAP version "v0.5 250915 improved PLUS" the scaling of the frequency, > date & time and Astro data fields is not done correctly when System -> > Display -> Scale is set to 150%. > Setting the scaling to 100% and all fields and widgets are correctly > displayed. > > Also the version should probably read ... 250925 > > This is a MINOR problem and happens on W11. > > Regards, > Erik > ON4PB > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: Erik I. <run...@gm...> - 2025-09-22 15:26:15
|
Dear developers, In QMAP version "v0.5 250915 improved PLUS" the scaling of the frequency, date & time and Astro data fields is not done correctly when System -> Display -> Scale is set to 150%. Setting the scaling to 100% and all fields and widgets are correctly displayed. Also the version should probably read ... 250925 This is a MINOR problem and happens on W11. Regards, Erik ON4PB |
|
From: Glenn W. <af...@al...> - 2025-09-22 13:07:24
|
My ONLY message that I was sending was "E44OM AF8C EN81" with unsuccessful contacts using 3.0.0. I had a successful contact with E44OM on 10m with 2.7.0. So I was NOT criticizing SuperHound as defective, only the timer display in the right-hand corner. My point was that the watchdog timer readout should not start at 30 minutes, then in the middle suddenly decrement to 2 minutes, and have glitches (29,26) and so forth. The numbers should decrement smoothly from 5 or whatever is first, end up at 0 like it does, and without converting from "WD" to "HWD" (which I interpret to mean "Hound Watch Dog"). This leads me to worry about things like buffer sizes being wrong or pointer problems in the code. Code design should never have issues like that. Also, other than all that readout glitching, the actual watchdog timing out and stopping transmissions worked fine. Also I did not test with plain Hound or non-Hound operation. Maybe I should do that! I will let you know. --Glenn, AF8C On 9/22/2025 1:37 AM, Reino Talarmo via wsjt-devel wrote: > Hi Glenn, > > This is just educated guesswork about how the SuperHound > may work. > First, I assume that the same principle is applied to > the SuperFox as in F/H protocol: > 'Fox will respond to such "R+rpt" messages by sending > "RR73" up to three times.' > Secord, that should mean the Hound at maximum sends the > "R+rpt" only three times and automatically stop after > that. The change in the WD: may indicate an > implementation of that feature. I have no idea which > messages you were sending in your test as it may affect > to the behavior. > > 73, Reino OH3mA > > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- This email has been checked for viruses by Avast antivirus software. www.avast.com |
|
From: Erik I. <run...@gm...> - 2025-09-22 10:56:26
|
Dear developers, I observed this odd F/H behavior this morning when working FP5KE : 1. When activating Hound, the "DX Call" turns yellow and "Enable TX" turns yellow at the end of the watchdog timer, although 'Enable Wait features' are disabled. 2. The hound calls the fox for a much longer period as before. In earlier releases, the hound was calling 2-3 mins. In rel 3.0.0-rc1, the hound calls as longs as the watchdog timer is not expired. Note this is regular F/H and not Superfox mode, and "Enable Wait features" are disabled. Is this the correct behavior ? Kind regards, Erik ON4PB |
|
From: Kari S. <kai...@gm...> - 2025-09-22 10:12:44
|
Hi Glenn, This is by design. "//To keep calling Fox, Hound must reactivate Enable Tx at least once every 2 minutes" The "HWD" indicates that your timer is about to pop soon. 73's de Kari, oh2gqc On 9/22/25 01:26, Glenn Williams via wsjt-devel wrote: > Tests run after NIL results for QSO E44OM on 18095 this afternoon, > ONLY while in SuperHound mode. I have run this multiple (10?) times > into dummy load after the DX QRT'd. > > As opposed to the description in > https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-3.0.0-rc1.html > where the lower right corner display imaged as "WD:6m" > I followed the watchdog timeout sequence during SuperHound as: > > Starting transmit: > Text WD background Color "Enable TX" background Color > WD:30m White Red > > After clicking "Enable TX" (each minute two Tx transmissions) > Text WD: background Color "Enable TX" Color Transition to next # on > WD:30m White Red End of 2nd Tx > WD:29m White Red End of 2nd Tx > WD:28m White Red End of 2nd Tx > WD:27m White Red Mid of Rx after 2 Tx > HWD:2m White Red Mid of Rx after 2 Tx > (sometimes flickers to WD:26) > HWD:1m Yellow Red Mid of Rx after 2 Tx > (sometimes flickers to WD:29) > HWD:0m Red Yellow halt > > --Glenn, AF8C > > > |
68 messages has been excluded from this view by a project administrator.
