HI!
There could be many reasons that are hard to specify with so little amount of information.

If you compare preferences/TRXcontrol with your friend are they both similar? Take a very careful look with all columns and checkboxes. Double check everything!
If "run rigctld at program start" is checked you should see Runrigctld = true when running with "--debug=1"

If rigctld does not start there are mainly two reasons.
First one is that "path to rigctld binary" is wrong. in this case you should see a warning splash that rigctld is not found every time you open preferences/TRXcontrol.
If that does not happen the path should be correct and rigctld binary can be found.

Second reason is that the port setting of rigctld is already in use. That means that rigctld is already started.
You can check this from terminal with command:
ps ax | grep rig
That should show if there is any rigctld already running.

[saku@hamtpad ~]$ ps ax | grep rig
7147 ? Sl 0:00 /usr/local/bin/rigctld -m 3073 -r /dev/ttyUSB0 -t 4532 -s 19200 -C auto_power_on=1
7382 pts/0 S+ 0:00 grep --color=auto rig
[saku@hamtpad ~]$

You say wsjtx and js8call works. They have built in rigctld and use different version of rigctld called rigctld-wsjtx.
fldigi has it's own way to communicate with rig's CAT without rigctld.

Either of these reasons do not produce "Runrigctld = false" to Cqrlog debug. It must come from Cqrlog settings.

Please note that you can not run Cqrlog together with those other programs fldigi wsjtx js8call by setting 101mp as rig for all settings.
It causes chaos on CAT line. Linux does not care is several programs are accessing same serial device unlike WIndows. User must control this by himself.
Running together needs special arrangement. Please read this pdf:
https://github.com/OH1KH/CqrlogImproved/blob/main/compiled/setting_rigct...

Getting forward with this case needs a bit more information. If you start Cqrlog from terminal with "--debug=1" you find this kind of part at the beginning of debug text:

Settings:
-----------------------------------------------------
RigCtldPath:/usr/local/bin/rigctld
RigCtldArgs:-m 3073 -r /dev/ttyUSB0 -t 4532 -s 19200
RunRigCtld: TRUE
RigDevice: /dev/ttyUSB0
RigCtldPort:4532
RigCtldHost:localhost
RigPoll: 500
RigSendCWR: FALSE
RigChkVfo TRUE
RigId: 3073

Starting RigCtld ...
rigProcess.Executable: /usr/local/bin/rigctld
Parameters:
-m
3073
-r
/dev/ttyUSB0
-t
4532
-s
19200
-C
auto_power_on=1

rigctld started!
Waiting for rigctld Poll 1 @ localhost:4532
Connecting to rigctld Poll (OnConnect)

If you are using official version of Cqrlog the debug text may look a bit different than this example from Cqrlog_Improved's debug with Icom7300 rig.

Anyway the main settings should be there. That would be interesting to see what can be seen from that.