Hello everyone, #raspberryPi #Bullseye #wsjt-x-crashing New install of WSJT-X 2.5.3 is randomly crashing between receive sequences during decode. Newly built Raspberry Pi 4 Model B Rev 1.4, 8GB Raspbian GNU/Linux 11 (bullseye) Started with wsjtx-2.5.3.tgz I've managed to get through the section "Building WSJT-X from the Self-Contained Source Tarball" I can now run WSJT-X and it communicates over USB to the ICOM IC9100 for CAT & Audio - no problems. It decodes a few times (sometimes only once and sometimes it may decode for several minutes). It was very sporadic. I began to think it must be a specific callsign but that was pure speculation. Oddly enough right now it has been decoding for several minutes. Usually the FT9 process is left orphaned and I have to kill it but not always. Decode Fast or Deep does not seem to make a difference. Without any error message I'm clueless where to begin but I'm also a newb on Raspberry and Linux. Do I need to start over with WSJTX-2.5.2 which I do have working on an identical Pi (but it's running "Raspbian GNU/Linux 10 (buster)") Or do I need to really start over with Buster and WZJTX-2.5.2 ? It felt great to accomplish this much but then to have this problem it's just taken the wind out of my sail.. maybe I should have stuck with build-a-pi or hampi.. 3:30 am.. maybe I should get some sleep.. Thanks de N5ZY 73
Timing! Today (several hours after I posted the request for help) a new version of WSJT-X was posted, 2.5.4. That solved the problem! No more crashing! WSJT-X 2.5.4 seems to work with Raspberry Pi Bullseye just fine!
Self-proclaimed NON-power user here: I was having similar "crash" issues with WSJTx when I updated to the 2.5.3 64 bit version on Windows 10. Two weeks ago I installed the 32 bit version of 2.5.3 which resolved the crashes and I had no further issues. The 32 bit ran fine on my 64-bit Windows 10 install. This Mon evening (1/3) I installed the new 2.5.4 64 bit version and it runs with no crashes of course, no trouble with callsigns that include a slant bar, and maybe even decodes a bit faster than before. I would suggest that to resolve your 'crash' troubles you consider rolling your host computer OS back to Windows 10 and use the 2.5.4 64 bit update of WSJTx, at least until Microsoft makes Windows 11 into a stable OS without patches and repairs every week. Usually being the first on a new Windows OS release isn't the most productive step to take.
