Was working yesterday.
After a “zypper up” which updated plenty of things I believe also the libvirt packages, any tool that browses the local directory now freezes (tried both configuring a shared file system and “create new vm” wizard).
I then tried to “force re-install” the libvirt related pakages.
Because I also have some openstack related private repos installed, the Solutions given were to do nothing, break dependencies or change vendor to support the private repos (probably further confirming that an Update changed something seriously).
However, after choosing the option to change vendor, the problem has now gotten worse. Now, when I launch vm manager it cannot connect to a local running qemu server (required for KVM and I believe also for recent versions of Xen).
Am going to submit a bug, but if anyone is seeing the same thing on their machine, post a “me, too” here so I know it really is something others are experiencing.
Again, this seems to be related to an update pushed sometime between 16-17 July 2013.
After gathering as much info about the problem as possible, am going to investigate rolling back (if possible).
Minor update:
Current investigation suggests the problem may show up in vm manager, but is more likely related to how it interacts with the Desktop for its file browsing functionality. Am now looking more closely at what KDE components were updated since yesterday (there were many).
After the following,
All seems to be working properly now…
Force re-install all libvirt, then all qemu packages pointing to original Install DVD
Due to a qemu re-install issue, <added> the following to /etc/permissions
/usr/lib/qemu-bridge-helper
After running “zypper up again” it looks like whatever the problem was has been resolved. Either someone read my bug in bugzilla and pushed a fix really fast or my system suffered from some quirkiness.
Because this issue was described in another Post, I suspect that this problem was not isolated but without knowing for sure whether a specific update or my process of re-installing worked, I wouldn’t know if the solution is to do the force installs I described or if simply getting most recent updates is all that is required.