Sudo su problem in new Parrot 6

[rh3nt0n (Felix)]

In the new version of Parrot Os when doing:
sudo su

responds with an error

• Parrot version in use (if you are not aware of it, open terminal and type cat /etc/os-release | grep VERSION):
  $cat /etc/os-release | grep VERSION
  VERSION_ID=“6.0”
  VERSION=“6.0 (lorikeet)”
  VERSION_CODENAME=lory

• Kernel version (if you are not aware of it, open terminal and type uname -r):
  $uname -a
  Linux parrot 6.5.0-13parrot1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.13-1parrot1 (2023-12-19) x86_64 GNU/Linux

“Solution”
(while the problem is solved with a patch or revision)

• Screenshots:
  The error:
  
  
  
  Comment the following lines in root’s .bashrc (with #):
  
  

[Masmer (Masmer Snerd)]

Hi @rh3nt0n

It appears this is a recurring bug (reported by @happyoutkast), and I have experienced it myself. Hopefully, a developer or Linux guru will assist.

[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' \ …

(I fixed hostname resolution after posting.)

[rh3nt0n (Felix)]

@Masmer

(I fixed hostname resolution after posting.)

Hello, how did you solve it?

As I read in the query you have cited, do they comment on the lines giving more importance to correct output in the terminal to the output format?
is that so?
thank you

[Masmer (Masmer Snerd)]

The hostname resolution was a separate issue. I think the Calamares installer may not have set the hostname I chose during installation. In case a developer reads this post, I wanted to make sure they knew that this issue we are experiencing is not due to hostname issues, and reproducible.

┌─[masmer@cracker]─[~]
└──╼ $sudo su
\]\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┌─[root@cracker]─[/home/masmer]
└──╼ #

[rh3nt0n (Felix)]

@Masmer

The hostname resolution was a separate issue. I think the Calamares installer may not have set the hostname I chose during installation. In case a developer reads this post, I wanted to make sure they knew that this issue we are experiencing is not due to hostname issues, and reproducible.

I think it is simply a problem with the formatting function of that output, something aesthetic that is solved by commenting on the lines I put in the screenshot of the first post.
I understand that it is not the best solution, but the annoying output disappears.
Sorry if I don’t understand well what you posted, I’m a Spanish speaker.

Icono de Validado por la comunidad

[Masmer (Masmer Snerd)]

Yes, something is wrong with the formatting (syntax) in .bashrc.

[dmknght (Nông Hoàng Tú)]

Line 60 and Line 69 are broken. The current syntax makes it very hard to debug and fix. But i accidently found a way to make prompt be flash like LED lol

[Masmer (Masmer Snerd)]

Stop doing that!

[dmknght (Nông Hoàng Tú)]

OH that looks funny lmao. BTW after like an hour debugging, here’s my result: the first character \033 (or \e in short) made the error. IDK why and how. It’s likely not from prompt but something else. It’s possibly from bash or other config file.
I tested with some bashrc files. I tested many other cases that has color escape. That’s everything i see. I’m trying to have a solution.

[dmknght (Nông Hoàng Tú)]

Very simple test case.

[rh3nt0n (Felix)]

After looking more closely it seems the simplest solution is not to touch the .bashrc file since there is no problem and just comment out the last line of the bash.bashrc file:

trap 'echo -ne "\033]0;$BASH_COMMAND - Parrot Terminal\007" > /dev/stderr' DEBUG

This situation was already resolved in the previous version of Parrot which occurred after an update (it doesn’t happen to me) I was unaware of this circumstance

[SOLVED] Strange terminal output on launch

I found the error. In the file /etc/bash.bashrc they added a new line at the end of the file which is causing the issue. It is literally the last line in the file: trap 'echo -ne "\033]0;$BASH_COMMAND - Parrot Terminal\007" > /dev/stderr' DEBUG The above line needs to be deleted or commented out in order to correct the problem. I don’t know why they added this line since all it seems to do is break things. I can’t see any purpose for it and maybe it needs to be defined a bit better (comments about what each section does are really key here). Either way, that part of the script is definitely broken. Thankfully I was able to narrow down the issue after evaluating the files in the meld program (gui version of diff).

The truth is that it looks ugly when you finish installing your new parrot and the terminal gives you such ugly lines when you root… but hey, it is something that is easily solved, fortunately.

I also find the warnings that appear when doing sudo apt update ugly, but that is even easier to solve!
Saludos!