Hi Waka!

Do not give up!
You said "Cqrlog did not run". Any error visible? If you start cqrlog by typing "cqrlog" in console you should see something.
At least if you type "cqrlog --debug=1"

Test run in lazarus-ide can also have "--debug=1" It comes from "Run / Run parameters". There is 0 as default, change it to 1.
Then open "View / Debug windows / Console IN/Output" you see same things as with console run using --debug=1

Then you can define how far it starts before you get error.

Do you have localized (Japan) Linux?
Can you test with English version of Fedora (maybe set up a virtual machine)?

I had once an error with fldigi and we had long chats with Dave. Tried many debugs and did not find reason why I could not set up Hamlib connection but for Dave it worked always. I installed English version of Fedora as virtual machine and started to compare and finally we found the reason. It was not in fldigi, but one of the c.o. programs where localisation changed the way of handling decimal numbers.

This could be something similar because it should not be so difficult.

If you reinstall Fedora then first install cqrlog from package and start it to make sure it runs ok.
After that get the source using "git clone" and make "share" symlink to cloned "cqrlog" folder for testing with lazarus-ide

Daily before starting to compile go to cqrlog directory that was created by "git clone" and issue command "git pull" to get the latest source changes.

I wish I could give better help.
Next I would try with English version of Fedora

HI!

Starting from easy part:
You src/cqrlog has error trace compiled in. That is why it is so big in size. See project options/error tracing/Generate info for the debugger.
The best side of this is that you can put break point in source code line with F5. Then when program runs (green arrow) it stops to F5 line and you can step it forward line by line with F8 and when seen what happens you can continue normal run with green arrow. And what is even better you can take away breakpoint with F5 and put it to other line with F5 while program is running and it will again stop when it comes to that line you set.
That makes the file so big.

There is "Oracle VM virtual box" that you can install. If you have room in HD and multi core CPU virtual machine runs quite happy using as default one of the CPU cores.
In my Lenovo X201 there is 4 core CPU and 250Gb SSD. While running several "normal programs" I can start a virtual machine, I have Mint20 only installed now and everything runs smoothly. Mint machine uses 20Gb of SSD and one CPU core. Starting and stopping virtual machines do not need any reboots for the host linux system. And when virtual mahine does not run it is very easy to backup and move, it is just a file.

Then the hard part:
Filesystem formats should not effect in any way as long as system is error free. I use ext4 in all my systems.

Your receipt is just the same I use.
QSocketNotifier: error looks same as in https://wiki.lazarus.freepascal.org/Qt5_Interface#libqt5pas. I assume you have read that already.
They talk about wayland there.
My setup is LXDE https://spins.fedoraproject.org/fi/lxde/
But as said in beginning Grayline map RBN connection makes similar QSocketNotifier error, so it is not guaranteed to be caused by wayland.

I am quite out of ideas.
How ever I think you can compile using (project options) gtk2 but then you are back with those red arrow pointed problems.

How about trying to set a bit smaller font size with gtk2?
Preferences/Fonts unselect "use default settings" and then set all 4 fonts again. I have there "Sans 9" in all.
Is 9 too small for you with your zero slashed font?

Now when you have learned to use lazarus-ide nothing stops you to adjust column sizes in NewQSO window.
from Project/Forms (Shift+F12) you get a list. Write NewQSO and you see frmNewQSO. Select that and press OK.

You get graphical designer for NewQSO form.
Click callsign column with mouse left. You get black dots around it.
Point middle dot on right edge and press mouse left down and start to stretch column to right.
Same way you can do with all columns and with even whole NewQSO form.

When you are happy make test run to see what it looks like when cqrlog is running.

Then you have your own custom designed cqrlog. That is best in OpenSource programming.

Thanks Waka San!

I made new bug when fixing date change in old qso edit. It caused Offline to to turn always off.
Now fixes and will make pull request soon.

HI !
Contest box size, when you have released left side anchor keeps steady. If left side anchor is set box will stretch vertically if New QSO window is stretched. But remember that it is hidden box and does not show normally.

You can get rid of the blank space when runnig. Do not maximize window, make it smaller and stretch to size you want. Cqrlog will remember window position and size if closed normally.

You changes are in fNewQSO.lfm

Following is not perhaps the proper way but I would do it that way:

1) copy fNewQSO.lfm to somewhere . Your home directory or usb stick.
2) when in cqrlog root folder ( If you made git clone in your home dir it is ~/cqrlog ) give command: git checkout . (note: one dot included in command) It will erase all changes you made and return to original source.
3) give command: git pull (there are new commits from yesterday)
4) give command: git checkout -b mynewqso (you are now in branch "mynewqso")
5) copy saved fNewQSO.lfm to src folder replacing the original.
4) give command: git commit -am" my first modification"

Now you can do more modifications. If they are not good give comamnd : git checkout . (not the dot at end) and you are at starting point,
If you think modification is good give command: git commit -am"my second modification" and it will become your branch "root"

Every time you plan to pull from web first give: git checkout master
It does not change master if you have changes that are not committed. Then first give: git commit -am"some name for commit"

You can always check situation with command: git status
When you get to master then give command: git pull

After that command: git checkout mynewqso and when passed there command: git merge master
If no errors give command:git commit

That way you can always pull to master branch and keep it even with web and make local merge from that to your other branch(es).

Very often you will see that merge does not succeed and you have to do manual fixing to get it through. I use program "diffuse" for that.
diffuse src/fNewQSO.lfm (if that failed on merge) and you will see the original and new one and do changes manual then save changes.
After that you need to do: git status to see what waits for addition, then git add . (note dot) and git commit to finish merge.

I know this is very short guide.

I had lot of difficulties to understand how git works at beginning. (and still I'm not good with it) fortunately I got good instructions from DL7OAP.
Without them I probably would have given up with git.
Now when used it more I have noticed it is very handy tool, but sometimes I still have problems and need Google for help,

You can always change any anchoring as "floating". Keep the checkbox checked but choose (nil) from sibling. Then there is anchor to nil and you can freely move object with mouse. You must also free anchoring(s) from other objects that are tied to floating object if you want just move that one floating object.

But be aware that in complex window you have lot of work if you change position of one item. You maybe have to move several others too if they are not anchored together.
Even a small few pixel difference may show out ugly at runtime.

Fortunately there are blue lines when you move floating items slowly with mouse. When item is hitting another item horizontally or vertically a blue line will appear to show that they are equal positioned.

edtState and edtDok are positioned to same coordinates. Depending on callsign either one becomes hidden/visible (DL -> dok, others ->state)
Hiding can also be switched by clicking the lblState/lblDok. So if you move one you must move the other same amount.