Anybody noticed weird behavior with long commands which makes Konsole unusable, also Alacritty, Xterm

Ask Fedora
, ,
1

When long command is close to end of window weid behavior occurs which renders Konsole unusable with long commands, and, with multiple split windows almost unusable at all.

Open Konsole, write long command until to the end of window, notice if text goes in same line or is wrapped on next line.

If it is not wraped and goes in the same line then hit enter, bring back that command from history, use arrow to go to first line and then try to correct command by backspase, del or writing more text. After that command and text is mangled, parts of long command appear at the beggining of previous commands in history, no editing possible, only way out is to hit enter on somethin benign and try again.

It also happens on Alacritty and Xterm.

I tried few live ISO versions and it does not happen on Kubuntu 26.04, Debian KDE 13.5.0, Fedora MATE 43.1.6. I even doesn’t happen on Fedora KDE 43 iso but does on my regulary updated system.

It looks like it is something added to Fedora in recent time and don’t think it is something on my system since it happens on another pc with Fedora MATE 43.

I created bug report and added video and screen shots.

If anyone is interested I’ll post them here also.

2

Sounds like a problem with your shell. The shell is reponsible for editing a command recalled from history.

Which shell are you using?
Are you using ESC sequences to do stuff in the shell prompts?

3

Shell is bash, there are ESC sequences for prompt but nothing weird, user, hostname, current directory, git branch. That prompt is the same for a long time and all worked well until recently. I have another system with Fedora MATE 43 and same prompt and same happens.

I’ll try with some most basic prompt and see if it that changes behaviour.

4

Are you sure this should be an upstream KDE bug report? You said that the issue does happen in Alacritty and Xterm, but doesn’t happen in Konsole on Kubuntu or Debian KDE.

5

@barryascott was right, when I deleted all additions from prompt i.e. default one, behavior stopped. So I Immediately marked in bug report that it is resolved and not a bug.

What is weird is that old prompt worked for few years until recently.

6

You were right, with no additions in default prompt all is well.

Behaviour occured not only with commands brought back from history but also when typing goes after command arrives to the end of window.

Anyway the bug is now on my side, even if that prompt worked for a long time until recently.

7

This is one of those situations where having a 2nd “test” login with zero customizations can help with troubleshooting.

8

If anyone else runs in something simillar here is what happened:

problematic prompt:
PS1=“\033[00;36m\u\033[0;34m@\h \[\033[00;36m\]\W”

correct one with all color codes escaped:
PS1=“\[\033[00;36m\]\u\[\033[0;34m\]@\h \[\033[00;36m\]\W”

And only after resolving this I remembered that in fact I have been doing something about prompts recently to make them differ from the ones on vps.

What is certain is that alongside making prompts differ I also had “great” success of introducing bugs in them after a long time…

9

Starship - makes it much easier to customise prompts.

10

Great idea! And istead of having ‘test’ account permanently one can be made just to test if ‘test’ works well.

11

I’ll try that too. Thanks!