Date   

Walt (KK4DF)
 
Edited

Same results after the update and dist-upgrade commands.  lib1t5core5a:arm64 (and :armhf) is installed.

pi@raspberrypi:~ $ apt list --installed | grep libqt5core5
 
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
 
libqt5core5a/stable,now 5.11.3+dfsg1-1+deb10u4 arm64 [installed,automatic]
libqt5core5a/stable,now 5.11.3+dfsg1-1+deb10u4 armhf [installed,auto-removable]
 
(gdb) run wsjtx
Starting program: /usr/bin/wsjtx wsjtx
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ff2981040 (LWP 8278)]
qt5ct: using qt5ct plugin
[New Thread 0x7ff1362040 (LWP 8303)]
[New Thread 0x7ff0919040 (LWP 8304)]
[New Thread 0x7fe10c8040 (LWP 8333)]
[New Thread 0x7fdbfff040 (LWP 8450)]
[New Thread 0x7fdb7fe040 (LWP 8578)]
[New Thread 0x7fdaffd040 (LWP 8579)]
[New Thread 0x7fda7fc040 (LWP 8588)]
[New Thread 0x7fd9ffb040 (LWP 8597)]
[New Thread 0x7fd97fa040 (LWP 8598)]
[New Thread 0x7fd8df5040 (LWP 8679)]
[Detaching after fork from child process 8680]
[New Thread 0x7fb2675040 (LWP 8705)]
[Thread 0x7fdb7fe040 (LWP 8578) exited]
 
Thread 8 "QThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fdaffd040 (LWP 8579)]
strlen () at ../sysdeps/aarch64/strlen.S:94
94 ../sysdeps/aarch64/strlen.S: No such file or directory.
(gdb) bt
#0  strlen () at ../sysdeps/aarch64/strlen.S:94
#1  0x0000007ff60413ec in __GI___strdup (s=0x0) at strdup.c:41
#2  0x0000005555872574 in ?? ()
#3  0x000000555582f0f4 in ?? ()
#4  0x00000055557b3658 in ?? ()
#5  0x0000005555827ad0 in ?? ()
#6  0x00000055558285f0 in ?? ()
#7  0x0000007ff671006c in QObject::event(QEvent*) ()
   from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#8  0x0000007ff73be3d4 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib/aarch64-linux-gnu/libQt5Widgets.so.5
#9  0x0000007ff73c5a8c in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/aarch64-linux-gnu/libQt5Widgets.so.5
#10 0x000000555571a7f0 in ?? ()
#11 0x0000007ff66e4618 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
    () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#12 0x0000007ff66e7820 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#13 0x0000007ff673bb50 in ?? () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#14 0x0000007ff3cba674 in g_main_context_dispatch ()
   from /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0
#15 0x0000007ff3cba8e8 in ?? ()
   from /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0
#16 0x0000007ff3cba984 in g_main_context_iteration ()
   from /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0
#17 0x0000007ff673b04c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#18 0x0000007ff66e2ed8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#19 0x0000007ff652b124 in QThread::exec() ()
   from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#20 0x0000007ff6536444 in ?? () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#21 0x0000007ff7aac7e4 in start_thread (arg=0x7fffffa1bf)
    at pthread_create.c:486
#22 0x0000007ff6095adc in thread_start ()
    at ../sysdeps/unix/sysv/linux/aarch64/clone.S:78
 


Bill Somerville
 

