ldconfig fails

AntoineLaLune

Please do not read my post as it contains a lot of nonsense. Instead, read this, where I have corrected myself: https://discuss.getsol.us/d/11949-ldconfig-fails/3

I wanted to compile and install quickshell for niri, but unfortunately I broke all my DEs (Budgie as well as Niri). I eventually managed to repair them by reinstalling mesalib, by using AI.
The problem is, running sudo ldconfig breaks my DEs again. I don’t know what this command actually does, but when I run readelf -Ws /usr/lib64/libgbm.so.1 | grep gbm_bo_write after ldconfig, the “gbm_bo_write” entry disappears from the output.
Since I couldn’t fix the problem, I decided to ignore it.
That was a mistake, because now one of my Flatpak apps refuses to launch and shows this error in the terminal:
bwrap: Can't mkdir /app/lib/ffmpeg: Read-only file system
error: ldconfig failed, exit status 256.

Please don’t refuse to help me just because I used AI. I will understand your remarks about that. It was a mistake on my part to use it originally to compile code, and next time I will just come ask directly. The problem is that I really hate bothering people, because it stresses me out, like it does here.

I’ll carefully read and consider any advice you give me, and don’t hesitate to ask me for any additional information you need.
Finally, I am very bad at writing texts in English, so it is normal if the text seems strange because of using a translator. However, I will have no problem reading your replies.

Here is a short summary that the AI had given me in the past, useful in case I was not clear enough, and I apologize if that is the case:

Budgie and Niri crash because they expect ~~gbm_bo_write~~ mesalib
The mesalib I have (25.2.2) is recent enough and should normally provide this symbol
After reinstalling Mesa -> gbm_bo_write is visible
After running ldconfig -> it disappears
- I don’t have anything in /usr/local/lib* useless
~~My history shows: compilation of quickshell, breakpad, cli11~~ useless

Thank you for reading, and for your time.

brent

 ldconfig --help
Usage: ldconfig [OPTION...]
**Configure Dynamic Linker Run Time Bindings.**

  -c, --format=FORMAT        Format to use: new (default), old, or compat
  -C CACHE                   Use CACHE as cache file
  -f CONF                    Use CONF as configuration file
  -i, --ignore-aux-cache     Ignore auxiliary cache file
  -l                         Manually link individual libraries.
  -n                         Only process directories specified on the command
                             line.  Don't build cache.
  -N                         Don't build cache
  -p, --print-cache          Print cache
  -r ROOT                    Change to and use ROOT as root directory
  -v, --verbose              Generate verbose messages
  -X                         Don't update symbolic links
  -?, --help                 Give this help list
      --usage                Give a short usage message
  -V, --version              Print program version

Yikes that looks like a scary command. Running this is a requirement of Niri?

AntoineLaLune Please don’t refuse to help me just because I used AI. I will understand your remarks about that.

I only listen to humans and read human-written answers, it would never occur to me to ask a machine anything. Ever. For anything. We're not the same--I go outside, breath air, buy crappy Belkin usb ports at Goodwill, drive on dirt roads. The machine will never do these things. It's not a peer. Not a judgement thing it's a trust thing.

sudokit

I had the exact same issue after running sudo ldconfig. If anyone else has this problem, running eopkg it --reinstall mesalib worked for me.

AntoineLaLune

After quite a bit of troubleshooting through web searches, reviewing what the AI had shared with me in the past, and verifying some ideas I had, I realize I need to correct much of what I initially said.

First, the issue with ldconfig breaking my DEs does not come from compiling and installing quickshell. I don’t even think I successfully installed quickshell. The problem actually comes from minigbm, which was installed via Steam. ldconfig selects minigbm, which breaks mesalib, mesalib-32bit, and curl-gnutls-32bit (as confirmed by sudo eopkg check), and consequently, my DEs after a restart of lightdm or my PC.

My symlinks change from:

/usr/lib64/libgbm.so -> libgbm.so.1
/usr/lib64/libgbm.so.1 -> libgbm.so.1.0.0
/usr/lib64/libgbm.so.1.0.0
/usr/lib32/libgbm.so.1 -> libgbm.so.1.0.0
/usr/lib32/libgbm.so.1.0.0

