Take copy of your ~/config/cqrlog directory (with all subfolders and files) as backup.
Then remove install. I think in debian based systems it is "apt-get remove cqrlog".

When successfully ended give again "whereis cqrlog".
If there still is "cqrlog" somewhere you have to manually remove that file.

Then try again to install (repository and program) using line copied from download page. If you still get old version remove it again and try to install binaries "cqrlog_2.1.0_i386.tar.gz" or "cqrlog_2.1.0_amd64.tar.gz" depending your hardware.

When you have latest version restore copied directory ~/.config/cqrlog (When cqrlog is NOT running!!!)

Apt stores it's lists of repositories under /etc/apt from there you should chek that you really have Petr's repository installed ok.
Repository and it's contents should be ok as there are many users that have succeeded to install 2.1.0.

Being an Fedora user myself I can not give any better detailed informations. Systems are bit different.

--
Saku
OH1KH

Hi Remo!

Today I downloaded cqrlog_2.1.0_amd64.tar.gz from download page and I can confirm that it is 2.1.0(001)

You ask step by step description of the installation.
First backup your ~/.config/cqrlog folder with all files and subfolders to safe place (usb stick, perhaps) to save your logs.
Then download cqrlog_2.1.0_amd64.tar.gz (or the i386 version if you have 32bit OS).
Save downloaded file to /tmp
You can use browser on wget (console) for download.

Start console change dir to /tmp with:
cd /tmp

extract the file with command:
tar vzxf cqrlog_2.1.0_amd64.tar.gz (change filename if 32bit version).

Now you have folder /tmp/cqrlog-2.1.0 change to that with:
cd /tmp/cqrlog-2.1.0

Now there is folder "usr". It is same structure than you have from system root "/"
under "usr" you have "bin" and under that you have binary "cqrlog".

If you still have 2.0.5 installed you can try simply to start new binary by typing:
/tmp/cqrlog-2.1.0/usr/bin/cqrlog

I can not confirm this binary works over 2.0.5 install (I do not have 2.0.5 any more) but it is worh of trying.
If all works just replace existing binary:
sudo cp /tmp/cqrlog-2.1.0/usr/bin/cqrlog /usr/bin/cqrlog

If not, remove 2.0.5 installation. Then go to root directory:
cd /
extract downloaded file again:
sudo tar vzxf cqrlog_2.1.0_amd64.tar.gz (change filename if 32bit version)

Now it goes right away to right folders.

After that you might have to create icon for starting it as this kind of installation does not make icons.
Consult you desktop help for making start icons.

Anyway without icons you can still start from console by typing: cqrlog

--
Saku
OH1KH

Hi Marty!

Nice to see that you have succeeded to upgrade with manual process.

You should start cqrlog first and let it start rigctld.
Then you may start wsjt-x manually. Do not set cqlrog preferences to start it. Not recommended as if cqrlog dies it will pull down also wsjt-x.
After that choose "Remote mode for wsjtx". Work qsos.
Unselect "Remote mode for wsjtx" and continue with CW , RTTY or Fone qsos.
If you again like to use wsjt-x select "Remore mode for wsjtx". And so on....

You have to start rigctld only once !
Easiest way is to start it via cqrlog.
You can also start it at linux start using command line at file /etc/rc.local (i this it is the place of your linux version).
Or you can start it when you login to your desktop (entry place depends what desktop you are using)
You can get line format for /etc/rc.local by giving console command: ps ax | grep rig while cqrlog is running.
You get line like this:
3914 ? Sl 0:00 /usr/bin/rigctld -m 309 -r /dev/rig -t 4532 -p /dev/rig -P RTS -s 19200 --set conf=serial_handshake=None,dtr_state=Unset,rts_state=Unset
By copying all from "/usr/bin.....until end of line" you get working command to start rigctld from console, or rc.local file.

But as said: Easiest way is to start rigctld from inside of cqrlog. And start always cqrlog as first program.

You have to set wsjt-x settings again. I think you use your rig name there. Instead use "Hamlib NET rigctl"
By that setting no new instance of rigctld is started and you can switch between programs.(even more than just cqlrog and wsjtx if all are using same rigctld).

See the pictures of my setup.

