Bug in terminal

[Jhon_Herbert (Herbert)]

Hey there!

I’ve freshly installed Parrot Os Version 6 and I’ve noticed a bug in the terminal when login as root.

I see this shell prompt message.

Any idea? I can make changes for it though, but urgh not sure.

[Masmer (Masmer Snerd)]

Hi @Jhon_Herbert

This is a known issue. I’m not sure if the problem has been rectified by the developers yet, but there is a fix…

[SOLVED] Strange terminal output on launch

– Please Write here your help request, – Hello- Ever since an update ~a month ago (during one of the last parrot 5.x updates), I started getting strange output on my terminal. This never occured prior to the update, and I did not make any changes to ~/.bashrc that didn’t exist before the update when everything was fine. I did notice there was an update that did replace /etc/bash.bashrc but I can’t match the terminal output to anything in that file either. So, I’m stumped. I cannot for the life of me figure out what file is being sourced to generate this ouput. Basically I get this when opening a terminal or running the “bash” command: \]\342\224\214\342\224\200\$([[ \$? != 0 ]] && echo \"[\[\]\342\234\227\[\]]\342\224\200\")[$(if [[ ${EUID} == 0 ]]; then echo '\[\]root\[\]@\[\]\h'; else echo '\[\]\u\[\]@\[\]\h'; fi)\[\]]\342\224\200[\[\]\w\[\]] \[\]\342\224\224\342\224\200\342\224\200\342\225\274 \[\]\[\]\$\[\]" - Parrot Terminal\]\342\224\214\342\224\200\$([[ \$? != 0 ]] && echo \"[\[\]\342\234\227\[\]]\342\224\200\")[$(if [[ ${EUID} == 0 ]]; then echo '\[\]root\[\]@\[\]\h'; else echo '\[\]\u\[\]@\[\]\h'; fi)\[\]]\342\224\200[\[\]\w\[\]] \[\]\342\224\224\342\224\200\342\224\200\342\225\274 \[\]\[\]\$\[\]" - Parrot Terminal┌─[happyoutkast@parrot]─[~] └──╼ $ It also makes the same noise that I get when I make an invalid keypress. I’m also having an issue changing the hostname (which is why it’s still "parrot), but that’s an issue for another post. I tried searching that text in both ~/.bashrc and /etc/bash.bashrc but can’t find any results and a manual check of the file doesn’t yield anything that I can find that would generate this ouput. The contents of my ~/.bashrc: # ~/.bashrc: executed by bash(1) for non-login shells. # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) # for examples # If not running interactively, don't do anything case $- in *i*) ;; *) return;; esac # added by user, this is to make sure that all new files created have secure # permissions set by default. umask 027 # added a function to dynamically set the title of new terminal windows based # upon the currently running command (hopefully). This way terminal tabs have unique names. # just run set-title at the command prompt... function set-title() { if [[ -z "$ORIG" ]]; then ORIG=$PS1 fi TITLE="\[\e]2;$@\a\]" PS1=${ORIG}${TITLE} } # on with the "default" stuff, below defines the PATH variable. export PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/share/games:/usr/local/sbin:/usr/sbin:/sbin:~/.local/bin:/snap/bin:~/bin:$PATH # don't put duplicate lines or lines starting with space in the history. # See bash(1) for more options HISTCONTROL=ignoreboth # append to the history file, don't overwrite it shopt -s histappend # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) HISTSIZE=1000 HISTFILESIZE=2000 # check the window size after each command and, if necessary, # update the values of LINES and COLUMNS. shopt -s checkwinsize # If set, the pattern "**" used in a pathname expansion context will # match all files and zero or more directories and subdirectories. #shopt -s globstar # make less more friendly for non-text input files, see lesspipe(1) #[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)" # set variable identifying the chroot you work in (used in the prompt below) if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then debian_chroot=$(cat /etc/debian_chroot) fi # set a fancy prompt (non-color, unless we know we "want" color) case "$TERM" in xterm-color) color_prompt=yes;; esac # uncomment for a colored prompt, if the terminal has the capability; turned # off by default to not distract the user: the focus in a terminal window # should be on the output of commands, not on the prompt force_color_prompt=yes # it does make things easier to see when working with code though.... if [ -n "$force_color_prompt" ]; then if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then # We have color support; assume it's compliant with Ecma-48 # (ISO/IEC-6429). (Lack of such support is extremely rare, and such # a case would tend to support setf rather than setaf.) color_prompt=yes else color_prompt= fi fi if [ "$color_prompt" = yes ]; then PS1="\[\033[0;31m\]\342\224\214\342\224\200\$([[ \$? != 0 ]] && echo \"[\[\033[0;31m\]\342\234\227\[\033[0;37m\]]\342\224\200\")[$(if [[ ${EUID} == 0 ]]; then echo '\[\033[01;31m\]root\[\033[01;33m\]@\[\033[01;96m\]\h'; else echo '\[\033[0;39m\]\u\[\033[01;33m\]@\[\033[01;96m\]\h'; fi)\[\033[0;31m\]]\342\224\200[\[\033[0;32m\]\w\[\033[0;31m\]]\n\[\033[0;31m\]\342\224\224\342\224\200\342\224\200\342\225\274 \[\033[0m\]\[\e[01;33m\]\\$\[\e[0m\]" else PS1='┌──[\u@\h]─[\w]\n└──╼ \$ ' fi # Set 'man' colors if [ "$color_prompt" = yes ]; then man() { env \ LESS_TERMCAP_mb=$'\e[01;31m' \ LESS_TERMCAP_md=$'\e[01;31m' \ LESS_TERMCAP_me=$'\e[0m' \ …

[Jhon_Herbert (Herbert)]

Thank you very much