On 04/06/2021 13:13, Walt (KK4DF) wrote:
(gdb) run wsjtx
Starting program: /usr/bin/wsjtx wsjtx
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ff2981040 (LWP 11385)]
qt5ct: using qt5ct plugin
[New Thread 0x7ff1362040 (LWP 11402)]
[New Thread 0x7ff0919040 (LWP 11411)]
[New Thread 0x7fe10c8040 (LWP 11431)]
[New Thread 0x7fdbfff040 (LWP 11535)]
[New Thread 0x7fdb7fe040 (LWP 11641)]
[New Thread 0x7fdaffd040 (LWP 11642)]
[New Thread 0x7fda7fc040 (LWP 11651)]
[New Thread 0x7fd9ffb040 (LWP 11660)]
[New Thread 0x7fd97fa040 (LWP 11661)]
[New Thread 0x7fd8df5040 (LWP 11732)]
[Detaching after fork from child process 11733]
[New Thread 0x7fb2675040 (LWP 11758)]
[Thread 0x7fdb7fe040 (LWP 11641) exited]
 
Thread 8 "QThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fdaffd040 (LWP 11642)]
strlen () at ../sysdeps/aarch64/strlen.S:94
94 ../sysdeps/aarch64/strlen.S: No such file or directory.
(gdb) bt
#0  strlen () at ../sysdeps/aarch64/strlen.S:94
#1  0x0000007ff60413ec in __GI___strdup (s=0x0) at strdup.c:41
#2  0x0000005555872574 in ?? ()
#3  0x000000555582f0f4 in ?? ()
#4  0x00000055557b3658 in ?? ()
#5  0x0000005555827ad0 in ?? ()
#6  0x00000055558285f0 in ?? ()
#7  0x0000007ff671006c in QObject::event(QEvent*) ()
   from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#8  0x0000007ff73be3d4 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib/aarch64-linux-gnu/libQt5Widgets.so.5

<snipped log stack trace>

Hi Walt,

that looks like a Qt defect, is your system up to date?

sudo apt update
sudo apt dist-upgrade

to bring up tp date.

My Raspberry Pi 4 64-bit Raspberry Pi OS system has this version of the Qt packages:

pi@raspberrypi4:~ $ apt list --installed | grep libqt5core5

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libqt5core5a/stable,now 5.11.3+dfsg1-1+deb10u4 arm64 [installed,automatic]

73
Bill
G4WJS.


Walt (KK4DF)
 
Edited

(gdb) run wsjtx
Starting program: /usr/bin/wsjtx wsjtx
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ff2981040 (LWP 11385)]
qt5ct: using qt5ct plugin
[New Thread 0x7ff1362040 (LWP 11402)]
[New Thread 0x7ff0919040 (LWP 11411)]
[New Thread 0x7fe10c8040 (LWP 11431)]
[New Thread 0x7fdbfff040 (LWP 11535)]
[New Thread 0x7fdb7fe040 (LWP 11641)]
[New Thread 0x7fdaffd040 (LWP 11642)]
[New Thread 0x7fda7fc040 (LWP 11651)]
[New Thread 0x7fd9ffb040 (LWP 11660)]
[New Thread 0x7fd97fa040 (LWP 11661)]
[New Thread 0x7fd8df5040 (LWP 11732)]
[Detaching after fork from child process 11733]
[New Thread 0x7fb2675040 (LWP 11758)]
[Thread 0x7fdb7fe040 (LWP 11641) exited]
 
Thread 8 "QThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fdaffd040 (LWP 11642)]
strlen () at ../sysdeps/aarch64/strlen.S:94
94 ../sysdeps/aarch64/strlen.S: No such file or directory.
(gdb) bt
#0  strlen () at ../sysdeps/aarch64/strlen.S:94
#1  0x0000007ff60413ec in __GI___strdup (s=0x0) at strdup.c:41
#2  0x0000005555872574 in ?? ()
#3  0x000000555582f0f4 in ?? ()
#4  0x00000055557b3658 in ?? ()
#5  0x0000005555827ad0 in ?? ()
#6  0x00000055558285f0 in ?? ()
#7  0x0000007ff671006c in QObject::event(QEvent*) ()
   from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#8  0x0000007ff73be3d4 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib/aarch64-linux-gnu/libQt5Widgets.so.5
