Description of problem: Hello everyone, I installed a brand new Mageia 7.1 with Plasma 5 (from Live ISO, with updates and tainted software repositories enabled). Then I upgraded the system and installed gnome-terminal, which should have installed a "vte3-profile" package. This package installs an /etc/profile.d/vte.sh script. After a restart, Konsole has begun to show a double backslash at every print of the (Bash) prompt. Carriage Return was not perfectly working when I scrolled the history. For now I solved this by adding a line into vte.sh file. (See attachment) The patch works for both Mageia 7.1 (0.56.3-1) and Cauldron (0.58.3-1) versions. Version-Release number of selected component (if applicable): vte3-profile-0.56.3-1.mga7.noarch.rpm vte3-profile-0.58.3-1.mga8.noarch.rpm How reproducible: Anytime the /etc/profile.d/vte.sh is present. Steps to Reproduce: 1. urpmi gnome-terminal vte3 vte3-profile 2. Close and reopen Konsole 3. Print some long comment and scroll the history in order to see issues with carriage return. Double backslash will always be printed before the prompt. Attachment: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 - --- etc/profile.d/vte.sh 2019-05-06 23:05:04.000000000 +0200 +++ etc/profile.d/vte.sh 2020-01-19 19:26:39.711876785 +0100 @@ -22,6 +22,7 @@ # Not running under vte? [ "${VTE_VERSION:-0}" -ge 3405 ] || return 0 +[ -z "$KONSOLE_VERSION" ] || return 0 __vte_urlencode() ( # This is important to make sure string manipulation is handled -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEKW3afw3eIssMTt/gPL30/UY+UAYFAl4l99kACgkQPL30/UY+ UAbdkgf/ZHfnJb9PIUI58mpIXmYyW29TI4dERCt0f4MJAJC0oCSnyV9TML72AMUs Rg7t0aHDRQsHZ6NHqWVtbSKBuQIPu0/SzmHEb3j97k9ojg7HPnchuJuRPN87ZBbF lkNsPszUzoclPU7kFFOFlLqI36mpd/VSgdgV8oLeHc2CurEA8ViKF/nb+1kZI5Rn POCEbKBA8dTdVT1E+aMuhf7Oi3Cbb9Vqu2b+OxZ2IzODBgPQEP1r774ZpLUsZIyK cg1J4VzkBBnApsVqgLj6TmmwsbhYyUOSewKmExkYkuZu3RHiOxbucF6ytxJDhg7G hPer4PH4t9eJODGP7RnJJHQfTWU81Q== =8+fn -----END PGP SIGNATURE-----
Created attachment 11478 [details] Bypass vte3 profile in Konsole
CC: (none) => f.open.p
Source RPM: vte3-profile-0.56.3-1.mga7.noarch.rpm - vte3-profile-0.58.3-1.mga8.noarch.rpm => vte3-profile-0.56.3-1.mga7.src.rpm - vte3-profile-0.58.3-1.mga8.src.rpm
Source RPM: vte3-profile-0.56.3-1.mga7.src.rpm - vte3-profile-0.58.3-1.mga8.src.rpm => vte3-0.56.3-1.mga7.src.rpm - vte3-profile-0.56.3-1.mga7.noarch.rpm - vte3-profile-0.58.3-1.mga8.noarch.rpm
What language is your system? Can you supply a screenshot of Konsole misbehaving? And supply an explicit example (instructions) of how to create the fault (see my failure to do so later). This is all a bit confusing - what requires or is required by what - as I tried to reproduce the fault. I had already: konsole-19.04.0-1.mga7 gnome-terminal-3.32.2-1.mga7 vte3-0.56.3-1.mga7 vte3-profile-0.56.3-1.mga7 lib64vte2.91_0-0.56.3-1.mga7 /usr/bin/vte-2.91 -rw-r--r-- 1 root root 1945 /etc/profile.d/vte.sh has: # Not running under vte? [ "${VTE_VERSION:-0}" -ge 3405 ] || return 0 --- $ urpmq --requires gnome-terminal | grep vte libvte-2.91.so.0()(64bit) $ urpmq --whatrequires vte3-profile vte3 $ urpmq --whatrequires vte3 lib64vte2.91_0 $ urpmq -l lib64vte2.91_0 /usr/lib64/libvte-2.91.so.0 $ urpmq -l vte3 | grep bin /usr/bin/vte-2.91 $ urpmf /etc/profile.d/vte.sh vte3-profile:/etc/profile.d/vte.sh So we have 3 terminals: konsole, gnome-terminal, vte-2.91 The last I did not know, but (I am in Xfce at the moment) it *looks* like what Gnome uses for its default terminal application. The explicit 'gnome-terminal' I do not recognise. But they all work. I am not sure of the relevance of gnome-terminal. The best test I could do from your description was, in Konsole: $ # hsdfojkdh hsjklfkj hfsjklfkjhl hsjklf hshjfklshf hfsjkljfh hsjklfj hfshfjk lsjfh hfsjklf hsjfkl sjhfjkd lsfkjsh fhsjklf jhsfhsjklfdj hhfsjklfd hsfjklfjd h $ and that long line was perfectly shown by up-arrow. No messed prompts. Similarly, Konsole: $ echo A very long comment qjklqjklmkdl jdklmq jdqklmd jqdklm jqdklm qjd qjklmdk qjdkldm jqkldmk jqd jqdklmd djqkldm qjdklm djqklmdk dqjklms jdkqlsdjdl mqjkldm A very long comment qjklqjklmkdl jdklmq jdqklmd jqdklm jqdklm qjd qjklmdk qjdkldm jqkldmk jqd jqdklmd djqkldm qjdklm djqklmdk dqjklms jdkqlsdjdl mqjkldm $ $ [up arrow] $ echo A very long comment qjklqjklmkdl jdklmq jdqklmd jqdklm jqdklm qjd qjklmdk qjdkldm jqkldmk jqd jqdklmd djqkldm qjdklm djqklmdk dqjklms jdkqlsdjdl mqjkldm ---------- I wonder about the differences between us. However, your suggested fix in /etc/profile.d/vte.sh to bypass vte3 profile in Konsole looks innocent enough, and if it solves your problem, good. This file is in:package: vte3-profile-0.56.3-1.mga7 which is in SRPM: vte3-0.56.3-1.mga7.src.rpm I will try the edit here to see whether it has any -ve effect on the 3 terminals. Assigning this globally as vte3 has no registered maintainer; CC'ing Olav who has done all its recent commits.
CC: (none) => lewyssmith, olavAssignee: bugsquad => pkg-bugs
I just solved another issue with byobu's tmux. Although it seems not correlated, I tried to restore the original vte.sh file and now the two backslashes are no more present. The strange thing is that the issue was present outside of byobu and tmux. So this is not a bug. Thanks for you help Lewis Smith!
Status: NEW => RESOLVEDResolution: (none) => INVALID