Bug 1086998

Summary: error when customizing display before install
Product: [Fedora] Fedora Reporter: Tom Horsley <horsley1953>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: berrange, crobinso, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-13 22:42:41 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:
Embargoed:
Attachments:
Description Flags
clicking on display
none
choosing spice explicitly
none
error after apply none

Description Tom Horsley 2014-04-12 15:30:25 UTC
Created attachment 885728 [details]
clicking on display

Description of problem:

I tried to install a linux mint virtual machine using the iso I downloaded:
linuxmint-16-cinnamon-dvd-64bit.iso
I check the "customize before install" box, then click on display so I can explicitly pick "spice" (since I have no idea what the default is).
That changes the Display item to say:

Display <gi.overrides.gtk.treemodelrow object at 0xyaddayadda>

After that it cannot start the install.


Version-Release number of selected component (if applicable):
virt-manager-1.0.1-1.fc20.noarch


How reproducible:
Every time

Steps to Reproduce:
1. see above
2.
3.

Actual results:
error

Expected results:
explicitly setting display to spice mode

Additional info:
I'll attach screen shots of the sequence of events.

Comment 1 Tom Horsley 2014-04-12 15:31:15 UTC
Created attachment 885729 [details]
choosing spice explicitly

Comment 2 Tom Horsley 2014-04-12 15:31:57 UTC
Created attachment 885730 [details]
error after apply

Comment 3 Cole Robinson 2014-04-13 22:42:41 UTC

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