after running nano as root through konqueror, when i close konqueror there is a nano proccess using 100% of my cpu Reproducible: Always Steps to Reproduce: 1.run konqueror 2.type su 3.type password 4.type nano 5.close konqueror (using x at top right) Actual Results: #ps -A | grep nano 26544 ? 00:03:04 nano Expected Results: nano should have just closed #emerge info Portage 2.0.50-r9 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.2-r9, 2.4.26) ================================================================= System uname: 2.4.26 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.4.16 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distcc sandbox" GENTOO_MIRRORS="ftp://mirror.pacific.net.au/linux/Gentoo ftp://gentoo.ccccom.com ftp://gg3.net/pub/linux/gentoo/ http://gentoo.ccccom.com" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gpm gtk2 guile imlib java jpeg kde libg++ libwww mad mikmod mmx motif mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline sdl slang spell ssl svga tcltk tcpd tiff truetype wmf x86 xml2 xmms xv zlib"
ummm @#$% konqueror = konsole, I was rather wrecked when I wrote that bug report, sorry.
It's impossible for konsole to kill that process, it is owned by root and konsole is not permitted to close it. So, when you close the konsole, it really can do nothing better than that...
Ok forgetting about konsole closing nano it or not (which I think it should be able to: send su close signal, it sends root proggies kill signal...), why is nano using up 100% of my cpu when this happens?
Just found this: http://lists.gnu.org/archive/html/nano-devel/2003-09/msg00033.html bug 17878 and bug 44296
*** This bug has been marked as a duplicate of 17878 ***