Upgraded V2.6.0 from 001 to alpha 126 - Now GLIBC failure - won't start CQRLog

4 posts / 0 new
Last post
WG9L
Upgraded V2.6.0 from 001 to alpha 126 - Now GLIBC failure - won't start CQRLog

I tried to upgrade my version 2.6.0 (001) gtk2 to 2.6.0 alpha 126. I read, but didn't fully understand exactly what Saku meant on the upgrade page about the following:

"NOTE: For now on binaries are compiled using system that has GLIBC version 2.35.
If you can not start Cqrlog after update check your GLIBC version with command console: ldd --version Update GLIBC if it is below 2.3.5. If you do not want to do that you can compile this source (see 1 folder up) with your current OS version and get it running. Note that the Alpha source version is usually one step higher than ready compiled versions."

Now I can't start CQRLog. From researching the version history of CQRLog, it looks like alpha 122 does not require the newer version of GLIBC. My current version of GLIBC is (ldd --version) Version 2.31 - I am running Linux Mint version 20.3

Can I use newupdate.sh to fetch an older version of CQRLog (example alpha 122) and just replace the new alpha 126 version (basically over write it)?

Thanks,
Bob

PA3GOS
Upgraded V2.6.0 from 001 to alpha 126 - Now GLIBC failure - won

Hi Bob,

I think you can. Make sure you have backed-up your data from .config/cqrlog.
Simply copy the directory to a place you can remember.

That way, even if things do get messed up, you can always recover.

Good luck with it and let us know when it works,

Tjalling

oh1kh
Upgraded V2.6.0 from 001 to alpha 126 - Now GLIBC failure - won'

Hi Bob!
If you used newupdate.sh script it always does backup before upgrading. You just need to find them from your conputer.

In this case all you need to do is to navigate to folder /usr/bin
The best way is to open the command console and then give
cd /usr/bin
After that give:
ls cqrlog*
You should see at least two names. the plain "cqrlog" is the program you updated and can't now open. other one is "cqrlog" with date as suffix.
If you have used newupdate.sh script several times you may see many "cqrlog" with dates as suffix.
All they are backups from previous versions. Now you need to copy the backup over the plain "cqrlog".

Give:
sudo cp cqrlog-20240730-090441 cqrlog

Of course the date-time you have different there than my example command. If there are several names "cqrlog" with date as suffix try to select that one that has date-time when you last run the newupdate.sh

That is all you need. Then you should be able to start old cqrlog.

newupdate.sh backups also your log and settings folder ~/.config/cqrlog but in this case when you never was able to run new cqrlog version restoring that is not needed.
How ever, If you ever need to do that, the system is same:
At your ~/.config folder you have folder "cqrlog" (the current one in use and backup folders that have "cqrlog" and date as suffix)
If you ever need to restore your logs and settings just remove folder "cqrlog" and make copy from backup folder using name "cqrlog" .

The third backup is help files folder.
They do not affect running the program and now if you restored the program you will still have new help files.
If you want them also to be restored give:
cd /usr/share/cqrlog
then give:
ls help*
There are "help" and "help" with date suffix folders made every time you had run newupdate.sh
Just pick up the one with right date and give:
sudo rm help
and then:
sudo mv help-20240730-090441 help

Of course you have different date also here as in my example, but it is the same you did have with "cqrlog".

All these actions are told in newupdate.sh's log file that it makes to folder /tmp during runtime. (of course /tmp is cleaned up if you restart your PC)

--
Saku
OH1KH

jendy henna
abc

Many games are designed to Drive Mad encourage healthy competition, teaching players how to win and lose gracefully.