Info (/usr/bin/info) is crashing (SIGABRT)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
texinfo (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
====
My system:
~$ lsb_release -rd
Description: Ubuntu 20.04.4 LTS
Release: 20.04
~$ apt-cache policy info
info:
Instalado: 6.7.0.dfsg.2-5
Candidato: 6.7.0.dfsg.2-5
Tabela de versão:
*** 6.7.0.dfsg.2-5 500
500 http://
100 /var/lib/
====
The application Info (/usr/bin/info) crashes with SIGABRT on startup running in terminal.
To replicate I need just to run:
$ info
Abortado (imagem do núcleo gravada)
$
My computer is in pt_BR. Translating the message: Aborted (core image recorded/saved)
====
This happens in a terminal under X or on native text terminal.
It behaves a bit differently if you redirect output with a pipe:
$ info | less
====
I hope this information help.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: info 6.7.0.dfsg.2-5
ProcVersionSign
Uname: Linux 5.4.0-104-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
Date: Fri Mar 11 14:55:59 2022
InstallationDate: Installed on 2018-05-21 (1389 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
LANGUAGE=
TERM=xterm-
PATH=(custom, no user)
LANG=pt_BR.UTF-8
SHELL=/bin/bash
SourcePackage: texinfo
UpgradeStatus: Upgraded to focal on 2021-09-16 (175 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https:/ /errors. ubuntu. com/user/ ID where ID is the content of file /var/lib/ whoopsie/ whoopsie- id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.
3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.
Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.