Now that you can update manually and you are active wsjt-x user you could try also latest test binaries (for x86_64 kernels).
It is just copying a new /usr/bin/cqrlog from downloaded zip. (after backuping current things)
See this message: https://www.cqrlog.com/comment/5625#comment-5625

--
Saku
OH1KH

Hi Marty.
Do yo have polling from programs about same level as in my picture? (more than few seconds for both).

As you are now using same rigctld for both programs the rigcld will handle rig polling and you get actual information to your programs from rigctld, not directly from rig.

Rigctld itself has many parameters that can be changed. There are delays and repeats and all kind of settings. You just have to do a bit Googling to find description for them all. Perhaps first starting with console using command "man rigctld".

The "unusual" options are given with command -C or long format --set-conf=parm=val[,parm=val]*
Use "rigctl -L" at console for option list. Check them.

But before that:

You have another rigctld from your wsjt-x install. Check where it is. Use console you should get something like:

[saku@hamtpad /]$ whereis rigctld
rigctld: /usr/bin/rigctld /usr/local/bin/rigctld /usr/share/man/man1/rigctld.1.gz

[saku@hamtpad /]$ whereis rigctld-wsjtx
rigctld-wsjtx: /usr/local/bin/rigctld-wsjtx /usr/share/man/man1/rigctld-wsjtx.1.gz

If both exist try to give:
[saku@hamtpad /]$ rigctld -V
rigctl, Hamlib 3.1

[saku@hamtpad /]$ rigctld-wsjtx -V
rigctl, Hamlib 3.2~git

If you get different version numbers use the higher. I think it is "rigctld-wsjtx"
Put rigctld-wsjtx path to cqrlog/preferences/trx control to get newer version running.

Does it work any better?
If not, then it is time to play with "--set=" parameters for rigctld.

Let's try these for next.

After that you can go deeper search by taking start of rigctld away from cqrlog.
Start rigctld first from console (see how to get the command line with parameters from previous messages) adding an extra parameter "-vvvvv" to the parameter list.

Then start cqrlog and finally wsjt-x.
When programs run you can see debug information from rigctld console and see what goes wrong when errors happen with wsjtx.

--
Saku
OH1KH

Hi Marty!

"The WSJT-X log function works correctly. "
Means this that wsjt-x logs ok it's own log, or logs ok to cqrlog's log ?

If logging is transferred to cqrlog ok when pressing OK-button at wsjtx's logging window UDP transfer must work.
If not check cqrlog/preferences/fldigi/wsjtx interface and wsjtx/settings/Reporting to have same values.
It is better to use "127.0.0.1" in some cases than word "localhost" even it should mean same in address.
See my setup screenshot.

You should always set "cqrlog/NewQso/File/remote mode for wsjt" to get cqrlog read information from wsjt-x program.

When it is set:
IF you answer to wsjtx-CQ, or give report for someone that answered to your CQ, you should see station call
appearing to NewQSO/callsign and possibly additional information from qrz/hamqth if configured.

IF you monitor band and CQmonitor is open you should see stations calling CQ and their information related to your current
cqrlog. If CQmonitor does not open when "cqrlog/NewQso/File/remote mode for wsjt" is set you can open it from "cqrlog/NewQso/Window/Wsjtx monitor" (this varies between official and beta binaries).

IF you double click any line on CQ-monitor it should initiate qso with that station activating wsjt-x TX(+ set frequency).
WHEN you finish qso press "log qso" at wsjt-x main screen to get wsjtx logging window open, or modify setup so that wsjtx will pop up logging window when 73 is sent.
Add possible power and remarks information and press OK. That will close wsjt-x logging window and move data to cqrlog's log.

Poll rate of 2000 (2sec) is not high for modern PC and should not make problems.

Have you read this? http://www.saunalahti.fi/sakny/bin/cqrlog2/CqrlogAdditions2.pdf
It is for beta binary, but most of text is valid also for 2.1.0(001) release.

Hi Marty.
Fine that you have your settings now in order.

For split operation: Always use it if your rig supports it. You will notice support by selecting it and testing.

Explanation can be found when wsjt-x is running selecting "help" from top menu of main screen and from there select "Local user guide".
Opens to your web browser.
See section 4.2 Radio / sub section "Split operation"

--
Saku
OH1KH