localedef crashed with SIGABRT in __libc_start_call_main()

Bug #2061336 reported by hatune
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
glibc (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

send repot is displayed on install

ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: libc-bin 2.39-0ubuntu8
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.496
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
Date: Mon Apr 15 09:23:34 2024
Dependencies:
 gcc-14-base 14-20240330-1ubuntu2
 libc6 2.39-0ubuntu8
 libgcc-s1 14-20240330-1ubuntu2
 libidn2-0 2.3.7-2
 libunistring5 1.1-2
ExecutablePath: /usr/bin/localedef
ExecutableTimestamp: 1711784525
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
ProcCmdline: localedef -i ru_UA -c -f UTF-8 -A /usr/share/locale/locale.alias ru_UA.UTF-8
ProcCwd: /
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
Signal: 6
SignalName: SIGABRT
SourcePackage: glibc
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 __libc_start_call_main (main=main@entry=0x56fd98422ec0, argc=argc@entry=9, argv=argv@entry=0x7fff9e8c08a8) at ../sysdeps/nptl/libc_start_call_main.h:58
 __libc_start_main_impl (main=0x56fd98422ec0, argc=9, argv=0x7fff9e8c08a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff9e8c0898) at ../csu/libc-start.c:360
Title: localedef crashed with SIGABRT in __libc_start_call_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:

Revision history for this message
hatune (nemu-asakura) wrote :
hatune (nemu-asakura)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in glibc (Ubuntu):
status: New → Confirmed
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!

Changed in glibc (Ubuntu):
status: Confirmed → Invalid
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.