Red Hat Bugzilla – Bug 249655
System Monitor shows wrong values after kernel update to 220.127.116.11-27.fc7
Last modified: 2008-06-16 21:58:09 EDT
Description of problem:
After recent kernel update (18.104.22.168-27.fc7) System Monitor 2.18.2 in Gnome
shows wrong values in Memory field. Previous kernel showed correct values. To be
more precise those values are extremely low now (like OpenOffice using about
0.5MB of ram) and for most applications it shows just zero. Here is screenshot
Version-Release number of selected component (if applicable):
Use kernel 22.214.171.124-27.fc7
Steps to Reproduce:
1.Open System Monitor
2.Open few "heavy" applications.
3.Watch memory values in Memory field.
Values are incorrect (too low or just zero).
Values are correct.
Same thing happens with the newest kernel-126.96.36.199-33.fc7.
Same thing happens with latest kernel-188.8.131.52-41.fc7.
I can confirm Comment #2
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.
I can reproduce this but I don't think its a bug. For example, if I make some
changes to a word document (import an image for example) the memory requirements
increase respective to what is being used. You can also view various types of
memory (virtual, shared etc) by checking the boxes under Edit>Preferences>Processes.
I'm re-assigning to the gnome-system-monitor folks to see if they wish to add
anything but suggest this be closed NOTABUG. I certainly don't think it is a
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008.
Fedora 7 is no longer maintained, which means that it will not
receive any further security or bug fix updates. As a result we
are closing this bug.
If you can reproduce this bug against a currently maintained version
of Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.