Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

version `GLIBC_2.36' not found #203

Open
davorg opened this issue Jul 3, 2023 · 4 comments
Open

version `GLIBC_2.36' not found #203

davorg opened this issue Jul 3, 2023 · 4 comments

Comments

@davorg
Copy link

davorg commented Jul 3, 2023

I've just upgraded from version 36 to version 38, following the instructions in this blog post. I've restarted WSL, but every time I open a Fedora Remix terminal, I get these errors:

/usr/bin/dbus-daemon: /lib64/libc.so.6: version `GLIBC_2.36' not found (required by /lib64/libexpat.so.1)
EOF in dbus-launch reading address from bus daemon
flatpak: /lib64/libc.so.6: version `GLIBC_2.36' not found (required by /lib64/libarchive.so.13)
flatpak: /lib64/libc.so.6: version `GLIBC_2.36' not found (required by /lib64/libcurl.so.4)
flatpak: /lib64/libc.so.6: version `GLIBC_2.36' not found (required by /lib64/libevent-2.1.so.7)

Also, when trying to run sudo dnf update, I see:

sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy"
sudo: unable to load /usr/libexec/sudo/sudoers.so: /lib64/libc.so.6: version `GLIBC_2.36' not found (required by /lib64/libevent-2.1.so.7)
sudo: fatal error, unable to load plugins

rpm tells me I still have glibc 2.35 installed.

$ rpm -qa | grep glibc
glibc-gconv-extra-2.35-22.fc36.x86_64
glibc-langpack-en-2.35-22.fc36.x86_64
glibc-2.35-22.fc36.x86_64
glibc-common-2.35-22.fc36.x86_64
glibc-minimal-langpack-2.35-22.fc36.x86_64
glibc-headers-x86-2.35-22.fc36.noarch
glibc-devel-2.35-22.fc36.x86_64
@davorg
Copy link
Author

davorg commented Jul 3, 2023

I'm trying to use su as an alternative to sudo, but I realise I have no idea what the default root password is.

@davorg
Copy link
Author

davorg commented Jul 3, 2023

Something really didn't go right here.

$ rpm -qa | grep fc36 | wc -l
2127
$ rpm -qa | grep fc38 | wc -l
0

@crramirez
Copy link
Contributor

Hello @davorg ,

You can login as root using wsl -d fedoraremix -u root

Then try to upgrade to Fedora 37 first.

Be sure that systemd is disabled before doing the upgrade.

By any chance you did a backup before starting the upgrade? If so it is better to restore the backup and start again.

Regards,
Carlos

@davorg
Copy link
Author

davorg commented Jul 3, 2023

Thanks for trying to help.

You can login as root using wsl -d fedoraremix -u root

Yeah. I found that. Thanks.

Then try to upgrade to Fedora 37 first.

I really can't do much, even when I'm logged in as root - as the system still thinks it needs to use glibc 2.36 and that's not available. Even running upgrade.sh fails (because it uses sudo which needs glibc).

Be sure that systemd is disabled before doing the upgrade.

I don't think I ever enabled systemd - but I certainly ran the command to disable it before starting the upgrade.

By any chance you did a backup before starting the upgrade? If so it is better to restore the backup and start again.

Yes, I'm an idiot. There's no backup. I've been upgrading this installation since Fedora Remix first appeared. It's always worked before, so I got cocky. Lesson learned.

As I see it, I have a couple of options:

  • I can somehow edit the config of my installation so it knows to use glibc 2.35. And then restart the upgrade.
  • I can try to reinstall Fedora Remix from the MS Store and take it from there. I'm currently backing up my user files, in order to make that easier.

So if anyone can suggest how I do either of those things, I'd love to hear it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants