cling::DynamicLibraryManager::loadLibrary(): libGpad.so.6.28

[juivhi019]

ROOT Version: 6.32.04
Platform: Ubuntu 22.04.5
Compiler: gcc 11.4.0

---

Hi.

I am trying to reinstall ROOT. However, when I start ROOT, I get the following message.

cling::DynamicLibraryManager::loadLibrary(): libGpad.so.6.28: cannot open shared object file: No such file or directory
cling::DynamicLibraryManager::loadLibrary(): libGpad.so.6.28: cannot open shared object file: No such file or directory
root [0] 

What do I need to correct? Any help would be greatly appreciated.

[mczurylo]

Hi @juivhi019,

so what exactly are you doing, are you building root from source?

Cheers,
Marta

[juivhi019]

Thank you for your reply.
Yes. After removing the old ROOT, the following steps have been taken to reinstall it. The source has been downloaded.

tar -xzvf root_v6.32.04.Linux-ubuntu22.04-x86_64-gcc11.4.tar.gz
source root/bin/thisroot.sh

When I run ROOT after this.

cling::DynamicLibraryManager::loadLibrary(): libGpad.so.6.28: cannot open shared object file: No such file or directory

This message is displayed.

[mczurylo]

Hi @juivhi019,

okay, it looks like you are missing some dependencies - you can check them here: Dependencies - ROOT

Cheers,
Marta

[ferhue]

This is weird, you are downloading root 6.32, but then the message is about root 6.28

Did you remove the system-wide root installation before this?

[juivhi019]

These packages are already installed, including optional ones.

I think root 6.28 is the version that was used before.
I deleted the previous root directory using the rm -rf command. Might this not be enough?

[ferhue]

@juivhi019

libGpad.so.6.28

If you get this 6.28 in the error message, it means that somehow it’s still picking up an old ROOT installation, that was only partially removed. Try apt remove root-framework and snap uninstall root or things like that. Also “which root” or “whereis root” can give you an idea.

[juivhi019]

I was using a program that runs on ROOT, which I had installed in an older version. After reinstalling the program, the error disappeared. It seems that some environmental variables from the old installation may have persisted.

I really appreciate your help.