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
- 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*
My history shows: compilation of quickshell, breakpad, cli11
Thank you for reading, and for your time.
