Upgrade from version 2.0.5 to Version 2.1.0 problem

I've been using CQRLOG for about a year and really enjoy the program. Today I tried to upgrade from version 2.0.5 to version 2.1.0. I used the following line (copied from the download location on this site) in my terminal window:
sudo add-apt-repository ppa:ok2cqr/ppa;sudo apt-get update;sudo apt-get install cqrlog
(Note: I copied the entire line as shown, and pasted it into the terminal window and hit the return key).

Everything appeared to install correctly, but I noticed that after the install was complete, there was a line displayed that said, the current version was up to date. After starting CQRLOG, I noticed that I'm still on version 2.0.5. Even a computer reboot didn't do anything. Any thoughts as to what may be going wrong?

Could it be that you have cqrlog exec now in 2 different locations?
From console give: whereis cqrlog
If several found try to start each from console using full path like /usr/bin/cqrlog
Do they all start same version?

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.

I also have a problem with updating to V 2.1. As I have been a CQRLog user for a few years I've usually received updates form the ppa in Synaptic when they were released. That did not happen this time. From your post above I have found CQRLog in the following directories on my Mint 17.1 system:

It seems to me that the newest version of cqrlog is not present on the repository. Removed 2.05 version , but again on the new installation I have the same version (2.05)
Downloaded the tar.gz but can't install it...

It would be nice to have a step by step description of the installation.
Linux mint 17

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.

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

Thank you for this post. I'm running LMDE2, which is still running Debian old-stable( ! ) and it was impossible to update from 2.0.4 to 2.1.0 by the .deb archive as I've always done in the past, because of dependencies (libssl-dev & libmaria..dev). I uninstalled my previous install, and dload/install from the tar.gz and now it works!

As I have stated before I have the same problem. All past updates have been installed from the repository by Mint upgrade manager. The latest was not. The fact that it may be missing from the repository is possible. This is the first time in years I'm having trouble updating CQLog from the update manager, I suggest we ask Petr to check the contents of the ppa to be sure v 2.1 is included. Look forward to hearing from Petr.

You have not answered the basic question. Does the current version of CQRLog exist in Petr's repository? What happened to the automatic updates through Synaptic? I am a user of the ppa and have been for years . The upgrade should have happened automaticly as it has with past updates. I have not had any problems until now. Your instructions are appreciated but they relate only to the zipped package. Please address the issue with the ppa. Can we not check with Petr to see if the update is in the ppa?

As stated before I can not comment ppa issues as I am a Fedora user, that is not Debian based linux and it uses "dnf" for package install.
So I can not test Synaptic or any other method here wiithout first installing Debian/Mint/Ubuntu OS.

What I was able to do is check the contents of x86_64 based .tgz zipped binary. And it is 2.1.0(001),

I do not have either a "secret hotline" to Petr, so I'm as lost about ppa as others.
We just have to wait, but I think the HamQTH.com failure and restore eated so much Petr's time
that he now need to focus more to other things like family and work.

I just try to give as much help as I can on those things what I can because I feel stupid if I see someone asking help without getting any answers here.

I'm sure .tgz installation method works also for Debian based systems, but it is little more complicated as Synaptic or some other GUI based things.
When I have done my own addition versions to cqrlog I have noticed that almost every time upgrading works with only starting the new binary "cqrlog" itself. So extracting .tgz to /tmp and starting binary from there is very simple and save (as long as logs are backuped)
And if it works, just copy the only one binary file to /usr/bin solves upgrading.

And it does not spoil anything as system still thinks 2.0.5 is installed although binary would be 2.1.0 and next ppa upgrade should work in usual way.

Thank you for your comment. I'll install from the archive as you instructed after backing up cqrlog. You are right to try to be of help. You should not feel stupid if you do not know all the answers. Hopefully when things are better for Petr the ppa will be working again. I'll let you know how it worked out.

I have followed your instructions and now have CQRLog 2.1.0 running from ~/Desktop/tmp/cqrlog-2.1.0/usr/bin.
Seems to load OK and run. I have not fully tested it yet but, it will probably work. Next Should I copy only cqrlog file to /usr/bin overwriting the cqrlog file there. Is that correct? then copy over the .config/cqrlog directory if needed.

Worked with CQRLog V 2.1 this weekend. Tried all the functions I normally use and all worked as expected. I did have one problem however. When I start CQRLog I have it set to control the radio. No problem there. If I start WSJT-X in the remote mode from CQRLog WSJT-X tries to to control the radio and an error results. To work with WSJT-X remote I must start CQRLog without controling the radio. The WSJT-X is a major feature. I use it when I'm using FT8. I like to operate voice then switch to digital. Is there a simple way I can do this without changing my preferences and restarting CQRLog? Perhaps a menu choice to start and stop rigctrl.

Thanks for all your help and patience. I still think that CQRLog is one of the best logging programs out there.

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

File:

Followed your suggestions. That cured the rigctl problem. No I have problems with Hamlib errors. "hamlib protocol error while getting VFO status" and "hamlib protocol error getting ptt status" Both occur frequently. If I'm trying to make a qso WSJ-X shuts down the automatic xmit/rcv sequence. These errors occur at random times and do not seem to be related to any event. WSJT-X will run for awhlle then error out. I do not have any problem when WSJT-X is running alone. I think both programs may be polling the radio at the same time and a conflict occurs. I am using a USB serial adapter cable which has per form well in the past.

Can we modify the sampling rate to give priority to WSJT-X and less to CQRLog? What do you suggest? As these errors interupt WSJT-X qso's; I'd like to get this issue fixed.

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:

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.

Since I reworked the configurations it looks like the hamlib protocol errors are gone. I'll watch this over the weekend to confirm. Now have a new problem. QSO data does not transfer from WSJT-X to CQRLog and the "wsjt-x monitor" window is not populated.The WSJT-X log function works correctly. Could this be caused by the high (2000) poll rate in CQRLog? Tried the option in CQRLog menu to connect to WSJT-X remote but does not correct the problem.

"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.

File:

I got it working now. The problem was that I had not configured PSK Reporter properly. Your pdf on the additions to CQRLog was most helpful. Hopefully it could be added to the CQRLog documentation. Now that I have configured PSK Reporter I assume my QSO data will be added to PSK Reporter. You set split operation in the radio section of WSJT-X to rig. I'm not sure why you set it that way. Would you please tell me why this is of benefit.

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"

I recently did a fresh install of Ubuntu 17.10 and can report that Petr's repository is still providing only version 2.0.5 of CQRLog (as of October 30, 2107).

Previously I was working with Ubuntu 17.04 (upgraded from 16.04) but was able to get CQRLog 2.1 from the repository. It eventually ran fine, after I figured out the OTHER dependencies that Synaptic apparently didn't know about. That was very frustrating. I'm brand new to Linux and this almost caused me to give up the whole thought of using Linux for my ham activities.

I haven't had any luck getting CQRLOg 2.0.5 to run, though, in Ubuntu 17.10. So far it's having trouble connecting to the sql database. Here we go again........I'll post THOSE questions in a separate post. I haven't tried a manual installation of CQRLog 2.1-- I wonder if it would have better luck with the sql connection......?

I hadn't seen that yet, Saku. I'm not sure I understand exactly what Petr was trying to say there other than NO mariadb stuff is needed. I'll have to go check, but I don't think libmysqlclient18 is even in the repository any more. I remember installing libmysqlclient.20, but it wasn't included in the install that Synaptic did for me. I was just poking around trying to find something that CQRLog might like......but it wasn't enough to provide a connection to the sql database. I'll try to remove anything related to mariadb and see where that gets me.