Bug 1371719

Summary:	system monitor window content pane just shows the background
Product:	[Fedora] Fedora	Reporter:	Nivag <gavinflower>
Component:	mate-system-monitor	Assignee:	Wolfgang Ulbrich <fedora>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	25	CC:	fedora, gavinflower
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-01 17:37:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Nivag 2016-08-30 22:59:35 UTC

Description of problem:
When I bring up a fresh instance of a VM with F25: after logging in and clicking the System Monitor, the system monitor window appears, but the content pane just shows the background.  A while later it displays correctly.

If I log out, and back in again, the problem does not reoccur.  Appears only with a fresh VM instance, AFAICT.

The instance is up-to-date wrt dnf upgrades


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

How reproducible:
Every time

Steps to Reproduce:
1.bring up a fresh instance of a VM
2.log in
3.click on system monitor in top panel

Actual results:
content pane just shows the background, as if it was transparent

Expected results:
should show Resources panel with 3 graphs


Additional info:

Comment 1 Wolfgang Ulbrich 2016-08-31 11:42:11 UTC

If i understand it  correct than you mean m-s-m in a f25 VM?
Which virtualization?
Does it happens on baremetal with a regular graphic card?

Comment 2 Nivag 2016-08-31 21:06:29 UTC

m-s-m running in a f25 VM, using KVM on an F24 box - both boxen were fully uptodate wrt dnf upgrades

Comment 3 Nivag 2016-08-31 21:08:13 UTC

Problem does not arise on the bare metal host.

Comment 4 Wolfgang Ulbrich 2016-09-01 04:56:09 UTC

> If I log out, and back in again, the problem does not reoccur.  Appears only with a fresh VM instance, AFAICT.

I use also qemu-kvm with virt-manager but i never start the system-monitor in first run of a VM. I will check this on next installation.
But don't forget kernel and X driver aren't stable yet.