For example: I won't report that, for some reason, 2.2.1 seems to cycle my 7300 from VFO A to VFO B and back to VFO A on startup, which makes me need to press the "TUNE" button again to get the auto-tuner back in sync with the radio. I won't report that changing bands to a band 15m and above using the dropdown in WJST-X automatically turns my preamp on.. sometimes it's Preamp1, others Preamp2, and sometimes not at all. I also won't report that both of these behaviors are undesirable. de AI8W -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS/CM/CC/E/IT/TW d-@ s+:+ !a C++$@ UBLVSCX*++++(on)$>$ P++>$ L+++$ E+@ W++>$ N+++ o+@ K+++ w@ O+@ M-@ V@>$ PS+@ PE@ Y+ PGP++ t+ 5+ X++ R@* tv++ b+>$ DI++ D+ G++ e h r+++ y+++ ------END GEEK CODE BLOCK------
On Sat, Jun 6, 2020 at 7:50 PM Topher Petty <ai8...@gmail.com> wrote: > Bill: > You tell me. All I know is that I was having issues with rig control on > two other pieces of software, and when I uninstalled WSJT-X 2.1.x, those > problems disappeared. The other two pieces of software worked flawlessly > with their hamlib rig control, even surviving reboots, until I re-installed > WSJT-X 2.1.x. It got to the point that I refrained from using WSJT-X and, > instead, concentrated on CW (keyed by hand, copied by head), RTTY, and > PSK-31... > The (mis)behavior doesn't seem to exist with 2.2.1 installed, so I'm not > sure what the issue was with the older version, or what it is that changed > between 2.1.x and 2.2.x w/r/t hamlib. > Since it seems you get quite ruffled by the reporting of symptoms that are > WSJT-X related, I'll refrain from doing so in the future. > You have a great evening, Bill. Enjoy a brandy and relax. > > 73 de AI8W, Chris > > -----BEGIN GEEK CODE BLOCK----- > Version: 3.1 > GCS/CM/CC/E/IT/TW d-@ s+:+ !a C++$@ UBLVSCX*++++(on)$>$ P++>$ L+++$ E+@ > W++>$ N+++ o+@ K+++ w@ O+@ M-@ V@>$ PS+@ PE@ Y+ PGP++ t+ 5+ X++ R@* tv++ > b+>$ DI++ D+ G++ e h r+++ y+++ > ------END GEEK CODE BLOCK------ > > > On Sat, Jun 6, 2020 at 7:06 PM Bill Somerville <g4...@classdesign.com> > wrote: > >> Chris, >> >> here's the list of files installed by the WSJT-X Debian package, no more, >> no less. Please explain to me how any of those files could possibly >> interfere with another application? Indeed, how could any of them have >> anything to do with some other Hamlib installation on your system. >> >> BTW, exactly the same list of files is installed by v2.2.1. >> >> bill@Ubuntu-64-vbox:~$ dpkg-deb -c ~/Downloads/wsjtx_2.1.0_amd64.deb >> drwxr-xr-x root/root 0 2019-07-14 00:54 ./usr/ >> drwxr-xr-x root/root 0 2019-07-14 00:54 ./usr/bin/ >> -rwxr-xr-x root/root 14392 2019-07-14 00:54 ./usr/bin/fcal >> -rwxr-xr-x root/root 10296 2019-07-14 00:54 ./usr/bin/fmeasure >> -rwxr-xr-x root/root 10224 2019-07-14 00:54 ./usr/bin/fmtave >> -rwxr-xr-x root/root 216248 2019-07-14 00:54 ./usr/bin/ft8code >> -rwxr-xr-x root/root 88256 2019-07-14 00:54 ./usr/bin/jt4code >> -rwxr-xr-x root/root 90720 2019-07-14 00:54 ./usr/bin/jt65code >> -rwxr-xr-x root/root 949584 2019-07-14 00:54 ./usr/bin/jt9 >> -rwxr-xr-x root/root 84952 2019-07-14 00:54 ./usr/bin/jt9code >> -rwxr-xr-x root/root 247968 2019-07-14 00:54 ./usr/bin/message_aggregator >> -rwxr-xr-x root/root 227632 2019-07-14 00:54 ./usr/bin/msk144code >> -rwxr-xr-x root/root 103848 2019-07-14 00:54 ./usr/bin/qra64code >> -rwxr-xr-x root/root 120648 2019-07-14 00:54 ./usr/bin/qra64sim >> -rwxr-xr-x root/root 4400800 2019-07-13 22:54 ./usr/bin/rigctl-wsjtx >> -rwxr-xr-x root/root 4330720 2019-07-13 22:54 ./usr/bin/rigctlcom-wsjtx >> -rwxr-xr-x root/root 4400736 2019-07-13 22:54 ./usr/bin/rigctld-wsjtx >> -rwxr-xr-x root/root 116896 2019-07-14 00:54 ./usr/bin/udp_daemon >> -rwxr-xr-x root/root 8534192 2019-07-14 00:54 ./usr/bin/wsjtx >> -rwxr-xr-x root/root 100800 2019-07-14 00:54 ./usr/bin/wsprd >> drwxr-xr-x root/root 0 2019-07-14 00:54 ./usr/share/ >> drwxr-xr-x root/root 0 2019-07-14 00:54 ./usr/share/applications/ >> -rw-r--r-- root/root 246 2018-06-05 20:18 >> ./usr/share/applications/message_aggregator.desktop >> -rw-r--r-- root/root 220 2018-06-05 20:18 >> ./usr/share/applications/wsjtx.desktop >> drwxr-xr-x root/root 0 2019-07-14 00:54 ./usr/share/doc/ >> drwxr-xr-x root/root 0 2019-07-14 00:54 ./usr/share/doc/WSJT-X/ >> -rw-r--r-- root/root 137 2018-06-05 20:18 >> ./usr/share/doc/WSJT-X/AUTHORS >> -rw-r--r-- root/root 741 2018-06-05 20:18 ./usr/share/doc/WSJT-X/BUGS >> -rw-r--r-- root/root 31953 2018-06-05 20:18 >> ./usr/share/doc/WSJT-X/COPYING >> -rw-r--r-- root/root 13175 2019-07-14 00:42 >> ./usr/share/doc/WSJT-X/INSTALL >> -rw-r--r-- root/root 75799 2019-07-14 00:42 ./usr/share/doc/WSJT-X/NEWS >> -rw-r--r-- root/root 4228 2018-11-26 15:50 ./usr/share/doc/WSJT-X/README >> -rw-r--r-- root/root 2829 2018-06-05 20:18 ./usr/share/doc/WSJT-X/THANKS >> -rw-r--r-- root/root 216 2019-07-14 00:54 >> ./usr/share/doc/WSJT-X/changelog.Debian.gz >> -rw-r--r-- root/root 392 2019-07-14 00:29 >> ./usr/share/doc/WSJT-X/copyright >> -rw-r--r-- root/root 4227318 2019-07-14 00:42 >> ./usr/share/doc/WSJT-X/wsjtx-main-2.1.0.html >> drwxr-xr-x root/root 0 2019-07-14 00:54 ./usr/share/man/ >> drwxr-xr-x root/root 0 2019-07-14 00:54 ./usr/share/man/man1/ >> -rw-r--r-- root/root 50 2019-07-14 00:42 >> ./usr/share/man/man1/jt4code.1.gz >> -rw-r--r-- root/root 2173 2019-07-14 00:42 >> ./usr/share/man/man1/jt65code.1.gz >> -rw-r--r-- root/root 43 2019-07-14 00:42 ./usr/share/man/man1/jt9.1.gz >> -rw-r--r-- root/root 50 2019-07-14 00:42 >> ./usr/share/man/man1/jt9code.1.gz >> -rw-r--r-- root/root 1415 2019-07-14 00:43 >> ./usr/share/man/man1/message_aggregator.1.gz >> -rw-r--r-- root/root 868 2019-07-14 00:42 >> ./usr/share/man/man1/rigctl-wsjtx.1.gz >> -rw-r--r-- root/root 913 2019-07-14 00:43 >> ./usr/share/man/man1/rigctlcom-wsjtx.1.gz >> -rw-r--r-- root/root 861 2019-07-14 00:43 >> ./usr/share/man/man1/rigctld-wsjtx.1.gz >> -rw-r--r-- root/root 1588 2019-07-14 00:43 >> ./usr/share/man/man1/udp_daemon.1.gz >> -rw-r--r-- root/root 2189 2019-07-14 00:42 >> ./usr/share/man/man1/wsjtx.1.gz >> -rw-r--r-- root/root 2049 2019-07-14 00:42 >> ./usr/share/man/man1/wsprd.1.gz >> drwxr-xr-x root/root 0 2019-07-14 00:54 ./usr/share/pixmaps/ >> -rw-r--r-- root/root 17659 2018-06-05 20:18 >> ./usr/share/pixmaps/wsjtx_icon.png >> drwxr-xr-x root/root 0 2019-07-14 00:54 ./usr/share/wsjtx/ >> -rw-r--r-- root/root 3738096 2018-06-05 20:18 ./usr/share/wsjtx/JPLEPH >> bill@Ubuntu-64-vbox:~$ >> >> Before you claim it is somehow to do with the libraries that WSJT-X uses >> from the system, here is the list of libraries loaded by WSJT-X: >> >> bill@Ubuntu-64-vbox:~$ ldd `which wsjtx` >> linux-vdso.so.1 (0x00007ffd2619d000) >> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fac83591000) >> libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 >> (0x00007fac83379000) >> libfftw3f.so.3 => /usr/lib/x86_64-linux-gnu/libfftw3f.so.3 >> (0x00007fac82f6c000) >> libQt5SerialPort.so.5 => >> /usr/lib/x86_64-linux-gnu/libQt5SerialPort.so.5 (0x00007fac82d54000) >> libQt5PrintSupport.so.5 => >> /usr/lib/x86_64-linux-gnu/libQt5PrintSupport.so.5 (0x00007fac82ae5000) >> libQt5Widgets.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 >> (0x00007fac8229e000) >> libQt5Sql.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Sql.so.5 >> (0x00007fac82055000) >> libQt5Multimedia.so.5 => >> /usr/lib/x86_64-linux-gnu/libQt5Multimedia.so.5 (0x00007fac81d3e000) >> libQt5Network.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 >> (0x00007fac819b2000) >> libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 >> (0x00007fac81249000) >> libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 >> (0x00007fac80afe000) >> libgfortran.so.4 => /usr/lib/x86_64-linux-gnu/libgfortran.so.4 >> (0x00007fac8071f000) >> libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 >> (0x00007fac80396000) >> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fac7fff8000) >> libgomp.so.1 => /usr/lib/x86_64-linux-gnu/libgomp.so.1 >> (0x00007fac7fdc9000) >> libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 >> (0x00007fac7fbb1000) >> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 >> (0x00007fac7f992000) >> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fac7f5a1000) >> /lib64/ld-linux-x86-64.so.2 (0x00007fac87229000) >> libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007fac7f383000) >> libpulse.so.0 => /usr/lib/x86_64-linux-gnu/libpulse.so.0 >> (0x00007fac7f133000) >> libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fac7ef16000) >> libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x00007fac7ec8a000) >> libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 >> (0x00007fac7ea58000) >> libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 >> (0x00007fac7e7ba000) >> libicui18n.so.60 => /usr/lib/x86_64-linux-gnu/libicui18n.so.60 >> (0x00007fac7e319000) >> libicuuc.so.60 => /usr/lib/x86_64-linux-gnu/libicuuc.so.60 >> (0x00007fac7df61000) >> libdouble-conversion.so.1 => >> /usr/lib/x86_64-linux-gnu/libdouble-conversion.so.1 (0x00007fac7dd50000) >> libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 >> (0x00007fac7da39000) >> libquadmath.so.0 => /usr/lib/x86_64-linux-gnu/libquadmath.so.0 >> (0x00007fac7d7f9000) >> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fac7d5f1000) >> libpulsecommon-11.1.so => >> /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so >> (0x00007fac7d373000) >> libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 >> (0x00007fac7d126000) >> libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0 >> (0x00007fac7cef5000) >> libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 >> (0x00007fac7cc3f000) >> libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 >> (0x00007fac7c98b000) >> libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 >> (0x00007fac7c75e000) >> libicudata.so.60 => /usr/lib/x86_64-linux-gnu/libicudata.so.60 >> (0x00007fac7abb5000) >> libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fac7a943000) >> libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 >> (0x00007fac7a71b000) >> libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 >> (0x00007fac7a497000) >> libwrap.so.0 => /lib/x86_64-linux-gnu/libwrap.so.0 (0x00007fac7a28d000) >> libsndfile.so.1 => /usr/lib/x86_64-linux-gnu/libsndfile.so.1 >> (0x00007fac7a014000) >> libasyncns.so.0 => /usr/lib/x86_64-linux-gnu/libasyncns.so.0 >> (0x00007fac79e0e000) >> libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 >> (0x00007fac79ad6000) >> libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 >> (0x00007fac798d2000) >> libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 >> (0x00007fac796cc000) >> liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fac794a6000) >> liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 >> (0x00007fac7928a000) >> libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 >> (0x00007fac78f6e000) >> libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x00007fac78d54000) >> libFLAC.so.8 => /usr/lib/x86_64-linux-gnu/libFLAC.so.8 >> (0x00007fac78add000) >> libogg.so.0 => /usr/lib/x86_64-linux-gnu/libogg.so.0 >> (0x00007fac788d4000) >> libvorbis.so.0 => /usr/lib/x86_64-linux-gnu/libvorbis.so.0 >> (0x00007fac786a9000) >> libvorbisenc.so.2 => /usr/lib/x86_64-linux-gnu/libvorbisenc.so.2 >> (0x00007fac78400000) >> libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 >> (0x00007fac781e5000) >> libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007fac77fd0000) >> libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 >> (0x00007fac77dbb000) >> bill@Ubuntu-64-vbox:~$ >> >> FWIW, you will not see Hamlib mentioned there because, as I said above, >> it is statically linked into WSJT-X. >> >> 73 >> Bill >> G4WJS. >> >> On 06/06/2020 22:35, Topher Petty wrote: >> >> Bill, I just looked at github, and the latest commit was 23 minutes >> ago... >> I appreciate your stance w/r/t conflicts, however, uninstalling wsjtx 2.1 >> resolved issues I was having with SKCClogger and FLDIGI. it may be >> "rubbish", but using dpkg to remove the .deb published on the Princeton >> website resulted in the other two softwares behaving as expected, which >> leads me to the conclusion that your assertion that wsjtx was the cause of >> the issue being rubbish is, itself, rubbish. >> Luckily, the installation of the deb for 2.2.1 did not cause the return >> of the issues I was having. >> Carry on. >> 73 de AI8W, Chris >> >> On Sat, Jun 6, 2020, 15:11 Bill Somerville <g4...@classdesign.com> wrote: >> >>> On 06/06/2020 19:55, Topher Petty wrote: >>> > Out of curiosity, why not list hamlib as a prerequisite and have >>> > people install it separately, so that those of us that already use it >>> > and keep it updated don't have duplicated libraries on our systems >>> > that can potentially cause version conflicts? >>> > Hamlib has installers for windows and Mac on the git site, iirc.. >>> > I just tracked down difficulties I was having with SKCClogger and >>> > FLDIGI to the differing versions of hamlib installed on my system, and >>> > un-installing wsjtx fixed those other two bits of software... >>> > Going to bump up to 2.2.1 to test... Crossing my fingers I don't get >>> > to play "lib track bingo" again. >>> > >>> > 73 de AI8W, Chris >>> >>> Hi Chris, >>> >>> the last release of Hamlib was several Years ago. Although the project >>> has active development it is rather overdue for a new release. We have >>> worked with a snapshot of Hamlib, which we would prefer to bundle with >>> WSJT-X, at least until an official release with support for current rigs >>> is available. We have over the last several versions included some >>> patches that were ahead of even the Hamlib master branch, all of those >>> have been submitted and accepted by the Hamlib developers. We would >>> either have to deny a lot of users support for their new rigs or ask >>> them to install versions of Hamlib that may clash with other >>> appliactions or system installed versions. By static linking Hamlib we >>> avoid that mess, unfortunately most Linux distributions object to static >>> linking other projects's libraries so the package maintainers have to >>> unpick out build scripts to comply. We would gladly revert to having >>> WSJT-X dynamically link to Hamlib, just like it does with Qt and FFTW3 >>> but on balance at the moment it is not the best option for users. That >>> may change soon. >>> >>> Note that your assertion that the Hamlib used with WSJT-X might cause >>> conflicts is rubbish, the WSJT-X exposes nothing from the Hamlib it >>> uses. There are no version conflicts unless you have messed with our >>> build scripts. >>> >>> 73 >>> Bill >>> G4WJS. >>> >> >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
