Bug 477751

Summary: virt-manager should select a default connection from the list
Product: [Fedora] Fedora Reporter: Mark McLoughlin <markmc>
Component: virt-managerAssignee: Daniel Berrangé <berrange>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 11CC: berrange, crobinso, hbrock, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-14 15:39:56 UTC Type: ---
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
virt-manager-select-added-connection.patch none

Description Mark McLoughlin 2008-12-23 10:45:28 UTC 
Created attachment 327746 [details]
virt-manager-select-added-connection.patch

If you start virt-manager, nothing is selected from the list and you have to manually select something before doing anything

A sensible default might be to select a connection by default, patch attached
Comment 1 Cole Robinson 2009-02-16 02:38:15 UTC 
Okay, I used a couple fixes here:

The above fix, to select a connection after it has been appended to the list (though I forgot to attribute it to you in the commit message. Sorry Mark :/ )

http://hg.et.redhat.com/cgi-bin/hg-virt.cgi/applications/virt-manager--devel/rev/e2ba569c6609

But since for multiple connections this can seemingly select a random list entry, I committed a fix to explicitly select the first list entry on app startup:

http://hg.et.redhat.com/cgi-bin/hg-virt.cgi/applications/virt-manager--devel/rev/28730e3a48b8

Moving to POST.
Comment 2 Cole Robinson 2009-09-14 15:39:56 UTC 
Moving this to F11 and closing as CURRENTRELEASE: not enough of a critical issue to backport.