In the last day I am loosing rather often control in terminal windows. I have the feeling it happens mostly with gnome-terminal: rose@impala:/home/rose(2)$ qlist -Iv gnome-terminal x11-terms/gnome-terminal-3.14.2 I think, mostly it is happens after starting programms with graphical output, e.g. starting meld or unison from the command line. After finishing the graphical programm the "echo" property in the terminal window is missing. Today it happens even without starting a "graphical" programm. I did the following: rose@impala:/home/rose(3)$ ll -t Downloads/ | head insgesamt 3920760 -rw-r----- 1 rose rose 836356 7. Jan 18:12 TM-1-main.pdf -rw-r----- 1 rose rose 3334664 5. Jan 14:35 document.pdf -rw-r--r-- 1 rose rose 2408 31. Dez 21:49 test-bw-master.zip -rw-r--r-- 1 rose rose 1054867456 25. Dez 17:12 gnome-3.14.iso -rw-r--r-- 1 rose rose 1549615104 24. Dez 16:23 linuxmint-17.1-cinnamon-64bit.iso -rw-r----- 1 rose rose 2177 11. Nov 10:42 nv84_fence.diff -rw-r--r-- 1 rose rose 62984169 6. Nov 20:39 Matplotlib.pdf -rw-r--r-- 1 rose rose 426647 6. Nov 16:51 unicode-math.pdf -rw-r--r-- 1 rose rose 52334 20. Okt 08:51 lLyrics-master.zip rose@impala:/home/rose(4)$ mv: Fehlender Dateioperand „mv --help“ liefert weitere Informationen. rose@impala:/home/rose(5)$ speed 38400 baud; line = 0; lnext = <undef>; min = 1; time = 0; -brkint -icrnl -imaxbel iutf8 -icanon -echo rose@impala:/home/rose(6)$ At the bash line number (3) everything was fine. Then I tried to move a file. I entered "mv " but I did not get the output of "mv " at the prompt. I pressed <enter> and got the error message. Then I entered "stty <enter>" and got the output of stty, but the command is not show. I opened a new terminal window and entered the same command: rose@impala:/home/rose(1)$ stty speed 38400 baud; line = 0; -brkint -imaxbel iutf8 I switched again to the first terminal window and blindly "stty sane", the echo is back. Now everything seems again work as expected (Even backspace = erase). I am just remembering, that something similar has also happened for user root. As user root I am only using xterm (not gnome-terminal). So the reason is maybe something deeper (x11-libs/vte ?). Any idea, what I could further check?
An other strange behaviour I noticed in the last time is the CTL-C handling. I am trying to enter a new command, but sometimes some background process garbles with his output my terminal window. I do not know how much of the new command I have already entered. I am used to press CTL-C to get a clear prompt. But the terminal or bash logs me out. I reported this already as Bug 528914. Maybe there is a connection between both issues.
Looks exactly like bug #528914 - perhaps you should check precisely what bash-completion scripts are being loaded. Also, can you reproduce this with a different terminal emulator?
(In reply to Jeroen Roovers from comment #2) > Looks exactly like bug #528914 - perhaps you should check precisely what > bash-completion scripts are being loaded. > > Also, can you reproduce this with a different terminal emulator? At least the CTL-C logout problem I just have seen again in a pure xterm: root@orca:/root(2)# >nohup ; nohup emerge -uvDN wol^C root@orca:/root(2)# logout rose@orca:/home/rose(2)$ ^C
The echo problem also happens in xterm: root@impala:/root(85)# wan_speed_check.sh > /home_caiman/rose/Txt/Configurations/wan_speed__ wan_speed__impala.txt wan_speed__lynx2__BIC.log wan_speed__orca.txt root@impala:/root(85)# wan_speed_check.sh > /home_caiman/rose/Txt/Configurations/wan_speed__impala_01.01.2015.txt ^C root@impala:/root(86)# rm: missing operand Try 'rm --help' for more information. root@impala:/root(87)# speed 38400 baud; line = 0; erase = ^H; lnext = <undef>; min = 1; time = 0; -brkint -icrnl -imaxbel iutf8 -icanon -echo 'stty sane' sets echo back, but 'BACKSPACE = erase': root@impala:/root(88)# -su: sttysane: command not found root@impala:/root(89)# root@impala:/root(90)# ls^H^H How can I check precisely what bash-completion scripts are being loaded? 'eselect bashcomp list' shows 776 lines. I did not set this manually.
Created attachment 393546 [details] Output of 'eselect bashcomp list'
I would focus on bug 528914... until that is not handled there is no much sense on reporting more bugs that are caused by that one :/ *** This bug has been marked as a duplicate of bug 528914 ***
