That is in short. You fail to explain how you “launch” bash (and we are no mind-readers ).
Also, please only copy/paste complete actions. That is starting with the prompt/command line as first, then all output and then the new prompt line.
And please use the Preformatted text feature (the button </> from the tool bar of the post editor) around such copied/pasted computer text. then maybe the silly bold text will also revert to normal.
# Sample .profile for SUSE Linux
# rewritten by Christian Steinruecken <cstein@suse.de>
#
# This file is read each time a login shell is started.
# All other interactive shells will only read .bashrc; this is particularly
# important for language settings, see below.
test -z "$PROFILEREAD" && . /etc/profile || true
# Some applications read the EDITOR variable to determine your favourite text
# editor. So uncomment the line below and enter the editor of your choice :-)
export EDITOR=/usr/bin/nvim
#export EDITOR=/usr/bin/mcedit
# For some news readers it makes sense to specify the NEWSSERVER variable here
#export NEWSSERVER=your.news.server
# Some people don't like fortune. If you uncomment the following lines,
# you will have a fortune each time you log in ;-)
#if [ -x /usr/bin/fortune ] ; then
# echo
# /usr/bin/fortune
# echo
#fi
#
Maybe you could try first to start in e.g. konsole (where you get those three errors) and then at the prompt
bash -v
that will start bash again and print all lines it gets. The problem is that it will make a long list of profile’s and bashrc’s.
I was not able to catch this in a file. So you have to scroll back up in konsole and check if you can find the error and what is above it.
The three “command not found” were concentrated at the end of the bash -v output result. The last 21 lines of the output result are shown below.
# End of /etc/bash.bashrc
#
# Sample .bashrc for SUSE Linux
# Copyright (c) SUSE Software Solutions Germany GmbH
echo $"$1: command not found" >&2
: command not found
# There are 3 different types of shells in bash: the login shell, normal shell
# and interactive shell. Login shells read ~/.profile and interactive shells
# read ~/.bashrc; in our setup, /etc/profile sources ~/.bashrc - thus all
# settings made here will also take effect in a login shell.
#
# NOTE: It is recommended to make language settings in ~/.profile rather than
# here, since multilingual X sessions would not work properly if LANG is over-
# ridden in every subshell.
echo $"$1: command not found" >&2
: command not found
test -s ~/.alias && . ~/.alias || true
echo $"$1: command not found" >&2
: command not found
Can you test this by adding temporary a blank line, e.g. between the two lines
# Sample .bashrc for SUSE Linux
# Copyright (c) SUSE Software Solutions Germany GmbH
Then there should be four error messages.
=====
Maybe I must add that I am not using Tumbleweed, but Leap. So comparing is difficult. But the two are not very different in this area I assume. I doubt that other Tumbleweed users have the same. No reports, nor people posting here that have seen the phenomenon at their own system.
Nevertheless could you explain if you had this before, or is this a new installation, or is it after an update?
I’ll bet this is closely related or the same problem. This image is from TDE 14.1.1 Konsole freshly opened and untouched in TW20240426. The user login account is old, but it was never previous to today used to open a TDE session or TDE’s Konsole. When I resize the window, the prompt count increases until it fills the entire cmdline. An updir/downdir key sequence reduces the prompt count to one. On many instances of these anomalous MCs, attempts to run commands from the prompt fail in various ways that I have not made any attempts to keep track of.
I have many installations and users where these multiple prompts appear when Konsole is opened or reopened in TDE, KDE3 and Plasma5. It started too long ago to remember with any specificity, but I believe it’s conjoined with this bug’s timing.
.bashrc for this image’s user contains a single non-blank line that is not a comment, and 5 blank lines. The non-comment, non-blank is the last:
Thank you for your suggestion.
I also observed the behavior of midnight commander and confirmed that it exhibits exactly the same phenomenon, including during resizing.
bor@bor-Latitude-E5450:~$ LANG=C . /tmp/foo.sh
: command not found
: command not found
bor@bor-Latitude-E5450:~$ LANG=C file /tmp/foo.sh
/tmp/foo.sh: Bourne-Again shell script, ASCII text executable, with CRLF line terminators
bor@bor-Latitude-E5450:~$
).
