Comment 6 for bug 1745273

My locale is as follows:
$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=de_DE.UTF-8
LC_TIME=de_DE.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_ALL=

Using “unset PROMPT_COMMAND” had no effect at all (and seems to be empty for me, anyway?). This is pretty much a fresh install, so I’m using Ubuntu’s default value of PS1:

$ echo "'$PS1'"
'\[\e]0;\u@\h: \w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '

However, when I change that to

PS1='\[\033[01;34m\]\w\[\033[00m\]\$ '

there seems to be no more crashing. So it seems that certain values of PS1 do indeed trigger this bug.

I have also tried the bash development version, as suggested. Even with the default value of PS1, I haven’t been able to cause a crash there. However, this version goes REALLY crazy with the input prompt (junk characters, erratically printing parts of the history or working directory path to the terminal when pressing the arrow keys, invisible text input etc.) for long working directory paths (with or without Unicode characters), making input all but impossible. So whatever the difference between the two versions is, it’s not an improvement.

Anyway, thanks a lot for the help so far. Since I’m not seeing the crash in the newer version, I’m assuming it will be gone when Ubuntu updates (with the weird behavior for long paths hopefully due to different compiler flags or something like that). As a workaround, modifying PS1 seems to work.