Bug 354977

Summary:	sys-process/procps: top writes a wrong .toprc for root
Product:	Gentoo Linux	Reporter:	Quasimodo <quasi>
Component:	[OLD] Core system	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	Defective amd64 version of the file correct x86 version of the file

Description Quasimodo 2011-02-15 08:28:48 UTC

I've installed sys-process/procps-3.2.8 on my systems and I found that for root it didn't remember my color settings for top. First I thought, this is special to root account until I noticed that I can save my settings on x86 systems with the same version.
Today I've started to dig, tried to remove the .toprc file in case there was something wrong, started top and saved my settings again. No effect, the changed setting are not loaded, but I found that the config files for amd64 and x86 differ in size unless they should contain the same settings.
So I found that on amd64 there are missing some keys in the .toprc file which, when entered manually will cause correct function. I have attached both the working x86 and the non-working amd64 version of the config file.

Reproducible: Always

Steps to Reproduce:
1. On amd64 start top as root
2. Change some settigns like color and save the config
3. restart top

Actual Results:  
top will start with default settings

Expected Results:  
top should use the saved settings

Comment 1 Quasimodo 2011-02-15 08:29:42 UTC

Created attachment 262571 [details]
Defective amd64 version of the file

Comment 2 Quasimodo 2011-02-15 08:31:39 UTC

Created attachment 262573 [details]
correct x86 version of the file

Comment 3 Jeroen Roovers (RETIRED) gentoo-dev

2011-02-15 15:20:01 UTC

*procps-3.2.8-r1 (25 Jan 2010)

  25 Jan 2010; Robin H. Johnson <robbat2@gentoo.org>
  +procps-3.2.8-r1.ebuild, +files/procps-3.2.8-toprc-fixup.patch:
  Bug #279819: make top not ignore .toprc.

Maybe something newer should go stable, especially when even the -r2 is quite mature now.

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