#9  0x0000007ff73c5a8c in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/aarch64-linux-gnu/libQt5Widgets.so.5
#10 0x000000555571a7f0 in ?? ()
#11 0x0000007ff66e4618 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
    () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#12 0x0000007ff66e7820 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#13 0x0000007ff673bb50 in ?? () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#14 0x0000007ff3cba674 in g_main_context_dispatch ()
   from /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0
#15 0x0000007ff3cba8e8 in ?? ()
   from /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0
#16 0x0000007ff3cba984 in g_main_context_iteration ()
   from /usr/lib/aarch64-linux-gnu/libglib-2.0.so.0
#17 0x0000007ff673b04c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#18 0x0000007ff66e2ed8 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#19 0x0000007ff652b124 in QThread::exec() ()
   from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#20 0x0000007ff6536444 in ?? () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5
#21 0x0000007ff7aac7e4 in start_thread (arg=0x7fffffa1bf)
    at pthread_create.c:486
#22 0x0000007ff6095adc in thread_start ()
    at ../sysdeps/unix/sysv/linux/aarch64/clone.S:78
(gdb) 
 


Bill Somerville
 

On 04/06/2021 13:07, Walt (KK4DF) wrote:
gdb wsjtx does not launch wsjtx for me.  Help me figure out how to launch wsjtx with this debugger.
Hi Walt,

sorry, my bad. I omitted a key piece of information, start WSJT-X within gdb by typing 'run' then hit ENTER.

73
Bill
G4WJS.


locked Re: 2.5.0 RC1 - No receive after transmit - rig control disables RX on Yaesu FTDX-3000 VFO A running split #IssueReport

Bill Somerville
 

On 04/06/2021 11:13, Mark Steele wrote:
Version: WSJT-X 2.5.0 RC1
Rig: Yaesu FTDX-3000
Mode: FT8 / FT4 tested
When transmitting using Rig Split mode, VFO-B is switched to for transmit, and the RX light for VFO begins flashing. After the TX cycle, receive is disabled until the RX button is manually pressed on the rig. If left to repeat, RX works every OTHER cycle.
Tested on various bands and modes. Switching back to version 2.4.0-rc4 and this behavior does not happen.
Went back thru the entire WSJT-X configuration and saved. Forced a sync of VFO-A settings to VFO-B - no joy.
This was first reported in 2.4.0 GA.
Please note, switching to 'fake-it' is a workaround.
Hi Mark,

this issue appears to be a strange behaviour of the FTdx3000 in response to one of its CAT commands. If "Fake-It" split mode works then I recommend using that, it is provided for exactly these sort of circumstances.

73
Bill
G4WJS.


locked 2.5.0 RC1 - No receive after transmit - rig control disables RX on Yaesu FTDX-3000 VFO A running split #IssueReport

Mark Steele
 

Version: WSJT-X 2.5.0 RC1
Rig: Yaesu FTDX-3000
Mode: FT8 / FT4 tested
 
When transmitting using Rig Split mode, VFO-B is switched to for transmit, and the RX light for VFO begins flashing. After the TX cycle, receive is disabled until the RX button is manually pressed on the rig. If left to repeat, RX works every OTHER cycle.
 
Tested on various bands and modes. Switching back to version 2.4.0-rc4 and this behavior does not happen.
 
Went back thru the entire WSJT-X configuration and saved. Forced a sync of VFO-A settings to VFO-B - no joy.
 
This was first reported in 2.4.0 GA.
 
Please note, switching to 'fake-it' is a workaround.


locked Re: WSJTX terminates on UBUNTU 20.04 #wsjt-x-crashing

Bill Somerville
 

On 04/06/2021 01:16, Ron McMurdy wrote:
Both downloaded version and compiled on computer crash after approx 20 minutes with the following error:

terminate called after throwing an instance of 'boost::wrapexcept<boost::log::v2_mt_posix::conversion_error>'
  what():  Could not convert character encoding
Aborted (core dumped)


Worked fine on Ubuntu 18.04

