Hi, On 2023-07-07 19:22, Raúl Sánchez Siles wrote: > Hello: > > I also came accross this and I had hard time to find out how to unlock the > system. Fortunately I didn't have to reboot or suspend it and I have a > couple of yakuake tabs opened so I could try several this. The command that > lead me here was an `apt update && apt full-upgrade` I'm attaching the apt > log (1040452_install_log.txt) that eventually lead to a almost unusable > system ( even ls core dumped, attached backtrace 1040452_ls_backtrace.txt) > > In this broken state setting LC_ALL=C allowed all commands to work. > > In order to unbreak the system I had to do the following: > > ``` > cd /var/cache/apt/archives > LC_ALL=C sudo apt reinstall ./locales_2.37-3_all.deb ./ > libc6_2.37-3_amd64.deb ./libc6_2.37-3_i386.deb ./libc6-dbg_2.37-3_amd64.deb > ./libc6-dev_2.37-3_amd64.deb ./libc6-i386_2.37-3_amd64.deb ./libc-dev- > bin_2.37-3_amd64.deb ./libc6-dev-i386_2.37-3_amd64.deb ./libc6-dev- > x32_2.37-3_amd64.deb ./libc6-x32_2.37-3_amd64.deb > ``` > After this I could perform a regular `apt update && apt full-upgrade` Thanks for all the details, that helped to find the issue. It appears that the issue is not linked to the new upstream version, but has been added by the parallelization of the locale-gen code, introduced in glibc 2.37-2. It sometimes generate correupted locale-archive file depending on the number of locales generated and the number of CPU available, plus some randomness. This will be reverted in the next upload. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://aurel32.net
Attachment:
signature.asc
Description: PGP signature