Created attachment 7147 garbled text prompt in terminal Hi, I am using xfce4-terminal 0.8.5.1 for testing on Slackware64 14.2 (compiled it myself). If I right click on thunar -> open terminal on a folder where the path is long (longer than the width of the terminal I believe), I get garbled text. Have attached to show better [1]. Initially if I maximize or minimize the terminal it remains the same [2], but if I maximize and press enter it gets corrected [3] and then if i minimize it remains corrected. My shell is bash and $PS1 is as follows: \[\033[01;32m\]\u\[\033[01;34m\] \w \[\033[01;32m\]$\[\033[00m\] P.S. xfce4-terminal 0.8.5.1 seems to have other bugs with displaying the entered commands when the terminal prompt is too long (like eating the first character of the typed command) [4].
Created attachment 7148 on maximizing the initial garbled prompt terminal
Created attachment 7149 after pressing enter on maximized screen it gets corrected
Created attachment 7150 first character of command eaten if prompt is too long
Created attachment 7151 eats last character as well on alternativelt pressing enter On pressing enter it alternatively eats the last character of the typed command as well [5].
Hi, thanks for the report. I cannot reproduce your problem here: the terminal is showing correctly the path 2 times longer than the window width. I suspect your $PS1 can be the root cause. Can you try it with something more traditional, like "\u@\h \w$ "?
Actually, your $PS1 works fine for me, but please try a simple one anyway. Another question: what is the version of vte3 (or vte-2.91) package in your system?
Hey Igor, Thanks for the quick response! Yes, it does seem my PS1 has something to do with it (used to work earlier though), on changing to the PS1 you wrote ("\u@\h \w$ ") it worked. vte package version is 0.44.3 (inside the package its vte-2.91).
Created attachment 7152 this is how it looks like wit the suggested simple PS1
(In reply to Aaditya Bagga from comment #8) > Created attachment 7152 > this is how it looks like wit the suggested simple PS1 Part of the path is still swallowed, this is weird. It's not happening here. IDK, it could be related to vte or basj, I guess. Can you try updating those packages? Also, can you try another terminal app which is based on vte, e.g. gnome-terminal?
Hi Igor, Compiling gnome-terminal is proving to be slightly tricky: checking for TERM... configure: error: Package requirements (vte >= 0.26.0 glib-2.0 >= 2.25.0 gthread-2.0 gio-2.0 >= 2.25.12 gtk+-2.0 >= 2.18.0 gconf-2.0 >= 2.31.3 x11) were not met: No package 'vte' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables TERM_CFLAGS and TERM_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. vte-0.44.3 is installed as pointed out earlier. As soon as I am able solve this or try it on another distro, I will let you know.
(In reply to Aaditya Bagga from comment #10) > Hi Igor, > > Compiling gnome-terminal is proving to be slightly tricky: > > > checking for TERM... configure: error: Package requirements (vte >= 0.26.0 > glib-2.0 >= 2.25.0 > gthread-2.0 > gio-2.0 >= 2.25.12 > gtk+-2.0 >= 2.18.0 > gconf-2.0 >= 2.31.3 > x11) were not met: > > No package 'vte' found Hi Aaditya, It seems you're trying to build a very old gtk2 version of gnome-terminal. Can you build a newer gtk3 version? Also, is it possible to update vte-2.91 version?
Hey Igor, I check on another distribution where I have xfce4-terminal-0.8.5.1 and vte-0.46.1 (2.91), and this bug is not present :-) So its likely the bug lies with vte; will try upgrading to vte-0.46.1 (2.91) on my Slackware install and see if it gets fixed.
Hi Aaditya, Thanks for the update! Ok, so this seems to be a vte or a system configuration issue.
Hi Aaditya, any news?
Hi Igor, Updating to vte-0.46.1 is proving to be slightly difficult as it needs libpcre2-8 >= 10.21 and many packages depend on libpcre2.8 so upgrading it would not be easy. So I think this bug can be marked as resolved due to the issue likely being with vte rather than xfce4-terminal. If later on after upgrading vte this bug is still present then I can reopen it. Thanks for your help, Aaditya