When I start CLI, the prompt will appear normal but soon turns into some sort of unicode looking character stream. Inputs are also displayed as unicode and do not execute. Only Ctrl-c seems to work, and only on one of two computers. Here is an example: Asterisk 13.9.1, Copyright © 1999 - 2014, Digi…

I’m using Linux alarm 3.14.65-16-ARCH on arm. i’m kinda glad to know it isn’t due to the arm environment… :wink: You say it happened after a kernel update? Did you have to rebuild asterisk or just did it happen just after rebooting? I tried to play with the locale/language/input environment parame…

[image] v345: You say it happened after a kernel update? Did you have to rebuild asterisk or just did it happen just after rebooting? Probably not a kernel update, that’s something that is different between the two of us, but probably the update of some other component. It literally happened …

Well i got an old image (± 1 month old), rebuild asterisk 13 lts, and the cli is just fine. I’ll try to make small updates and see which one breaks it…

Well if the bug comes from a single package, it’s one of these… I ran an update on a batch, didn’t really expect any of them to be the culprit (except systemd maybe…) But after i ran the update, without even rebooting or restarting asterisk, the bug appears… Packages (17) libarchive-3.2.1-2 libass…

I would hazard a guess that it’s libedit. In the CHANGES file for Asterisk: Asterisk can now use a system-provided NetBSD editline library (libedit) if it is available.

[image] v345: Packages (17) … libedit-20160618_3.1-1 … Nice work! My bet is libedit: Editline Library (libedit) - Port of NetBSD Command Line Editor Library Editline Library (libedit) - Port of NetBSD Command Line Editor Library Stephen

Right on target :slight_smile: I reverted back to an old image and updated everything but libedit, and the cli is fine. Just for the sake of completeness: Works: libedit 20150325_3.1-2 Glitches: libedit-20160618_3.1-1 Not sure if the bug is in asterisk or libedit, but libedit might stay out of …

Nice work! I’m thinking that the only reason that this is just affecting us, is that Arch is probably one of the few installs that is using libedit. Stephen

Hi guys, I’m having the same issue with alarm. Is there an easy way to fix this problem? Which version of Asterisk does the problem first appear in? Or is the problem just with libedit? Is there a way i can rollback libedit on alarm? Thanks, Luke

Hi Luke, there are two ways to fix the problem: downgrade libedit to the version described in Vincent’s post of July 27th: get the tar.xz from somewhere (maybe your package cache?: /var/cache/pacman/pkg/), invoke pacman -U on the package file, that should downgrade it. CLI should be working again…

CLI gibberish -- prompt and input appear to be some sort of unicode characters

Asterisk Asterisk Support

FixedWing July 27, 2016, 12:09am 15

Nice work!

My bet is libedit:

Stephen

Topic		Replies	Views
Asterisk CLI disfunction Asterisk Support	6	622	April 12, 2020
Asterisk cli Unicode error Asterisk Support	8	304	March 24, 2023
Change CLI prompt Asterisk Support	1	245	February 1, 2006
Console output garbled / scrambled Asterisk Support	3	408	April 23, 2018
Asterisk 16 piped "-rx" breaks shell Asterisk Support	16	1242	November 12, 2018

CLI gibberish -- prompt and input appear to be some sort of unicode characters

Related topics