Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1309913 - VM display not visible with GTK+ 3.19.9 (?)
Summary: VM display not visible with GTK+ 3.19.9 (?)
Keywords:
Status: CLOSED DUPLICATE of bug 1311612
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 24
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 00:01 UTC by Adam Williamson
Modified: 2016-02-25 15:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-25 15:32:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Adam Williamson 2016-02-19 00:01:10 UTC 
On current Fedora Rawhide, if I run a virtual machine in virt-manager, I cannot see the VM's display on the 'graphical console' tab as usual. The area where it should appear is just blank grey.

virt-viewer behaves the same way, but if there's a shared component that handles this I don't know what it is, so filing against virt-manager for now.

This happens whether the VM is using VNC or Spice. If I run virt-viewer at a console, I see what seems like a possibly-significant error:

(virt-viewer:5542): Gtk-WARNING **: Allocating size to VncDisplay 0x562471606270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

When using Spice there's a similar message only referencing 'SpiceDisplay' not 'VncDisplay'.

I haven't run a VM on this box for a while so I don't know for sure, but this *may* have started with GTK+ 3.19.9, which landed recently.
Comment 1 Jan Kurik 2016-02-24 15:34:21 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Comment 2 Cole Robinson 2016-02-25 15:32:24 UTC 

*** This bug has been marked as a duplicate of bug 1311612 ***
Note You need to log in before you can comment on or make changes to this bug.