Bug 124500 - Nano + konsole takes all cpu time
Summary: Nano + konsole takes all cpu time
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: nano
Version: 3.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Woodhouse
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-27 00:39 UTC by Tomi Malkki
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-19 19:25:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomi Malkki 2004-05-27 00:39:37 UTC
Description of problem:
When I edit file in konsole with nano and close konsole when nano is
open in tab which isn't visible nano takes all cpu time and I have to
kill it with pkill nano.

Version-Release number of selected component (if applicable):
nano-1.2.1-4 kdebase-3.1.3-5.2

How reproducible:
Sometimes

Steps to Reproduce:
1. open konsole
2. open nano
3. insert new tab to konsole
4. close konsole when nano-tab isn't visible
    

Additional info:
this have reproduced few times when many tabs open in konsole

Comment 1 Tomi Malkki 2004-05-27 03:06:46 UTC
usually this happens when im logged in as normal user and exec su and
nano. then close konsole and cpu usage is full.

Comment 2 RHEL Program Management 2007-10-19 19:25:21 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.


Note You need to log in before you can comment on or make changes to this bug.