Bug 436869 - Opening local connection via the file menu doesn't allow for the creation of a new guest.
Summary: Opening local connection via the file menu doesn't allow for the creation of ...
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager   
(Show other bugs)
Version: 5.2
Hardware: All Linux
Target Milestone: rc
: ---
Assignee: Daniel Berrange
QA Contact: Virtualization Bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2008-03-10 20:34 UTC by Scott Crenshaw
Modified: 2009-12-14 21:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-09-14 23:03:41 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Rob Kenna 2008-03-10 20:34:13 UTC
If the local connection is opened via file/"open connection", then the "new"
button" is not displayed.  If you double click on local, "new" is displayed.

version 0.5.3-2.el5

Comment 1 Cole Robinson 2008-03-11 15:35:00 UTC
Hmm, I'm a bit confused. The new guest button will only be active if you are
currently selecting an active connection. file->new connection should open this
new connection but it won't select/highlight it, so the new button will not
immediately appear active. This is expected behavior, as we don't want to steal
the current selection on the manager screen.

Is this what you meant, or did I misunderstand? If so, please explain the exact
process you are using: how many connections exist prior to file->new, what type
of connection are you opening, and please post ~/.virt-manager/virt-manager.log
as well. Thanks!

Comment 3 Cole Robinson 2008-06-23 20:51:47 UTC
Ping, never set this to needinfo. Any info in response to comment #1?

Comment 4 Cole Robinson 2008-09-14 23:03:41 UTC
Reporters account was closed, and I can't decipher the original bug's intent. Closing as NOTABUG.

Note You need to log in before you can comment on or make changes to this bug.