Kubuntu 23.10: BL does not open

[FuzzyExpress]

Describe the bug
Blender Launcher does not open.
When using the Ubuntu package it doesn't print anything in the console. However, it does create and empty log file:
Blender Launcher.log

I figured I should also try the Linux version; It prints error [175161] Error loading Python lib '/tmp/_MEIbIqVy0/libpython3.9.so.1.0': dlopen: libcrypt.so.2: cannot open shared object file: No such file or directory in the console. It does not make a log file.

To Reproduce
Steps to reproduce the behavior:

1. For each package download and extract it to ~/Apps.
2. Right click Copy Location.
3. Open a terminal and paste the location /home/[me]/Apps/Blender\ Launcher
4. See error, or lack of it when using the Ubuntu version.

Expected behavior
Open the GUI and show all of the builds I can go and download.

Screenshots
If applicable, add screenshots to help explain your problem.

System (please complete the following information):

• Operation system: Kubuntu 23.10 | KDE Plasma 5.27.8 | Wayland | 6.6.8-x64v3-xanmod1 Kernel.

• Blender Launcher version:
  Blender_Launcher_v1.16.1_Ubuntu_x64
  and
  Blender_Launcher_v1.16.1_Linux_x64

• Log file: The Linux Ubuntu version creates and empty log file.

Additional context
Add any other context about the problem here.
The Ubuntu version of the program shows it as running for about one second before returning to input.
Running it multiple times did not make anything show up in the log file, it is still blank.

[drdubosc]

Reproduced here, on Kubuntu: Ubuntu 20.04.06

[FuzzyExpress]

I have no idea what could have possibly changed but it works now, it successfully identified my manual install of Blender 4.0.3 RC and installed Daily 3.6.8. I can't figure out if it's the Linux or the Ubuntu version nothing in the app says that.
I'm going to leave the issue open because I don't know what changed, and it's the same version.

[juryrigging]

I was getting a similar error for v1.16.1 on Arch using the binary. Didn't look into it at the time as I had more pressing life concerns. It persisted into v2.0.24, however, only it was complaining about libcrypt.so.1. Whether it's the same root issue as Fuzzy had I don't know, especially as theirs cleared up.

[1400353] Error loading Python lib '/tmp/_MEIthc0yu/libpython3.9.so.1.0': dlopen: libcrypt.so.1: cannot open shared object file: No such file or directory

After some searching, it appears that glibc's libcrypt.so.1 was deprecated in favour of libxcrypt and has now been removed. It should be backwards binary compatible. https://github.com/besser82/libxcrypt#compatibility-notes

However, on Arch I had to install a package called libxcrypt-compat to get it working. Whether the extra package is required for other distros probably depends on the distro, perhaps the ubuntu flavours didn't need to and Fuzzy just got caught in a transition. What I don't understand is why v1.16.0 still works just fine without.

I hope this helps in some way. I think libxcrypt holds the answer, and linking against it would solve this issue without requiring users to do anything on their end?