Thanks

Hi Ron,

please report back with the output of the following command?

locale -a | grep en_US

73
Bill
G4WJS.


locked Re: #Set up for FT8 and others

Mike G0LQI
 

Hi Alan,
I've run an IC7600 with WSJT-X for many years. If you have your rig connected to your PC for CAT, then you you are home and dry. Just run WSJT-X and set the "Radio" connection as in the attachment. Then set the "audio" as shown in the second attachment. You only need the one USB CAT cable.
73 Mike G0LQI
PS  As regards Win 7, I'll pass on that; I use Win 10.


locked Re: Probleme compile WSJT-x in JTSDK64 #wsjt-x

Bill Somerville
 

On 04/06/2021 08:30, Jean-Claude F1DSZ wrote:

Hello to all
I have a problem to compile WSjt-x with JTsdk64 ...
all my downloads are good, the setup also, but in suite, to build it does not go to the end....
What did I do wrong?
Look at my file in attachment.

Thank you for your answer Jean Claude F1DSZ

Hi Claude,

this is a matter for whoever supports the JTSDK you are using.

73
Bill
G4WJS.


locked Re: JtAlert to WSJT-X #general

Bill Somerville
 

On 04/06/2021 03:29, Joe Parisella wrote:
Where do I find the setting to enable the transfer of a station listed in JtAlert window
To the WSJT-X generate message window ?
Hi Joe,

the option is "Settings->Reporting->UDP Server->Accept UDP requests".

73
Bill
G4WJS.


locked Re: No colors when using multiple instances #raspberryPi #WSJTX_config

jaime r
 

Hello!

It worked when I copied the "WSJT-X.ini" file to "WSJT-X - 7300.ini" and "WSJT-X - 9700.ini" in the .config folder.

I was not aware of those files were existing O:-)

Thank you so much!

Jaime, EA4K

El 04/06/2021 a las 0:01, Bill Somerville escribió:
On 03/06/2021 18:17, jaime r wrote:
Hello all,
I yesterday started to use multiple (two) instances of wsjtx on my raspberry pi.
One connected to a IC7300 and another one to a IC9700.
I am starting with wsjtx --rig-name 7300 or 9700.
Well, if i start one single instance, decodes show the right colors but if I start it with the --rig-name wsjtx does not show colors, not even wrong colors, just the green one if I select CQ on green but without considering the log.
I have copied the .adi file to the WSJT-X - 7300 folder, there wsjtx shows the .adi file and clicked to rescan the adi file in the setup->color tab jut nothing happens.
Does anybody has a clue for me?
Thank you!
Jaime, EA4K

Hi Jamie,

have you checked the "Settings->General->Show DXCC, grid, and worked before status" option?

BTW, rather than copy your WSJT-X log file to each instance's log files directory, make a symlink so they all share the same file.

73
Bill
G4WJS.





locked Probleme compile WSJT-x in JTSDK64 #wsjt-x

Jean-Claude F1DSZ
 
Edited


Hello to all
I have a problem to compile WSjt-x with JTsdk64 ...
all my downloads are good, the setup also, but in suite, to build it does not go to the end....
What did I do wrong?
Look at my file in attachment.

Thank you for your answer Jean Claude F1DSZ


locked Re: #Q65 Latest Performance Results for Q65 with Settings #Q65

 

Yes Charlie, that is correct. After an EME QSO on 70cm one could literally "feel" the energy that went through the cables at 1.5kW ... they were warm. For testing the system I once transmitted 15 min at full power straight up into the sky. The rig, the transverter and the driver with a 2C39 tube stayed coool and the homemade PA was a monster with a 300 watts blower ... I never ever broke that stuff. Now using SSPAs even with good cooling is more a thing I must have an eye on.
--
---

Christoph Petermann DF9CY

JO54al (Baltic Sea Coast)
7 MHz Dipole @9,5m - 400w

50MHz 6 ele OP-DES Yagi - 270w

