Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 88423 - nano is not killed (and uses nearly 100% cpu) when closing terminal w/o exiting.
Summary: nano is not killed (and uses nearly 100% cpu) when closing terminal w/o exiting.
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: SpanKY
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-08 20:16 UTC by Mint Shows
Modified: 2005-04-09 18:00 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mint Shows 2005-04-08 20:16:38 UTC
I noticed when opening my xfce terminal as a regular user, then changing to root to modify a few config files with nano, if I close the terminal without first exiting nano, my CPU usage would jump to nearly 100%.  I checked my list of processes, and sure enough, nano was never killed when the terminal was closed.

This only happens when su 'ing from a regular user account to root.  If I open nano as regular user, then close the terminal w/o exiting nano, it kills the process. Not sure if this is a nano bug..or an issue with the terminals.

I then tested with several other terminals.  Here are the results:
konsole: doesn't kill nano
xterm: doesn't kill nano
xfterm4: doesn't kill nano

gnome-terminal: OK ..kills nano process
aterm: OK ..kills nano process



Reproducible: Always
Steps to Reproduce:
1. open xterm, konsole, or xfterm4.
2. su  (switch to root)
3. run nano (either with a specified file..or by itself)
4. close the terminal without exiting nano.
Actual Results:  
The nano process is not killed and its CPU usage jumps to 90-100%.


Expected Results:  
The terminal should kill nano when it is closed..even without first exiting nano.

Here's the first few lines of 'top' after closing terminal:

top - 22:14:59 up 9 days,  3:28,  5 users,  load average: 0.48, 0.29, 0.35
Tasks: 112 total,   2 running, 110 sleeping,   0 stopped,   0 zombie
Cpu(s): 68.1% us, 31.9% sy,  0.0% ni,  0.0% id,  0.0% wa,  0.0% hi,  0.0% si
Mem:    513772k total,   413052k used,   100720k free,    33888k buffers
Swap:   522072k total,    76756k used,   445316k free,   158468k cached
Kill PID 6658 with signal [15]: 
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND           
 6658 root      25   0  4228 3380  676 R 94.2  0.7   0:24.89 nano
Comment 1 SpanKY gentoo-dev 2005-04-08 21:42:51 UTC
you neglected to mention what version of nano you're using or post `emerge info` like you were supposed to
Comment 2 Mint Shows 2005-04-08 22:01:17 UTC
sorry...I had intended to....just forgot...
*  app-editors/nano :
        [   ] 1.2.4 (0)
        [  I] 1.3.4 (0)
        [M~ ] 1.3.5 (0)
        [M~ ] 1.3.6 (0)

Here's my entire 'emerge info':

Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5, glibc-2.3.4.20041102-r1, 2.6.10-gentoo-r6 i686)
=================================================================
System uname: 2.6.10-gentoo-r6 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#2, Apr  5 2005, 16:38:26)]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r7
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://open-systems.ufl.edu/mirrors/gentoo http://mirror.datapipe.net/gentoo http://gentoo.seren.com/gentoo ftp://ftp.ndlug.nd.edu/pub/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X aalib alsa apm arts avi berkdb bitmap-fonts cdr crypt cups curl dvd emboss encode esd fam flac foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imagemagick imlib ipv6 java jpeg junit kde ldap libg++ libwww mad mikmod motif mozilla mp3 mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sdl spell ssl svga tcpd tiff truetype truetype-fonts type1-fonts x86 xml xml2 xmms xv zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Comment 3 SpanKY gentoo-dev 2005-04-08 23:03:20 UTC
give 1.3.6 a shot, iirc they fixed a bug with nano ignoring input/signals between 1.3.5 and 1.3.6
Comment 4 Mint Shows 2005-04-09 15:31:26 UTC
This does not happen with nano-1.3.6.  Maybe it should be unmasked now??
Comment 5 SpanKY gentoo-dev 2005-04-09 18:00:07 UTC
i'll prob move it into stable in a bit