http://bugzilla.suse.com/show_bug.cgi?id=1143060 Bug ID: 1143060 Summary: No colors shown for ls in screen (dircolors gives no output when called from /etc/profile.d/ls.bash) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: doerges@pre-sense.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Inside a screen session ls doesn't show colors for the entries by default anymore. Everything is working as expected in Leap 15.0 (with or without screen). In Leap 15.1 only the setup without screen is working. The following applies to: user@box:~> lsb-release -d Description: openSUSE Leap 15.1 No screen (everything is fine): --- snip --- user@box:~> echo $TERM xterm-256color user@box:~> echo "Value of LS_COLORS: '$LS_COLORS'" Value of LS_COLORS: 'no=00:...' user@box:~> echo $LS_OPTIONS -N --color=tty -T 0 -F user@box:~> dircolors LS_COLORS='rs=0:di=01;34:...'; export LS_COLORS --- snip --- Inside screen (note the empty LS_COLORS, and consequently the '--color=none' in LS_OPTIONS): --- snip --- user@box:~> echo $TERM screen.xterm-256color user@box:~> echo "Value of LS_COLORS: '$LS_COLORS'" Value of LS_COLORS: '' user@box:~> echo $LS_OPTIONS -N --color=none -T 0 -F user@box:~> dircolors LS_COLORS='rs=0:di=01;34:...'; export LS_COLORS --- snip --- What really puzzles me if I do a bit of debugging in /etc/profile.d/ls.bash, where apparently LS_COLORS and LS_OPTIONS are set. If I insert a little debug code in /etc/profile.d/ls.bash: --- snip --- echo DEBUG-BEGIN echo $TERM set -x if test -x /usr/bin/dircolors ; then # # set up the color-ls environment variables: # if test -f $HOME/.dir_colors ; then eval "`/usr/bin/dircolors -b $HOME/.dir_colors`" elif test -f /etc/DIR_COLORS ; then eval "`/usr/bin/dircolors -b /etc/DIR_COLORS`" fi fi set +x echo DEBUG-END --- snip --- starting a screen session gives me: --- snip --- DEBUG-BEGIN screen.xterm-256color ++ test -x /usr/bin/dircolors ++ test -f /home/td/.dir_colors ++ test -f /etc/DIR_COLORS +++ /usr/bin/dircolors -b /etc/DIR_COLORS ++ eval 'LS_COLORS='\'''\''; export LS_COLORS' +++ LS_COLORS= +++ export LS_COLORS ++ set +x DEBUG-END --- snip --- but if in that very same screen session I call dircolors from the command line, I get --- snip --- td@atlan:~> dircolors LS_COLORS='rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35 :*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:'; export LS_COLORS --- snip --- -- You are receiving this mail because: You are on the CC list for the bug.