144MHz 9 ele DK7ZB - 330w
432MHz 23 ele - 35w

https://www.df9cy.de


locked Re: JtAlert to WSJT-X #general

neil_zampella
 

Make sure all the UDP checkboxes are checked in the WSJT-X settings.

UDP Settings

Neil, KN3ILZ

On 6/3/2021 9:29 PM, Joe Parisella wrote:
Where do I find the setting to enable the transfer of a station listed in JtAlert window
To the WSJT-X generate message window ?



locked Re: #Q65 Latest Performance Results for Q65 with Settings #Q65

Charles Suckling
 

Christoph

The technical issue with longer periods is that unlike CW,  WSJT modes are essentially 100% duty cycle while transmitting, so poorly designed rigs or PAs may overheat with the longer period modes.  Better heatsinks, bigger fans etc should be able to deal with this.  I tested my small 130W 1296 PA with up to 300s periods and it reaches thermal equilibrium after a couple of minutes, and ran cool enough.

Re time to complete a QSO, I agree with you that if longer periods will enable a difficult QSO then who cares how long it takes. I have run 300s periods with KA1GT on 1296 EME  using small antennas (eg a helix).  In these extreme cases having the longer periods available is very useful.

73

Charlie G3WDG

On Fri, 4 Jun 2021 at 06:21, Christoph Petermann DF9CY <mail01@...> wrote:
Hi Dwight
in times of CW (what was this?) we had 2,5 minutes TX periods in EME or 5 minutes in high speed CW with full power. A QSO easily lasted up to one our ... Once a 70cm meteorscatter QSO I could complete after 4 hours and I was a very happy guy. But nowadays we live in sort of a "highspeed society" ....
--
---

Christoph Petermann DF9CY

JO54al (Baltic Sea Coast)
7 MHz Dipole @9,5m - 400w

50MHz 6 ele OP-DES Yagi - 270w

144MHz 9 ele DK7ZB - 330w
432MHz 23 ele - 35w

https://www.df9cy.de





locked Re: #Q65 Latest Performance Results for Q65 with Settings #Q65

 

Hi Dwight
in times of CW (what was this?) we had 2,5 minutes TX periods in EME or 5 minutes in high speed CW with full power. A QSO easily lasted up to one our ... Once a 70cm meteorscatter QSO I could complete after 4 hours and I was a very happy guy. But nowadays we live in sort of a "highspeed society" ....
--
---

Christoph Petermann DF9CY

JO54al (Baltic Sea Coast)
7 MHz Dipole @9,5m - 400w

50MHz 6 ele OP-DES Yagi - 270w

144MHz 9 ele DK7ZB - 330w
432MHz 23 ele - 35w

https://www.df9cy.de


locked Re: Intl. WSPR Beacon Project #Beacons

Roland
 

This is the map of the current Beacon candidates https://www.google.com/maps/d/u/1/edit?mid=14X0GJ4vSQ7D8piZfuHDs902Y9tINuPqB&usp=sharing nothing finalized yet


locked JtAlert to WSJT-X #general

Joe Parisella
 

Where do I find the setting to enable the transfer of a station listed in JtAlert window
To the WSJT-X generate message window ?


locked WSJTX terminates on UBUNTU 20.04 #wsjt-x-crashing

Ron McMurdy
 

Both downloaded version and compiled on computer crash after approx 20 minutes with the following error:

terminate called after throwing an instance of 'boost::wrapexcept<boost::log::v2_mt_posix::conversion_error>'
  what():  Could not convert character encoding
Aborted (core dumped)


Worked fine on Ubuntu 18.04

Thanks


locked Re: WSJT-X and HRD and neither one will key the radio #transmit

Neil Foster
 

Jimmy
You have not indicated what version of HRD you are using. Also if you click on tune does the radio go in to TX?
It would be most helpful to know what radio you are using??
Neil   N4FN

12741 - 12760 of 38026