Hello,
This is my first post here; I'm using CQR LOG 2.3.0 and WSJT-X 1.9.1 on a Linux openSUSE Tumbleweed system with dual monitors, the first (laptop) is 1366X768 and external (LG) is 1920x1080 in resolution.
Both applications (WSJTS-X and CQRLOG) are working correctly if started separately, but if I start CQRLOG before and then select New QSO-> WSJT-X remote, then WSJT-X starts with a different window layout so that the fields in WSJT-X window for TX frequency, RX frequency and Report are displayed shrinker, or better the dimensions of these fields are not large enough to display the audio frequency in KHz for TX and RX as well as Report value in the db field.
I suppose that the command launched by CQRLOG to start the WSJT-X remote being the cause of wrong screen settings for the external monitor LG 1920x1080, which I use as the main screen for WSJT-X
Any suggestion to solve this problem is very much welcomed.
Thanks, PY1ZRJ Marco
HI!
That may be the reason.
I have always recommended to start cqrlog and wsjtx manually. It does not matter if you first start wsjtx remote and then start wsjtx-program or start wsjtx-program first and then start wsjtx remote after that.
If you let cqrlog start wsjtx when remote is selected wsjtx will run as child process of cqrlog. If, for some reason, cqrlog stops (crash) it will take down also wsjtx.
Usually this happens in the middle of qso ;-( but if you have started wsjtx manually it will keep on running and you can finish qso, start cqrlog again and finally log the qso in usual way.
So accept a bit inconvenience and try to start wsjtx manually and look if that helps for display problem.
--
Saku
OH1KH
Hi Saku,
Many thanks for your fast reply!
I've just discovered that the issue is present on WSJT-X (shrink-ed fields as I told) when I start it manually, and it occurs exactly the same when I start WSJT-X from CQR LOG clicking on New-QSO wsjt-x remote so evidently this selection calls "wsjtx binary".
(See annexed picture).
On the other hand, I cannot start WSJT-X from inside CQRLOG, because there is a stale lock file of previous WSJT-X, so I should try to remove it because I cannot launch another WSJT-X if there is one already running.
I'm a bit confused now.
File:
This is the stale lock I was talking about if I try to start WSJT from CQRLOG.
File:
Last comment for today: the start command for WSJT-X from XFCE icon is: "wsjtx --style=fusion".
Dunno if it will be possible to add a setting in CQRLOG in order to select a custome setting to start WSJT-X.
Thanks and 73 de PY1ZRJ Marco
Sorry! Now my last comment because I found a workaround:
I create a simple bash script /home/marco/bin/wsjtx-fusion in my home dir wherein I put:
#!/bin/bash
/usr/bin/wsjtx --style=fusion
Then on main CQRLOG settings->fldigi/wsjt interface->Path to wsjtx, I put /home/marco/bin/wsjtx-fusion
Now the fields TX, RX and Report are displayed correctly in WSJT-X, without any reduction in their size.
Sorry to have raised an issue that could be easily resolved with a bit of care.
73 de PY1ZRJ
Hi!
Nice that you got it working.
The differences between X desktops can sometimes make lot of trouble.
About the stale lock file:
You may find difference selecting wsjtx/settings/audio either "pulse" for both, or "alsa-input....." and "alsa-output..." instead.
In my hamshack PC (fedora 27) both works and I use "pulse". But on my other PC (Fedora 28) only "alsa...." works proper way. Using "pulse" it leaves open process when closing wsjtx and thus "stale lock file" on next restart.
Although both ways use same sound device there may be difference in different linux versions (I think this is QT version's problem).
So it it worth of testing both ways to see is there difference.
--
Saku
OH1KH
Hi Saku!
I neither see "pulse" in my audio settings options.
I have set to alsa both output and input as you can spot from the attached image.
Note that it seems this is the best configuration for my environment.
Anyhow now the stale lock is not anymore an issue because the WSJT-X main window is displayed in the right dimensions.
Cheers,
File:
OK!
Maybe you do not have pulse audio installed at all (?) It should appear as one choice to those selectors you have now showing "alsa" in your picture.
Anyhow using alsa is good choice and ok about that right dimensioning of window effected also to stale lock file.
--
Saku
OH1KH
Hi Saku!
Yes it looks like I have pulse on my computer but I don't see the selection option specifically indicating for it from WSJT-X audio settings:
marco@linux-turion64:~> rpm -qa|grep pulse
pulseaudio-utils-12.2-1.1.x86_64
libxine2-pulse-1.2.9-136.10.x86_64
pulseaudio-lang-12.2-1.1.noarch
xfce4-panel-plugin-pulseaudio-lang-0.4.1-1.2.noarch
libpulse0-32bit-12.2-1.1.x86_64
pulseaudio-module-gsettings-12.2-1.1.x86_64
libpulse0-12.2-1.1.x86_64
libpulse-mainloop-glib0-32bit-12.2-1.1.x86_64
mpg123-pulse-1.25.10-2.1.x86_64
pulseaudio-module-lirc-12.2-1.1.x86_64
pulseaudio-module-bluetooth-12.2-1.1.x86_64
pulseaudio-module-jack-12.2-1.1.x86_64
alsa-plugins-pulse-32bit-1.1.6-3.1.x86_64
pulseaudio-esound-compat-12.2-1.1.x86_64
xfce4-panel-plugin-pulseaudio-0.4.1-1.2.x86_64
libpulse-devel-12.2-1.1.x86_64
pulseaudio-12.2-1.1.x86_64
pulseaudio-module-zeroconf-12.2-1.1.x86_64
pulseaudio-bash-completion-12.2-1.1.x86_64
pulseaudio-utils-32bit-12.2-1.1.x86_64
libpulse-mainloop-glib0-12.2-1.1.x86_64
pulseaudio-module-x11-12.2-1.1.x86_64
alsa-plugins-pulse-1.1.6-3.1.x86_64
marco@linux-turion64:~>
marco@linux-turion64:~> rpm -qa|grep alsa
alsa-1.1.6-2.2.x86_64
alsa-plugins-pulse-32bit-1.1.6-3.1.x86_64
alsa-utils-1.1.6-1.3.x86_64
alsa-oss-32bit-1.1.6-2.2.x86_64
alsa-plugins-1.1.6-3.1.x86_64
alsa-oss-1.1.6-2.2.x86_64
alsa-devel-1.1.6-2.2.x86_64
alsa-plugins-pulse-1.1.6-3.1.x86_64
marco@linux-turion64:~>