Bug 162941 - 'Top' utility doesn't save configuration file '.toprc' correctly
'Top' utility doesn't save configuration file '.toprc' correctly
Status: CLOSED DUPLICATE of bug 161449
Product: Fedora
Classification: Fedora
Component: procps (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Karel Zak
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-07-11 14:50 EDT by Niksa Jurinovic
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-11 16:16:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Niksa Jurinovic 2005-07-11 14:50:30 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322)

Description of problem:
`top` utility from procps doesn't function correctly. When window colors are changed, pressing 'W' doesn't save configuration file (.toprc) correctly, so the next time the top is started, the old black-and-white screen always appears (as if nothing were changed). Examining .toprc config file, it can be seen that labels on the left side are missing (Def, Job, ...). 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start top
2. Change the window colors
3. Press 'W' to save configuration file. Configuration file is saved (but not correctly). Restart the top utility. 

Actual Results:  Black-and-white screen appears as if nothing were changed.

Expected Results:  Colored window must appear.

Additional info:

This may be interesting: RHEL-4 AS 'procps' binary rpm package works OK on FC4. But, when source RHEL-4 'procps' rpm package is rebuilt on FC4, rebuilt 'top' works just as FC4 'top' (doesn't save .toprc correctly).
Comment 1 Karel Zak 2005-07-11 16:16:08 EDT

*** This bug has been marked as a duplicate of 161449 ***

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