My PopOS is totally fucked. Audio is fucked because of some problem with systemd and I can't upgrade shit to try to fix it.

This is the dumbest shit. I hate apt so much. Never fails to produce issues.

My crime? Trying to install GLIBC 2.38? Is that such a crime??

#PopOs #Linux

@cleverboi
Boi, I'm not knowledgeable about glibc, but I do use and like Pop!_Os, so I'm boosting your twt in an effort to secure you an answer.
I don't know your use case, so I have no clue why you'd be having this software issue with Pop!_Os!
Hope someone else can be of actual assistance.
#Linux #GLIBC #Pop!_Os #PopOs

@cleverboi you have entered... DEPENDENCY HELL

you will most likely need to downgrade glibc to the version podman expects and then remove the "manually installed" flag

https://serverfault.com/questions/87933/how-to-remove-the-installed-manually-flag-and-revert-to-automatically-install

How to remove the "installed manually" flag and revert to "automatically installed" with apt-get?

To compile something, I needed the zlib1g-dev package to be installed so I launched an apt-get install zlib1g-dev. apt-get informed me nicely that the package was already auto-installed because o...

Server Fault

@cleverboi if you were installing packages from unstable / experimental branches you should probably also read

https://wiki.debian.org/DontBreakDebian

DontBreakDebian - Debian Wiki

@fdavies93 Thanks for the response. I will try this.

I should note that at no place does apt actually refer to glibc as being part of the issue. It’s just a system package that I forcibly upgraded because of the number of Rust projects I can’t run with this hella old glibc in the PopOS repos.

I do take accountability for forcibly upgrading a low level system package and I was aware of the risk at the time of doing so, but I still blame apt for the shit-tier error messages.

@cleverboi rust programmers all using arch is a stereotype for a good reason, it seems...

you may want to take a look at histories of projects / packages to see if any are compatible with older glibc variants

@fdavies93 How dare you bring logic into this house
@fdavies93 So I tried downgrading to 2.35, because that's what dpkg logs show I had, and I somehow broke both sudo and su lol. So Pop rebooted into recovery mode and let me refresh the OS. Everything is good and I've learned absolutely nothing, I will absolutely break it again.
@cleverboi glibc is a very low level package which a lot of packages depend on. The same would happen if you try to replace python on a system level.

@ahoneybun I am aware of this, but two counterpoints.

One, I am upgrading from 2.36 to 2.38 which I would not expect to include breaking changes if it follows semvar

Two, no error message at any point has mentioned glibc. It’s just the only system package I’ve messed with that I can think of and, as you said, it is very low level.

My point being if that’s really the issue, apt does an absolutely horrible job of saying so.

@cleverboi it looks like you've told it to hold a package so it won't attempt to fix or update it. I don't know the command to I find which package or I hold it though and I'm on my phone so mega tedious to search the internet.

Boosted in case someone has the magic commands to hand, but hope you can undo whatever changes broke it :)

@CenturyAvocado I do indeed have held back packages.

It’s been a while since I’ve run a Debian/Ubuntu-based distro so the concept of “held back” is very odd to me. The internet told me they should have been approved by now, and I’ve done everything I can find to try to force update the held back packages, but it refuses to.

@cleverboi First of all: Not a crime! Let's try to fix this.
Can you give more information: How exactly did you install glibc 2.38?
@indibart I was able to resolve this by using Pop_OS's recovery lol