to:

/usr/lib64/libgbm.so -> libgbm.so.1
/usr/lib64/libgbm.so.1 -> libminigbm.so.1.0.0.disabled
/usr/lib64/libgbm.so.1.0.0
/usr/lib32/libgbm.so.1 -> libminigbm.so.1.0.0
/usr/lib32/libgbm.so.1.0.0

after running ldconfig.

The solution is to reinstall mesalib, as I mentioned at the beginning of my post, and as sudokit also mentioned. This restores the symlinks to their original state, allowing me to access my DEs again. I also recommend properly reinstalling mesalib-32bit and curl-gnutls-32bit with the following command:

eopkg it --reinstall mesalib mesalib-32bit curl-gnutls-32bit

At first, I thought my issue wasn’t fully resolved by reinstalling mesalib, since a Flatpak app refused to work and mentioned ldconfig in its logs. But I was wrong, because it was just the Flatpak. After checking the GitHub repository issues of the application, I found a recent issue (created a week ago) addressing this exact problem, with many users reporting it after an update. From now on, for any Flatpak related issues, I will check or open an issue elsewhere, such as on GitHub, instead of posting here, because I realized that Flatpak issues have nothing to do with Solus.

I also thought my DEs were broken by my attempt to compile and install quickshell, but in reality, I had just run ldconfig while working on it. The DE issues only appeared after rebooting my PC, and they were caused by minigbm, which was installed via Steam and selected by ldconfig, overriding mesalib.

To verify this behavior, I used a VM where I ran ldconfig and then rebooted. Everything worked normally. Then, I installed Steam as an example of a program that includes minigbm, but this would apply to any program that bundles minigbm. I ran ldconfig again, and after rebooting, the DE was broken.

Now, I should have nothing to worry about, but anyone with minigbm who runs ldconfig will have a very bad time. And I’m still very curious about why ldconfig prioritizes minigbm and how to prevent this from happening.

I hope I haven’t forgotten anything. I’ll leave this thread open for a while to see if anyone has an explanation for this behavior.

AntoineLaLune

brent Yikes that looks like a scary command. Running this is a requirement of Niri?

No, I don't think so for Quickshell either.

brent I only listen to humans and read human-written answers, it would never occur to me to ask a machine anything. Ever. For anything. We're not the same--I go outside, breath air, buy crappy Belkin usb ports at Goodwill, drive on dirt roads. The machine will never do these things. It's not a peer. Not a judgement thing it's a trust thing.

I always prioritize listening to real people on support forums, but if I can't find what I'm looking for, asking others scares me enough to ask an AI instead. I intend to change this behavior, but unfortunately, it's not that simple.

AlphaElwedritsch

brent I go outside, breath air, buy crappy Belkin usb ports at Goodwill,

😂👍

brent

AntoineLaLune I always prioritize listening to real people on support forums, but if I can't find what I'm looking for, asking others scares me enough to ask an AI instead. I intend to change this behavior, but unfortunately, it's not that simple.

I understand what you need to do. Many likely feel the same as you. It's good to have a Plan B if Plan A gets a little uneasy-going. My reply was a generational one to be sure.

Axios

My brain flips out like that now and then after I get home and my ideas dont work i say why the hell
did I buy that or need that.
I dunno a male thing...LOL
I just shrug and go on..

TraceyC

[⚠ Moderator Warning]
Please keep Support topics on-topic.

The purpose of the Support topic is to ask for and get support for specific issues. Given the warning in the first post not to read it, and the fact that this has meandered into off topic discussion, I'm moving it out of Support.

AntoineLaLune

TraceyC

I thought I was doing the right thing by adding a warning, so people wouldn’t waste time reading incorrect parts of my post, since my second message is more accurate. But I understand it made the thread confusing.

Would it be better if I reproduce the issue in a VM (with another DE or even another distro) and then open a new, clearer thread with a title like “ldconfig breaks mesalib with minigbm,” if it's only related to Solus?

My problem seems to be only partially solved: running ldconfig brings it back, and since this behavior seems to be able to break any DE, I think it’s important to investigate rather than ignore it as it is.