if you run nano su'ed to root inside a gnome-terminal and close the terminal without exiting nano, nano is not terminated and consumes 100% CPU. On the other hand if you are a normal user, and open nano and close the terminal, nano exits properly. Reproducible: Always Steps to Reproduce: 1.open gnome-terminal in GNOME2 2.su to root 3.open nano some file or any file existing or new 4. close gnome-terminal without exiting nano. Actual Results: nano consumes 100% CPU Expected Results: nano must be terminated and gnome-terminal must be exited
GNU nano version 1.0.9 gnome-terminal version 2.2.1
this is a nano problem....it happens a lot of times....why i switched to vim ;-) if this is reproduceable, then we know what the problem is, but it happens in eterms and aterms.... seth
what do you suppose the problem is?
coul'd not reproduce this in x86 (nano 1.2.0 , gnome-terminal 2.2.1)
cant reproduce on x86 with nano-1.0.9-r1, or nano-1.2.1 and gnome-terminal-2.2.2, using gnome-system-monitor and top to check cpu usage.
I have the same problem. But I have it both in Konsole and in the regular Linux Console. When I cleanly exit nano (with Ctrl-X) nano sometimes keeps running and consumes 100% CPU.
does this still occur with the 1.2.x series ? i had this happen a lot with me, but as the version increased, the # of times this happened dramatically decreased ...
looks like the bug has been tracked down ... when it's been fixed upstream i'll fix it in Gentoo ;)
added a patch to fix this to 1.2.1 and 1.2.2
I use nano 1.3.1 and it doesn't appear to be fixed, ie if I open shell, su, nano and just close the shell, nano goes to 100% CPU time.
send a message to the nano-devel because all my test cases have been fixed
*** Bug 44296 has been marked as a duplicate of this bug. ***
*** Bug 58601 has been marked as a duplicate of this bug. ***