Ubuntu
gnome-system-monitor package

gnome-system-monitor: display problems

Bug #956828 reported by Redmar on 2012-03-16

This bug report is a duplicate of: Bug #1019245: System Monitor graph fades when enlarging window size beyond a certain size.. Edit Remove

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	gnome-system-monitor (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

The 'graphs'-tab in gnome-system-monitor suffers from a number of graphical glitches. First of all the lines that show the cpu/memory/net history are very hard to see, and often invisible. Also the percentages and time shown on the x and y axis of the plots are mostly invisible. I do not have display problems with any other program, or with other parts of gnome-system-monitor

I've attached a screenshot of the problem

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-system-monitor 3.3.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Fri Mar 16 11:15:21 2012
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
SourcePackage: gnome-system-monitor
UpgradeStatus: Upgraded to precise on 2012-03-10 (5 days ago)

Tags:

Revision history for this message

Redmar (redmar) wrote on 2012-03-16:

screenshot of the probleml Edit (66.8 KiB, image/png)
Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (309 bytes, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-03-24:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-system-monitor (Ubuntu):
status:	New → Confirmed

Revision history for this message

Robert Roth (evfool) wrote on 2012-04-08:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #881172, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.