Getting a subversion missing symbol error after updgrading from F40 to F42

Ask Fedora
1

fedora version : Fedora release 42 (Adams)
os version : Linux 6.14.6-300.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 9 20:11:19 UTC 2025 x86_64 GNU/Linux

Just updated my os from F40 to F42.
Getting an error when tyring to run any svn command from the command line:

svn: symbol lookup error: /lib64/libsvn_subr-1.so.0: undefined symbol: apr_crypto_block_cleanup

I see the following libraries for svn:
/usr/lib64/libsvn_subr-1.so.0.14.5
/usr/lib64/libcrypto.so.3.2.4

Any idea on how to fix this error?
(ps: svn had been working for me with every upgrade of Fedora for many releases).

tia

-Sunil

2

It sounds like the apr package wasn’t updated. What does rpm -q apr show?

3

You should have these versions:

$ dnf list installed subversion apr*
Updating and loading repositories:
Repositories loaded.
Installed packages
apr.x86_64              1.7.5-2.fc42       fedora
apr-devel.x86_64        1.7.5-2.fc42       fedora
apr-util.x86_64         1.6.3-22.fc42      fedora
apr-util-lmdb.x86_64    1.6.3-22.fc42      fedora
apr-util-openssl.x86_64 1.6.3-22.fc42      fedora
subversion.x86_64       1.14.5-14.fc42     fedora

Did you try a sudo dnf update to see if anything will be updated?

4

$ rpm -q apr
apr-1.7.5-2.fc42.x86_64

5

Yes, I had done a dnf upgrade. And the dnfagora dialog app just showed about 30+ packages that needed an update. I didnt see subversion in that list.

Installed packages
apr.x86_64 1.7.5-2.fc42 fedora
apr-devel.x86_64 1.7.5-2.fc42 fedora
apr-util.x86_64 1.6.3-22.fc42 fedora
apr-util-devel.x86_64 1.6.3-22.fc42 fedora
apr-util-lmdb.x86_64 1.6.3-22.fc42 fedora
apr-util-openssl.x86_64 1.6.3-22.fc42 fedora
subversion.x86_64 1.14.5-14.fc42 fedora

6

Ok. Sorry for that. Issue seems to have occurred after I installed log4cxx.

In addition to log4cxx, I downloaded libraries apr, apr-util and log4cxx and put them into my own directories (not /usr/lib64) just for control of the installs.
At the time, I wasnt sure if I had to do this, but install instructions state to add the installed paths to ld_library_path. Which is what I did.
This caused havoc with subversion.

I have removed appending the above library paths to ld_library_path from my .bash_profile. Now svn is working again.

I will have to only add these libraries to the ld variable in startup scripts for applications that need it.

1 Like
7

Confirmed that my log4cxx apps still compile/run and outside of that build environment, subversion (svn) continues to work as before.

Thanks all

8

Why didn’t you install log4cxx that fedora provides?