locale-gen crashed with SIGABRT in __GI___wait4()

[Guillem Solivellas]

Install of ubuntu 23.10 stopped

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: locales 2.38-1ubuntu6
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
Date: Sat Apr 13 08:52:13 2024
ExecutablePath: /usr/sbin/locale-gen
InterpreterPath: /usr/bin/bash
JournalErrors:
 Apr 13 08:52:03 hostname kernel: evict_inodes inode 0000000087b0f7b8, i_count = 1, was skipped!
 Apr 13 08:52:03 hostname kernel: evict_inodes inode 000000008b4af7a5, i_count = 1, was skipped!
 Apr 13 08:52:03 hostname kernel: evict_inodes inode 000000004f04ff72, i_count = 1, was skipped!
 Apr 13 08:52:03 hostname kernel: evict_inodes inode 000000008ea7216b, i_count = 1, was skipped!
 Apr 13 08:52:12 hostname systemd[1]: systemd-localed.service: Watchdog timeout (limit 3min)!
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
PackageArchitecture: all
ProcCmdline: /bin/bash /usr/sbin/locale-gen
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
RebootRequiredPkgs: Error: path contained symlinks.
Signal: 6
SourcePackage: glibc
StacktraceTop:
 __GI___wait4 (pid=-1, stat_loc=0x7ffee4c5b3b0, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:30
 ?? ()
 wait_for ()
 execute_command_internal ()
 ?? ()
Title: locale-gen crashed with SIGABRT in __GI___wait4()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:

[Olivier Gayot (ogayot)]

Adding glibc since it's locale-gen crash.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2054193, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.