Comment # 15 on bug 947229 from Mike Latimer

(In reply to Scott Couston from comment #12)
> Created attachment 648985 [details]
> After software upgrade as discussed prior

Isn't this the issue you reported in bug 947242? If so, I'd prefer to keep the
conflicts issue separate from the daemon not starting automatically.

(In reply to Scott Couston from comment #14)
> I can understand the convenience of having installing virtualisation from
> menu rather than Yast, however as a product, we duplicate so many things.
> We have Apper and Yast Online Update....Apper cant always resolve dependency
> issues.
>
> We have the KDE control Module AND Yast rather than one cohesive force and
> Ive unfortunately been  around sine v9.0
> 
> It just seems to me that our product become more fractured and dispersed
> rather than one cohesive package. (yes understand the amalgamation of
> KDE/Gnome >> Opensuse

(As above, I'll leave the conflict resolution/dependency question for the other
bug.) Your points are valid, but the Virtualization section in YaST does much
more than just install RPMs. Likewise, the Software Manager tool should not be
involved with bridge creation, etc... Obviously you are concerned about
fragmentation more than just on the virt side. However, Bugzilla is not a great
place for this discussion as the participants are very limited. If you'd like
to continue this discussion with the rest of the community, I'd recommend using
the openSUSE mailing lists.